Date: Fri, 22 Jul 2005 01:22:24 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Kevin Oberman <oberman@es.net> Cc: freebsd-current@freebsd.org Subject: Re: More wi odd behavior Message-ID: <20050722012111.P16902@fledge.watson.org> In-Reply-To: <20050721183852.074415D07@ptavv.es.net> References: <20050721183852.074415D07@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 21 Jul 2005, Kevin Oberman wrote: > # ifconfig wi0 > wi0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 > inet6 fe80::205:3cff:fe03:86b9%wi0 prefixlen 64 scopeid 0x3 > inet 142.231.19.178 netmask 0xfffffe00 broadcast 142.231.19.255 > ether 00:05:3c:03:86:b9 > # wicontrol > wicontrol: SIOCGWAVELAN: Operation not supported by device > # dhclient wi0 > ifconfig: ioctl (SIOCAIFADDR): Operation not supported by device > wi0: not found If you dmesg, is there a partial driver detach? I saw that problem fairly frequently when I was using WEP a few months ago, but haven't seen it recently. At some point it seemed like the driver got upset and basically detatched or partially detached. Ejecting and re-inserting "fixed" the problem. Robert N M Watson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050722012111.P16902>