On 2015-06-12 17:22, Bryan Fields wrote:
(Please trim inclusions from previous messages) _______________________________________________ On 6/12/15 11:06 AM, Marc, LX1DUC wrote:
I do think that regardless of the OS it is much more important that anybody using 44net addresses shall support the IPIP mesh
Why?
I announce subnets via BGP, that should be enough. I maintain the single end point for the 44 network (UCSD gw) is a bad idea, and it's not my fault it has broken routing for more specific networks.
There are several reasons, I'll just provide 3+1, but there are probably many many more:
- not everybody can do BGP - accessing your network will require NAT on the remote end (unless the YLs/OMs ISP allows her/him to originate IP packets with 44net addresses), NAT breaks end-to-end communications - you won't be able to differentiate between commercial access to your 44net and 44net traffic NATed to commercial IP - (I'm not sure about this) in case the YL/OM can send unNATed traffic and the YL/OM didn't configure a revDNS for his 44net IP, you won't be able to send a response back to her/his 44net as the UCSD gw will block traffic from the WAN interface to 44net addresses without revDNS.
I advocate for an united 44net where each participant shall be able to reach any other participant from a routing perspective (there could still be firewalls). I don't think that HamRadio (and I include 44net) is about islands that cannot communicate with each other. But those are just my thoughts. Your opinion my be different.
vy 73 de Marc