Re: [PATCH net v2 0/2] pv6: fix sticky pktinfo behaviour

2016-01-29 Thread David Miller
From: Paolo Abeni Date: Fri, 29 Jan 2016 12:30:18 +0100 > Currently: > > ip addr add dev eth0 2001:0010::1/64 > ip addr add dev eth1 2001:0020::1/64 > ping6 -I eth0 2001:0020::2 > > do not lead to the expected results, i.e. eth1 is used as the > egress interface. > > This is due to two related

Re: [PATCH net v2 0/2] pv6: fix sticky pktinfo behaviour

2016-01-29 Thread Hannes Frederic Sowa
On 29.01.2016 12:30, Paolo Abeni wrote: The kernel has never enforced the egress interface specified via the sticky pktinfo, except briefly between the commits 741a11d9e410 ("net: ipv6: Add RT6_LOOKUP_F_IFACE flag if oif is set") and d46a9d678e4c ("net: ipv6: Dont add RT6_LOOKUP_F_IFACE flag if s

[PATCH net v2 0/2] pv6: fix sticky pktinfo behaviour

2016-01-29 Thread Paolo Abeni
Currently: ip addr add dev eth0 2001:0010::1/64 ip addr add dev eth1 2001:0020::1/64 ping6 -I eth0 2001:0020::2 do not lead to the expected results, i.e. eth1 is used as the egress interface. This is due to two related issues in handling sticky pktinfo, used by ping6 to enforce the device bindin