On Sunday 23 November 2008 11:05:40 Markos Chandras wrote:
> On Sunday 23 November 2008 01:14:41 John Blinka wrote:
> > I've recently subscribed to AT&T's u-verse which came with a
> > 2wire 3800hgv-b wireless gateway. On the windows side, my
> > dual-booting Dell laptop picked up the signal and connected
> > trivially. I've had no such success on the linux side.
> >
> > The gateway claims to use WPA-PSK authentication and TKIP
> > encryption. My supplicant.conf file looks like:
> >
> > ctrl_interface=/var/run/wpa_supplicant
> >
> > network={
> > ssid="my_ssid"
> > psk="my_password"
> > key_mgmt=WPA-PSK
> > proto=WPA
> > pairwise=TKIP
> > }
> >
> > wpa_gui provides the following information for a few seconds:
> >
> > adapter: ath0
> > network: 0: my_ssid
> > status: SCANNING
> > last message: Disconnect event - remove keys
> > authentication:
> > encryption:
> > ssid:
> > bssid:
> > ip address:
> >
> > then displays:
> >
> > adapter: ath0
> > network: 0: my_ssid
> > status: 4WAY_HANDSHAKE
> > last message: ASSOCIATED WITH 00:22:a4:0d:23:89
> > authentication: WPA-PSK
> > encryption: TKIP
> > ssid: my_ssid
> > bssid: 00:22:a4:0d:23:89
> > ip address:
> >
> > and then cycles between these two sets of information.
> >
> > I can't pretend that I understand what's going on, and I haven't
> > found any enlightenment in web searches. Does anyone know
> > what this means, where I'm stuck, and how to go forward?
> >
> > Thanks for any help,
> >
> > John Blinka
>
> I would suggest before trying the "hard way", to use Networkmanager and
> knetworkmanaget. If you have success with that, then you can try the other
> way
>
> Other wifi guis are wlassistant or wifiradar. Give them a try
Perhps you are authenticating but then not getting a dhcp address.
Try adding
modules=( "wpa_supplicant" )
wpa_supplicant_ath0="-Dmadwifi"
config_ath0=( "dhcp" )
to your /etc/conf.d/net file.
- noven
