[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <OF2A1B6BCC.6EDD542B-ON88257412.005C674C-88257412.005EEFF4@us.ibm.com>
Date: Thu, 20 Mar 2008 10:17:02 -0700
From: David Stevens <dlstevens@...ibm.com>
To: Glen Gray <glen.gray@...cor.com>
Cc: netdev@...r.kernel.org, netdev-owner@...r.kernel.org,
Francois Romieu <romieu@...zoreil.com>
Subject: Re: r8169 driver fails to see IGMPv2 SAP announcements
> The SAP announcements are made via IGMPv2, however the eth0 device
> comes up as IGMPv3 and so doesn't pick up the announcements. I've used
> the proc interface force_igmp_version to set all devices to v2, but it
> doesn't seem to make any difference.
Glen,
I don't really know what you're reporting here. If by "doesn't
seem to make any difference" you mean that you still get v3 reports
when force_igmp_version=2, that would be news to me, and a packet
trace demonstrating that on a mainline kernel would be good.
If you mean it doesn't fix your data loss problem, then I'd
just conclude that the loss has nothing to do with IGMP reports.
I think the things of interest to look at are whether the
sender side is sending SAP announcements when the failure occurs and
whether the multicast router ever drops membership when you think
it shouldn't during a failure. You can use "tcpdump" on the sender
side to track these, and your multicast router may have some
logging capability to let you know state changes of interest. I
recommend looking at those (or posting here, size permitting) to
narrow down the problem.
+-DLS
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists