Date: Fri, 12 Mar 2004 11:51:03 -0800 (PST) From: wpaul@FreeBSD.ORG (Bill Paul) To: jbarrett@amduat.net (Jacob S. Barrett) Cc: freebsd-mobile@freebsd.org Subject: Re: More TrueMobile 1300 Message-ID: <20040312195103.A034716A4CF@hub.freebsd.org> In-Reply-To: <51367.63.115.16.66.1079120307.squirrel@www.amduat.net> from "Jacob S. Barrett" at "Mar 12, 2004 11:38:27 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> > You don't show what command(s) you typed to initialize the interface.
> > You also don't say what kind of AP you're trying to associate with.
>
> I used:
> ifconfig ndis0 ssid xxx wepmode on wepkey xxxxx up
> which is the same as I use on my wi card:
> ifconfig wi0 ssid xxx wepmode on wepkey xxxxx up
>
> I have tried this with a Linksys WAP11v2 and Nokia A032 AP.
It could be something to do with the wepkey not being programmed
correctly. I usually specify my WEP keys as hex strings. Couple things
I would test:
- disable WEP on the AP temporarily (if you can) and see if it will
associate then
- use 'media autoselect' with the rest of your ifconfig options
- after a few seconds, do 'ifconfig ndis0 up' or 'ifconfig ndis0
ssid xxx' a couple of times (setting the ssid is supposed to
cause the driver to re-attempt to associate).
-Bill
--
=============================================================================
-Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu
wpaul@windriver.com | Wind River Systems
=============================================================================
<adamw> you're just BEGGING to face the moose
=============================================================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040312195103.A034716A4CF>