3 Jan
2015
3 Jan
'15
11:01 a.m.
I agree with Brian on his statement.
"Treating this like is some kinda special VPN really holds amprnet back.
73's W9CR"
--
When i friday tried to get my nodes activated, the portal.ampr.org was
down. A real detriment to someone new at this.
73s. Leo, N5JEP
On Jan 3, 2015 10:52 AM, "Bryan Fields" <Bryan(a)bryanfields.net> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
On 1/3/15, 11:45 AM, Brian wrote:
On Sat, 2015-01-03 at 08:35 -0800, Eric Fort
wrote:
Why tunnel at the gateway level?, let the other gateways run BGP. Problem
solved.
How you get to the gateway could be IPIP, GRE, IPSEC, or you can run BGP
yourself. Or even if you have a friendly peering location that lets you
put a
dish on the roof.
Treating this like is some kinda special VPN really holds amprnet back.
73's W9CR
--
Bryan Fields
727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
> how about eliminating this issue perminantly
from ever happening and
> moving to voluntary peering between gateways. Know thy neighbor and
> be responsible foryourpeers androutesseems to work really well for
> everyone else yet amprnet still relies upon route distribution from a
> single source.
Are you suggesting something such as a possible BGPv2 that all
gateways
or designated regional gateways could perhaps tunnel broadcast between
themselves? This would be interesting and may help with other route
issues between those using RIPv2 <-> BGP amprnet sites.