On 13.5.2015. 04:55, Andrew Ragone (RIT Alumni)
wrote:
> 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
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
Hi Eric,
Are you doing the BGP announce or would the hosting provider you are
proposing we share doing the announce?
Are you familiar with what the HamWAN group is doing with their Open
Peering Policy (