nanog mailing list archives
Re: Issue with point to point VPNs behind NAT and asymmetric traffic
From: Grant Taylor via NANOG <nanog () nanog org>
Date: Sat, 15 Jun 2019 15:34:47 -0600
On 6/15/19 2:06 PM, William Herrin wrote:
This is probably enabled on one or both ends: http://tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.kernel.rpf.html
Do some distros enable this now? I thought it was disabled by default.
Disable it.
Or make sure it's using loose (2) filtering. rp_filter - INTEGER 0 - No source validation.1 - Strict mode as defined in RFC3704 Strict Reverse Path Each incoming packet is tested against the FIB and if the interface is not the best reverse path the packet check will fail. By default failed packets are discarded. 2 - Loose mode as defined in RFC3704 Loose Reverse Path Each incoming packet's source address is also tested against the FIB and if the source address is not reachable via any interface the packet check will fail.
-- Grant. . . . unix || die
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
Current thread:
- Issue with point to point VPNs behind NAT and asymmetric traffic Anurag Bhatia (Jun 12)
- Re: Issue with point to point VPNs behind NAT and asymmetric traffic blakangel (Jun 12)
- Re: Issue with point to point VPNs behind NAT and asymmetric traffic Ross Tajvar (Jun 12)
- Re: Issue with point to point VPNs behind NAT and asymmetric traffic Anurag Bhatia (Jun 15)
- RE: Issue with point to point VPNs behind NAT and asymmetric traffic Jerry Cloe (Jun 12)
- Re: Issue with point to point VPNs behind NAT and asymmetric traffic Anurag Bhatia (Jun 26)
- Re: Issue with point to point VPNs behind NAT and asymmetric traffic Grant Taylor via NANOG (Jun 12)
- Re: Issue with point to point VPNs behind NAT and asymmetric traffic William Herrin (Jun 15)
- Re: Issue with point to point VPNs behind NAT and asymmetric traffic Grant Taylor via NANOG (Jun 15)