New subject: Strange Broadcasts...

12 Jun 2015

...
  Subject:
 Re: [44net] Strange Broadcasts...
 From:
 "Marc, LX1DUC" &lt;lx1duc(a)laru.lu&gt;
 Date:
 06/12/2015 05:06 PM

 To:
 AMPRNet working group &lt;44net(a)hamradio.ucsd.edu&gt;

 I do think that regardless of the OS it is much more important that anybody using 44net
addresses shall support the IPIP mesh, regardless of any other routing procedures (e.g.
direct BGP announcement, etc) in use. I have the "luxury" to be able to 
 do direct BGP announcements, so I can reach BGP-only 44networks without NATing my 44net
to my commercial IP address, others don't have this luxury but would eventually like
to reach those 44etworks without the requirement for NAT. 
Our country gateway is BOTH on BGP and on the IPIP mesh.  It advertises the entire
44.137.0.0/16 network on both BGP and IPIP.
My systems at home are on net 44.137.41.96/28 and are linked to a local node for
44.137.40.0/23 via RADIO (unusual, I know...)
and that node is again linked to the gateway system via our HAMNET.

So my system is reachable both for BGP and for IPIP systems (and radio-connected systems)
without me running IPIP myself.
Hence I don't need to do that at home.

When my radio link fails, I can setup an IPsec or OpenVPN VPN connection to our gateway,
and routing in the network will
automatically adapt  (the gateway and the nodes talk BGP on a private ASN# on the HAMNET
side and the gateway will advertise
my 44.137.41.96/28 subnet when I setup an IPsec or OpenVPN link).

So there is no need to worry!

Rob