fix: fix reverse routing for KubeSpan
This allows it to not come down when rp_filter is enabled. Fixes #9814
Signed-off-by: Dmitry Sharshakov [email protected]
chain kubespan_prerouting { # handle 50
type filter hook prerouting priority filter; policy accept;
meta mark & 0x00000060 == 0x00000020 accept # handle 51
ip daddr { 172.20.0.3-172.20.0.4 } meta mark set meta mark & 0xffffffdf | 0x00000040 accept # handle 53
ip6 daddr { fdbd:f075:61fa:5502:2c26:e0ff:fe99:e2a4, fdbd:f075:61fa:5502:e88a:18ff:fed2:32f3 } meta mark set meta mark & 0xffffffdf | 0x00000040 accept # handle 55
meta mark & 0x00000040 == 0x00000040 ip saddr != { 172.20.0.3-172.20.0.4 } meta mark set meta mark ^ 0x00000040 accept # handle 57
meta mark & 0x00000040 == 0x00000040 ip6 saddr != { fdbd:f075:61fa:5502:2c26:e0ff:fe99:e2a4, fdbd:f075:61fa:5502:e88a:18ff:fed2:32f3 } meta mark set meta mark ^ 0x00000040 accept # handle 59
iifname "kubespan" meta mark set meta mark & 0xffffffdf | 0x00000040 accept # handle 60
}
chain kubespan_prerouting { # handle 50
type filter hook prerouting priority filter; policy accept;
meta mark & 0x00000060 == 0x00000020 accept # handle 51
ip daddr { 172.20.0.2, 172.20.0.4 } meta mark set meta mark & 0xffffffdf | 0x00000040 accept # handle 53
ip6 daddr { fdbd:f075:61fa:5502:5cd0:eff:fea3:252f, fdbd:f075:61fa:5502:e88a:18ff:fed2:32f3 } meta mark set meta mark & 0xffffffdf | 0x00000040 accept # handle 55
meta mark & 0x00000040 == 0x00000040 ip saddr != { 172.20.0.2, 172.20.0.4 } meta mark set meta mark ^ 0x00000040 accept # handle 57
meta mark & 0x00000040 == 0x00000040 ip6 saddr != { fdbd:f075:61fa:5502:5cd0:eff:fea3:252f, fdbd:f075:61fa:5502:e88a:18ff:fed2:32f3 } meta mark set meta mark ^ 0x00000040 accept # handle 59
iifname "kubespan" meta mark set meta mark & 0xffffffdf | 0x00000040 accept # handle 60
}
This PR is stale because it has been open 45 days with no activity.
Did this get fixed?
Did this get fixed?
kube-router was updated to be less agressive about rpfilter, so it "just works" now. this PR hasn't been finished.
If it works with kube-router now is this PR still needed?
If it works with kube-router now is this PR still needed?
yes, otherwise we would have closed it
enabling rp_filter by default would be nice as a feature
maybe this could fix #11244 idk
This PR is stale because it has been open 45 days with no activity.
no stale
This PR is stale because it has been open 45 days with no activity.
no stale
This PR is stale because it has been open 45 days with no activity.
no stale