From: Ben Greear <greearb@candelatech.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: IPv4 multicast and mac-vlans acting weird on 3.0.4+
Date: Wed, 05 Oct 2011 13:09:52 -0700 [thread overview]
Message-ID: <4E8CB990.1010406@candelatech.com> (raw)
In-Reply-To: <1317844449.3457.3.camel@edumazet-laptop>
On 10/05/2011 12:54 PM, Eric Dumazet wrote:
> Le mercredi 05 octobre 2011 à 09:46 -0700, Ben Greear a écrit :
>> This is on a hacked 3.0.4 kernel...
>>
>> I am seeing an issue where an IPv4 mcast receiver will not receive
>> a 1473 or larger byte mcast message, but will receive a 1472. The difference
>> being that 1473 ends up being two packets on the wire. It works on
>> 802.1Q VLANs, VETH interfaces and real Ethernet. It does not work
>> on a mac-vlan hanging off the VETH.
>>
>> I see packets received on the macvlan in tshark, and they appear correct. No
>> obvious errors in the macvlan port stats or netstat -s,
>> and the 'ss' tool doesn't appear to support UDP sockets at all.
>>
>> So, I'm about to go digging into the code, but if anyone has any
>> suggestions for places to look, please let me know!
>>
>
> Well, problem is defragmentation and macvlan cooperation.
>
> Multicast messages are broadcasted on all macvlan ports.
>
> But IP defrag will probably deliver a single final frame.
>
> We probably need to handle defrag in macvlan before broadcasting to all
> ports.
I see packets get to this code in ip_input.c (line 467 or so),
and that printk is mine of course.
if ((dev && strcmp(dev->name, "rddVR10#0") == 0) ||
(dev && strcmp(dev->name, "rddVR10") == 0)) {
printk("calling ip_rcv_finish through NF_HOOK, dev: %s, len: %i\n",
dev->name, skb->len);
}
return NF_HOOK(NFPROTO_IPV4, NF_INET_PRE_ROUTING, skb, dev, NULL,
ip_rcv_finish);
But, the macvlan packets never make it to the ip_rcv_finish method.
I do see a big and a little packet entering this code.
I have no firewall rules that I'm aware of, though there
is some conn-track logic (though not associated with the
mac-vlan interface):
[root@lec2010-ath9k-1 ~]# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
And, I just reproduced the problem on vanilla linus top-of-tree (3.1.0-rc9).
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-10-05 20:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 16:46 IPv4 multicast and mac-vlans acting weird on 3.0.4+ Ben Greear
2011-10-05 19:54 ` Eric Dumazet
2011-10-05 20:09 ` Ben Greear [this message]
2011-10-05 20:17 ` Eric Dumazet
2011-10-05 20:19 ` Ben Greear
2011-10-05 20:31 ` Eric Dumazet
2011-10-05 20:56 ` Ben Greear
2011-10-05 21:36 ` Eric Dumazet
2011-10-05 21:52 ` Ben Greear
2011-10-05 22:35 ` Ben Greear
2011-10-06 20:28 ` [PATCH net-next] macvlan: handle fragmented multicast frames Eric Dumazet
2011-10-07 16:44 ` Ben Greear
2011-10-10 16:27 ` Ben Greear
2011-10-10 16:41 ` Eric Dumazet
2011-10-10 16:53 ` Ben Greear
2011-10-19 3:22 ` David Miller
2011-10-06 20:42 ` IPv4 multicast and mac-vlans acting weird on 3.0.4+ Eric Dumazet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E8CB990.1010406@candelatech.com \
--to=greearb@candelatech.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).