Re: [PATCH net-next] ipv6: Don't use dst gateway directly in ip6_confirm_neigh()

2019-09-11 Thread David Miller
From: Stefano Brivio Date: Mon, 9 Sep 2019 22:44:06 +0200 > This is the equivalent of commit 2c6b55f45d53 ("ipv6: fix neighbour > resolution with raw socket") for ip6_confirm_neigh(): we can send a > packet with MSG_CONFIRM on a raw socket for a connected route, so the > gateway would be :: here

Re: [PATCH net-next] ipv6: Don't use dst gateway directly in ip6_confirm_neigh()

2019-09-11 Thread Nicolas Dichtel
Le 09/09/2019 à 22:44, Stefano Brivio a écrit : > This is the equivalent of commit 2c6b55f45d53 ("ipv6: fix neighbour > resolution with raw socket") for ip6_confirm_neigh(): we can send a > packet with MSG_CONFIRM on a raw socket for a connected route, so the > gateway would be :: here, and we shou

Re: [PATCH net-next] ipv6: Don't use dst gateway directly in ip6_confirm_neigh()

2019-09-10 Thread Guillaume Nault
On Mon, Sep 09, 2019 at 10:44:06PM +0200, Stefano Brivio wrote: > This is the equivalent of commit 2c6b55f45d53 ("ipv6: fix neighbour > resolution with raw socket") for ip6_confirm_neigh(): we can send a > packet with MSG_CONFIRM on a raw socket for a connected route, so the > gateway would be :: h

[PATCH net-next] ipv6: Don't use dst gateway directly in ip6_confirm_neigh()

2019-09-09 Thread Stefano Brivio
This is the equivalent of commit 2c6b55f45d53 ("ipv6: fix neighbour resolution with raw socket") for ip6_confirm_neigh(): we can send a packet with MSG_CONFIRM on a raw socket for a connected route, so the gateway would be :: here, and we should pick the next hop using rt6_nexthop() instead. This