Route #3 - USB 802.11 a/b/g

Jim Stapleton stapleton.41 at gmail.com
Sun Oct 15 15:45:32 PDT 2006


On 10/8/06, Jim Stapleton <stapleton.41 at gmail.com> wrote:
> On 10/8/06, Sam Leffler <sam at errno.com> wrote:
> > Jim Stapleton wrote:
> > > On 10/7/06, Lars Engels <lars.engels at 0x20.net> wrote:
> > >> On Fri, Oct 06, 2006 at 07:22:50PM -0400, Jim Stapleton wrote:
> > >> > OK, that's interesting, I tried, that, and got this:
> > >> >
> > >> > ural0:
> > >> flags=108843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NEEDSGIANT> mtu
> > >> > 1500
> > >> >        inet6 fe80::215:e9ff:fe2d:72c3%ural0 prefixlen 64 scopeid 0x4
> > >> >        inet 192.168.1.84 netmask 0xffffff00 broadcast 49.49.253.171
> > >> >        ether 00:15:e9:2d:72:c3
> > >> >        media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps (OFDM/54Mbps)
> > >> >        status: no carrier
> > >> >        ssid mine channel 6
> > >> >        authmode OPEN privacy ON deftxkey 1 txpowmax 100 protmode CTS
> > >> >        bintval 100
> > >> >
> > >> > I've tried replacing wep with wepkey, I've tried weptxkey 1 to 4, no
> > >> > luck on any of those.
> > >> >
> > >> > Any other suggestions?
> > >> >
> > >>
> > >> Perhaps the authmode needs to be set to SHARED?
> > >>
> > >
> > > That didn't work either -- I also tried 8021x and wpa. Both gave me an
> > > error:
> > > ifconfig: SIOCS80211: invalid argument
> >
> > "status: no carrier" means you are not associated to the ap.  When the
> > reason is not obvious I usually do this:
> >
> > wlandebug -i ural0 scan+auth+assoc
> >
> > before bringing the interface up w/ ifconfig.  The console msgs should
> > tell you what's going on.  I don't recall if "ifconfig ural0 debug" will
> > give you similar info.
> >
> > Of course it'd be better if the failure code for the last auth/assoc
> > attempt was reported by ifconfig in this situation (I think it's
> > available by ioctl but can't recall--if not it's easy to add and has
> > been done for other systems).
> >
> >         Sam
> >
> > PS. wlandebug is in src/tools/tools/net80211.
> >
>
>
> well, it gave me something that is probably useful - but I've no idea
> how to use it.
>
> sjss at aragorn 16:17:27 (0) ~ > sudo wlandebug -i ural0 scan+auth+assoc
> net.wlan.1.debug: 0x0 => 0xe00000<assoc,auth,scan>
>
>
> there was no other output. Nothing appeared in dmesg
>
> thanks,
> -Jim Stapleton
>

addendum: I found a way to get by this problem - it only seems to fail
when the mouse is plugged in before the drive, if I plug in the mouse
first, the drive fails. I have verified this with anouth drive. This
only happens when the mouse is plugged in directly, if the mouse is
plugged in via a KVM (as it would be at home), the problem is not
observed.

-Jim Stapleton


More information about the freebsd-questions mailing list