Date: Wed, 20 Mar 2002 14:16:50 -0500 From: Alan Clegg <alan@clegg.com> To: freebsd-stable@FreeBSD.ORG Subject: Re: wi broken? Message-ID: <20020320141650.A62086@shell.wetworks.org> In-Reply-To: <20020318.182844.22165854.imp@village.org>; from imp@village.org on Mon, Mar 18, 2002 at 06:28:44PM -0700 References: <001201c1cd52$76ecb040$0600a8c0@mars> <200203182127.g2ILRDY70537@ambrisko.com> <20020318.182844.22165854.imp@village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Unless the network is lying to me again, M. Warner Losh said: > : | I read where others have had to do a "ifconfig fxp0 down" first before > : | they can bring their wi devices up, but "ifconfig rl0 down" didn't work > : | for me. When I try to invoke dhclient on wi0, I immediately get this: > : | > : | ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address > : I think this all due to the change in sys/netinet/in.c. Try to use > : version 1.44.2.7 and see if it fixes this. This commit also broke > : kernel BOOTP/DHCP configuration. Maybe this need code needs to > : verify that the duplicate 0.0.0.0 addresses are okay and not report > : an error. If it does you might want to ping the authors of the commit. > > I have verified that ed and ep have similar problems in -stable. > Likely it is this change. I think we should back it out in -current > and in -stable personally, but haven't had time to pursue it. I can confirm that after going back to 1.44.2.7 on in.c and being up-to-date on if_wi.c, I no-longer have the DHCP problems, nor the interface hangs that I had previously. AlanC [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8mOAiyJP8xSfQVdsRAmVjAJ9YknDyd3e4+Ksepyu+lsFjubTwewCdEpHZ Yv2RTSkZelmyu0S2vEWu5Ew= =qahN -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020320141650.A62086>