13 May
2015
13 May
'15
11:09 a.m.
On Wed, May 13, 2015 at 1:20 AM, Pedja YT9TP <yt9tp(a)uzice.net> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
On 13.5.2015. 04:55, Andrew Ragone (RIT Alumni) wrote:
for
a long time. the single dedicated IP is taken care of by the cloud
based hub and a relitively simple setup on your client router at your
network edge simply makes 44net show up on your lan. no dedicated machine,
no dedicated or special software, no having to write custom config files,
just easy and instantly deployable using standard protocols used everyday
that real people use often and understand.
Eric
With that said, I am not sure what the advantage
of this is (aside from
perhaps the dynamic IP issue you mention), though, since you could always
write a script to login to the AMPRNet portal and tweak the IPIP tunnels
with any WAN IP address updates. When you have the free gateway over in
California already, it seems like that would be the way to go aside from
directly advertising your own BGP CIDR block.
I guess this would allow anyone with any decent router with VPN client
capability) to be able to connect to 44net without requirements for
struggling with dedicated computer and very specific installation to make
it run.
Yes, exactly and well said! that's exactly the point I've been pushing ---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net