* [PATCH ipv4 multicast] Fix IPv4 multicast over network namespaces
@ 2012-03-27 16:12 Benjamin LaHaise
2012-03-27 21:35 ` David Miller
0 siblings, 1 reply; 3+ messages in thread
From: Benjamin LaHaise @ 2012-03-27 16:12 UTC (permalink / raw)
To: David S. Miller; +Cc: netdev
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.
---
net/ipv4/route.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/net/ipv4/route.c b/net/ipv4/route.c
index 12ccf88..3b110a4 100644
--- a/net/ipv4/route.c
+++ b/net/ipv4/route.c
@@ -2042,7 +2042,7 @@ static int ip_route_input_mc(struct sk_buff *skb, __be32 daddr, __be32 saddr,
if (err < 0)
goto e_err;
}
- rth = rt_dst_alloc(init_net.loopback_dev,
+ rth = rt_dst_alloc(dev_net(dev)->loopback_dev,
IN_DEV_CONF_GET(in_dev, NOPOLICY), false);
if (!rth)
goto e_nobufs;
--
1.7.4.1
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH ipv4 multicast] Fix IPv4 multicast over network namespaces
2012-03-27 16:12 [PATCH ipv4 multicast] Fix IPv4 multicast over network namespaces Benjamin LaHaise
@ 2012-03-27 21:35 ` David Miller
2012-03-28 0:49 ` Benjamin LaHaise
0 siblings, 1 reply; 3+ messages in thread
From: David Miller @ 2012-03-27 21:35 UTC (permalink / raw)
To: bcrl; +Cc: netdev
From: Benjamin LaHaise <bcrl@kvack.org>
Date: Tue, 27 Mar 2012 12:12:28 -0400
> 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.
No signoff.
No proper subsystem prefix in Subject line (should be "ipv4: " here)
And third you've been warned about this repeatedly in your previous
patch postings.
Therefore I'm not applying this.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH ipv4 multicast] Fix IPv4 multicast over network namespaces
2012-03-27 21:35 ` David Miller
@ 2012-03-28 0:49 ` Benjamin LaHaise
0 siblings, 0 replies; 3+ messages in thread
From: Benjamin LaHaise @ 2012-03-28 0:49 UTC (permalink / raw)
To: David Miller; +Cc: netdev
On Tue, Mar 27, 2012 at 05:35:41PM -0400, David Miller wrote:
> No signoff.
My apologies. Doing this manually clearly isn't working, so I've switched
to a script to try to catch this.
> No proper subsystem prefix in Subject line (should be "ipv4: " here)
I'm trying to get this right, and it looks like I botched this again, for
that I am truely sorry.
-ben
> And third you've been warned about this repeatedly in your previous
> patch postings.
>
> Therefore I'm not applying this.
--
"Thought is the essence of where you are now."
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-03-28 0:49 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-03-27 16:12 [PATCH ipv4 multicast] Fix IPv4 multicast over network namespaces Benjamin LaHaise
2012-03-27 21:35 ` David Miller
2012-03-28 0:49 ` Benjamin LaHaise
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).