+1
On November 12, 2014 12:15:25 PM EST, Tom Hayward <esarfl(a)gmail.com> wrote:
>
>I think we're getting a bit ahead of ourselves here proposing new
>special announcements.
>
>Here's another idea: don't assume anything spans the whole 44/8.
>Instead of policy-routing 44/8, policy route for each of the routes
>found in the encap. 44.24.221.0/24 isn't in the encap, so you should
>source packets to it from your commercial ISP source IP. UCSD is not
>involved.
>
>Tom KD7LXL
--
Bryan Fields
727-409-1194
http://bryanfields.net
When I was working on my gateway I noticed that stations use a 44-address as their external address.
For some time there has been the gateway to 44.24.240/20 with gateway 44.24.221.1
This morning I noticed gateways with address 44.151.94.28 and 44.140.0.1 but they have been removed
in the meantime.
I want to notice that my gateway cannot route traffic to gateways like that, due to the policy routing used
to separate internet traffic and tunnel traffic. And I think that many other gateways have a similar setup
and have the same problem.
Is there any official policy on the external gateway address? Is it allowed to be in net-44, and if not, wouldn't
it be better to check this in the portal and reject submissions like this with a suitable error message?
I suspect part of those entries are just the result of misunderstanding by a newcomer, and we help them
getting things working by hinting at this incorrect configuration.
Rob
