sit: allow encapsulated IPv6 traffic to be delivered locally
Subsystems (2)
PATCH 1/1 sit: allow encapsulated IPv6 traffic to be delivered locally
While experimenting with FOU encapsulation Amir noticed that encapsulated IPv6 traffic fails to be delivered, if the peer IP address is configured locally.
It can be easily verified by creating a sit interface like below:
$ sudo ip link add name fou_test type sit remote 127.0.0.1 encap fou encap-sport auto encap-dport 1111 $ sudo ip link set fou_test up
and sending some IPv4 and IPv6 traffic to it
$ ping -I fou_test -c 1 1.1.1.1 $ ping6 -I fou_test -c 1 fe80::d0b0:dfff:fe4c:fcbc
"tcpdump -i any udp dst port 1111" will confirm that only the first IPv4 ping was encapsulated and attempted to be delivered.
This seems like a limitation: for example, in a cloud environment the "peer" service may be arbitrarily scheduled on any server within the cluster, where all nodes are trying to send encapsulated traffic. And the unlucky node will not be able to. Moreover, delivering encapsulated IPv4 traffic locally is allowed.
But I may not have all the context about this restriction and this code predates the observable git history.
--- net/ipv6/sit.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/ipv6/sit.c +1 -1
@@ -956,7 +956,7 @@ static netdev_tx_t ipip6_tunnel_xmit(struct sk_buff *skb,dst_cache_set_ip4 (&tunnel->dst_cache, &rt->dst, fl4.saddr); } -if (rt->rt_type !=RTN_UNICAST ) { +if (rt->rt_type !=RTN_UNICAST && rt->rt_type !=RTN_LOCAL ) {ip_rt_put (rt); dev->stats.tx_carrier_errors++; goto tx_error_icmp;
Signature · 1 line
2.20.1
Quoted 35 lines · Ignat Korchagin
While experimenting with FOU encapsulation Amir noticed that encapsulated IPv6 traffic fails to be delivered, if the peer IP address is configured locally.
It can be easily verified by creating a sit interface like below:
$ sudo ip link add name fou_test type sit remote 127.0.0.1 encap fou encap-sport auto encap-dport 1111 $ sudo ip link set fou_test upand sending some IPv4 and IPv6 traffic to it
$ ping -I fou_test -c 1 1.1.1.1 $ ping6 -I fou_test -c 1 fe80::d0b0:dfff:fe4c:fcbc"tcpdump -i any udp dst port 1111" will confirm that only the first IPv4 ping was encapsulated and attempted to be delivered.
This seems like a limitation: for example, in a cloud environment the "peer" service may be arbitrarily scheduled on any server within the cluster, where all nodes are trying to send encapsulated traffic. And the unlucky node will not be able to. Moreover, delivering encapsulated IPv4 traffic locally is allowed.
But I may not have all the context about this restriction and this code predates the observable git history.
Reported-by Amir Razmjou <[email protected]>Signed-off-by Ignat Korchagin <[email protected]>--- net/ipv6/sit.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)net/ipv6/sit.c +0
-0
net/ipv6/sit.c static netdev_tx_t ipip6_tunnel_xmit(struct sk_buff *skb, · line 962
Quoted 8 lines
net/ipv6/sit.c +1
-1@@ -956,7 +956,7 @@ static netdev_tx_t ipip6_tunnel_xmit(struct sk_buff *skb,dst_cache_set_ip4 (&tunnel->dst_cache, &rt->dst, fl4.saddr); } -if (rt->rt_type !=RTN_UNICAST ) { +if (rt->rt_type !=RTN_UNICAST && rt->rt_type !=RTN_LOCAL ) {ip_rt_put (rt); dev->stats.tx_carrier_errors++; goto tx_error_icmp;
Quoted 22 lines · On Wed, 12 Jan 2022 12:59:37 -0700 David Ahern wrote:
Quoted 21 lines · Ignat Korchagin
While experimenting with FOU encapsulation Amir noticed that encapsulated IPv6 traffic fails to be delivered, if the peer IP address is configured locally.
It can be easily verified by creating a sit interface like below:
$ sudo ip link add name fou_test type sit remote 127.0.0.1 encap fou encap-sport auto encap-dport 1111 $ sudo ip link set fou_test upand sending some IPv4 and IPv6 traffic to it
$ ping -I fou_test -c 1 1.1.1.1 $ ping6 -I fou_test -c 1 fe80::d0b0:dfff:fe4c:fcbc"tcpdump -i any udp dst port 1111" will confirm that only the first IPv4 ping was encapsulated and attempted to be delivered.
This seems like a limitation: for example, in a cloud environment the "peer" service may be arbitrarily scheduled on any server within the cluster, where all nodes are trying to send encapsulated traffic. And the unlucky node will not be able to. Moreover, delivering encapsulated IPv4 traffic locally is allowed.
Quoted 7 lines
Quoted 5 lines
But I may not have all the context about this restriction and this code predates the observable git history.
Reported-by Amir Razmjou <[email protected]>Signed-off-by Ignat Korchagin <[email protected]>Reviewed-by David Ahern <[email protected]>
Applied, thanks!