On Sat, Apr 21, 2018 at 4:51 AM, Tony Langdon vk3jed@vkradio.com wrote:
The problem I have with this is when traffic is routed via the regular ISP, the source address is no longer 44.x, it's the public IP of the NAT router.
Why should I as an Echolink relay operator be expected to go through the additional effort of configuring IPIP just so you can enjoy the novelty of both ends of the connection having 44/8 addresses? Your IPIP encapsulated packet will still have your ISP's address and will take the same path regardless. I understood that one of the motivations of the 44.190/16 prefix was to allow end users to easily configure their routing policy correctly to avoid tunneling to UCSD first (which isn't the end of the world since Javier and I are setting up our relays also in California).
-- Kenneth Finnegan http://blog.thelifeofkenneth.com/