[EMAIL PROTECTED] writes: > sldn2302xap -> 224.0.0.22 IGMP v3 membership report > 139.149.66.1 -> 224.0.0.1 IGMP v2 membership query <= Here's
There's a bit of detail missing here. What's the address of 'sldn2302xap'? Is it on the same subnet as the others that are working? I also don't see any message from the s10 system captured after the v2 query. Nor do I see the query (if any) that caused that membership report. Does it switch to v2 or not? > The address 139.149.66.1 is the firewall's virtual IP connecting the > VLAN on which our servers connect. As you can see the IGMP v2 membership > query is going out correctly to 224.0.0.1 (all hosts) from the firewall > and a number of servers respond on IGMP v2 but not the Sol 10 server. Assuming the S10 system can actually see that IGMPv2 query and that it doesn't switch to v2, that sounds like a bug. Since this is S10, and thus _not_ Open Solaris, you should report that to your Sun support folks. If it does the same thing on Nevada, then this is the right place to discuss it. > IGMP: > 56 messages received > 0 messages received with too few bytes > 0 messages received with bad checksum > 0 membership queries received > 0 membership queries received with invalid field(s) That looks pretty clear. It can't see the queries. The next question is "why." I'd probably start by looking at the snoop traces to see if the packets are correctly formed. Then I'd turn up ip_debug with ndd and watching the console. Dtrace is probably the next step. > The stats above show that the host is not recognising the IGMPv2 > queries, assuming this is working since the count for "membership > queries received" is zero. Yes. > Are there any bugs or configurations that may explain why this server > appears to respond with IGMPv3. None that I know of. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
