There are actually several instances where there is an encap route for a /16 and then there are some /28s or /29s nested inside it.
BGP-only subnets aren't in the encap file.
Our BGP-routed /16 is in the encap file as well, for compatibility with gateway stations that cannot send their net-44 traffic over internet due to source address filtering, or that are otherwise configured in such a way that net-44 traffic is never sent to internet directly.
So we are one of those /16 networks with several small networks and single addresses inside it routed to different gateways. I don't know if the other instances are a result of the same setup.
Good to hear that those are properly handled.
Rob
Rob,
- Are you saying that some AMPRNet OPs simply forward packets to their WAN interface...WITH INVALID SRC IPs from their 44.0.0.0/8 RANGE?!?!
Can someone share a configuration with me where this actually works! I've always understood it to be - at minimum - a poor configuration, and - at most - an invalid configuration, to use Public IP space not assigned to the interface in use.
- How does the traffic return?
- If it's via a tunnel, why are they dropping the packets on the WAN interface, without the proper WAN IP address, couldn't they just properly configure an IPENCAP tunnel?
- Lynwood KB3VWG
"for compatibility with gateway stations that cannot send their net-44 traffic over internet due to source address filtering, or that are otherwise configured in such a way that net-44 traffic is never sent to internet directly."
-
lleachii＠aol.com -
Rob Janssen