| commit | 4e7b2f1454382b220f792a7fbcbebd0985187161 | |
| author | Benjamin LaHaise <bcrl@kvack.org> | |
| Tue, 27 Mar 2012 15:55:32 +0000 (27 15:55 +0000) | ||
| committer | David S. Miller <davem@davemloft.net> | |
| Wed, 28 Mar 2012 08:45:37 +0000 (28 04:45 -0400) | ||
| tree | c0161155b8d2dc170ee3727c4b4cd99302f41379 | treesnapshot (tar.gz zip) |
| parent | 2e57b79ccef1ff1422fdf45a9b28fe60f8f084f7 | commitdiff |
net/ipv4: fix IPv4 multicast over network namespaces
When using multicast over a local bridge feeding a number of LXC guests
using veth, the LXC guests are unable to get a response from other guests
when pinging 224.0.0.1. Multicast packets did not appear to be getting
delivered to the network namespaces of the guest hosts, and further
inspection showed that the incoming route was pointing to the loopback
device of the host, not the guest. This lead to the wrong network namespace
being picked up by sockets (like ICMP). Fix this by using the correct
network namespace when creating the inbound route entry.
Signed-off-by: Benjamin LaHaise <bcrl@kvack.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
When using multicast over a local bridge feeding a number of LXC guests
using veth, the LXC guests are unable to get a response from other guests
when pinging 224.0.0.1. Multicast packets did not appear to be getting
delivered to the network namespaces of the guest hosts, and further
inspection showed that the incoming route was pointing to the loopback
device of the host, not the guest. This lead to the wrong network namespace
being picked up by sockets (like ICMP). Fix this by using the correct
network namespace when creating the inbound route entry.
Signed-off-by: Benjamin LaHaise <bcrl@kvack.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
| net/ipv4/route.c | diffblobblamehistory |