Date: Tue, 22 Jan 2002 17:37:07 -0800 From: Eli Dart <dart@nersc.gov> To: "Kevin Oberman" <oberman@ptavv.es.net> Cc: freebsd-net@freebsd.org Subject: Re: IP multicast time and dhcp Message-ID: <20020123013707.3A2773B1A3@gemini.nersc.gov> In-Reply-To: Message from "Kevin Oberman" <oberman@ptavv.es.net> of "Tue, 22 Jan 2002 17:10:35 PST." <20020123011035.818B95D0A@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_189477153P Content-Type: text/plain; charset=us-ascii In reply to "Kevin Oberman" <oberman@ptavv.es.net> : > > Date: Tue, 22 Jan 2002 14:31:43 -0800 > > From: Eli Dart <dart@nersc.gov> > > Sender: owner-freebsd-net@FreeBSD.ORG > > > > I have a laptop (FreeBSD-4.2-R) that spends a lot of it's time > > disconnected from the network. When I do want to connect it, I kick > > off dhclient -- works fine. > > 4.2? Come on, Eli. 4.5 should be out in a week and pccard support > is one area that has seen vast improvement since 4.2 came out. (Most > were in 4.4, although a few things have been done since then.) No pccard stuff here. This is on the built-in fxp interface. It behaves like any other hard-wired ethernet interface, and does not seem to suffer from the recent problems with newer fxp chipsets. > Just a guess, but I suspect that the receive address hashes are not > getting properly set up for multicast when the card is connected to a > running system. > > To receive traffic for MAC addresses other than the native one, most > cards use a hashed table of addresses to recognize and I suspect that > it is only initialized at the initial multicast setup. If the card can't be > set at this time, maybe it never is. Hmmm.....some more info: Here are the syslog messages when ntpd kicks off..... note the failure of the setsockopt() call. Jan 22 17:24:43 lart ntpd[116]: ntpd 4.1.0 Fri Jan 11 13:10:27 PST 2002 (1) Jan 22 17:24:43 lart ntpd[116]: kernel time discipline status 2040 Jan 22 17:24:43 lart ntpd[116]: frequency initialized -141.220 from /etc/ntp.drift Jan 22 17:24:43 lart ntpd[116]: setsockopt IP_ADD_MEMBERSHIP fails: Can't assign requested address for 10100e0 / 0 (224.0.1.1) However, if I do a tcpdump on the now-configured interface, I see igmp queries from the router. The laptop just doesn't send a report, even though it's interested in multicast traffic (see netstat below): dart@laptop ~ >> netstat -naf inet Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp4 0 0 *.514 *.* LISTEN tcp4 0 0 *.21 *.* LISTEN udp4 0 0 *.68 *.* udp4 0 0 *.* *.* udp4 0 0 *.69 *.* udp4 0 0 224.0.1.1.123 *.* udp4 0 0 127.0.0.1.123 *.* udp4 0 0 *.123 *.* dart@laptop ~ >> Note that the igmp queries are sent to the multicast address 224.0.0.1, so the laptop is seeing multicast traffic. The kernel just seems to think that it doesn't have any multicast groups that it cares about. As for OS versions, I'm waiting for 4.5 :) If this should wait till then, I'm happy to table it for a bit..... --eli --==_Exmh_189477153P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: This is a comment. iD8DBQE8ThPDLTFEeF+CsrMRArpaAKDOYjsJEkTfmCJR5Ci2g1wswUsMRQCeJZAx T5ZOBn/pz7l6lhMOVmfuRPA= =l+00 -----END PGP SIGNATURE----- --==_Exmh_189477153P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020123013707.3A2773B1A3>