2 ms·
It's a routing behavior that is valid for non-VPN interfaces but bogus for VPNs, and it's this intersection of routing behavior and expected VPN behavior where
by loeg 7y ago
It's a routing behavior that is valid for non-VPN interfaces but bogus for VPNs, and it's this intersection of routing behavior and expected VPN behavior where there is a gap. So it's not a particular VPN issue or even a routing bug, exactly. My hypothesis is that routing layers need to allow VPNs to register/reserve interface addresses as "I'm a VPN, drop bogons," and that then VPN software should use these APIs. But I'm no expert in either field, so take that with a huge grain of salt.