New subject: Portal doesn't allow IPIP anycast via 44net

11 Apr 2014

On 4/11/14, 12:26 PM, lleachii(a)aol.com wrote:
...
  TOS section 7c requires him to provide an AMPRNet
connection for AMPR
 devices local to him; but not necessarily via rip44. Since its not valid at
 this time to tunnel to a 44subnet via a 44 address, I don't see how he's in
 compliance (save via RF, which is their local AMPRNet anyway). 
Where would hamradio be with out armchair lawyers?  I love this hobby.

If he's using 44net space and announcing it to the internet via BGP he is
providing access to the users behind his BGP router that have AMPRnet
addresses. Sure they may not have access to the rest of AMPRnet via the IPIP
routes, but that's optional.  I'd even venture to guess most hams on his
system won't care/know that it's missing the IPIP tunnels.

People using AMPRnet space in BGP are most likely concerned with providing
access to the internet via ham radio, not accessing slow 9600 baud links from
the internet.

...
  Bart also mentioned:

 >>> It allows our microwave network to
remain connected to the rest of 
>>> AMPRnet as long as we have at least 1 ISP that isn't dead.  **The
problem would also solved if he announces 209.189.196.68/32 on both
 ISP connections.** 
A /32 is going to be route filtered, and it's not his IP space, it's a /30 or
/31 from his upstream BGP peer.  So no, this is not possible.

The entire *IDEA* of BGP is to allow you to control your own redundancy and
peering to the routing table.
-- 
Bryan Fields

727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net

Re: [44net] Portal doesn't allow IPIP anycast via 44net