Date: Mon, 18 Mar 2002 18:28:44 -0700 (MST) From: "M. Warner Losh" <imp@village.org> To: ambrisko@ambrisko.com Cc: morgan.davis@hosting.com, freebsd-stable@FreeBSD.ORG Subject: Re: wi broken? Message-ID: <20020318.182844.22165854.imp@village.org> In-Reply-To: <200203182127.g2ILRDY70537@ambrisko.com> References: <001201c1cd52$76ecb040$0600a8c0@mars> <200203182127.g2ILRDY70537@ambrisko.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <200203182127.g2ILRDY70537@ambrisko.com>
Doug Ambrisko <ambrisko@ambrisko.com> writes:
: Morgan Davis writes:
: | After updating to the latest -STABLE as of 3/6/2002, wi refused to work
: | anymore. I updated my kernel as of 4:30PM PST today since wi_if.c was
: | changed. Still, no good. Relevant networking details on my system:
: |
: | FreeBSD 4.5-STABLE #0: Sat Mar 16 16:32:51 PST 2002
: |
: | wi0: <PRISM2STA PCI WaveLAN/IEEE 802.11> port
: | 0xdc00-0xdc3f,0xd800-0xd87f mem 0xde000000-0xde000fff irq 10 at device
: | 10.0 on pci0
: | wi0: 802.11 address: 00:90:d1:07:3b:61
: | wi0: using RF:PRISM2 MAC:HFA3841 CARD:HWB3163 rev.A, Firmware: 0.7
: | variant 6
: | rl0: <RealTek 8139 10/100BaseTX> port 0xe000-0xe0ff mem
: | 0xde001000-0xde0010ff irq 11 at device 12.0 on pci0
: | rl0: Ethernet address: 00:30:1b:07:63:76
: | miibus0: <MII bus> on rl0
: | rlphy0: <RealTek internal media interface> on miibus0
: | rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
: |
: | 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
: |
: | ...and it never does communicate with the DHCP server. All the
: | wicontrol details appear to be correct.
: |
: | How can I help debug this?
:
: 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.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020318.182844.22165854.imp>