Date: Mon, 06 Feb 2006 17:47:20 +0100 From: "[LoN]Kamikaze" <LoN_Kamikaze@gmx.de> To: Freddie Cash <fcash@ocis.net> Cc: freebsd-mobile@freebsd.org Subject: Re: WEP not working Message-ID: <43E77D98.2010602@gmx.de> In-Reply-To: <200602060830.27122.fcash@ocis.net> References: <3cc1a1cc0602051238q58d4653y@mail.gmail.com> <43E71686.50005@gmx.de> <200602060830.27122.fcash@ocis.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig46304881715E87BDE36CCAED Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable It might work for you, but it sure doesn't for me. Wpa_supplicant establishs a connection to the AP, but dhclient fails to receive an IP. If I don't use wpa_supplicant and just type # ifconfig ipw0 ssid myap wepkey 0x01234567890123456789012345 weptxkey 1 wepmode on # dhclient ipw0 it works. I know what wpa_supplicant is, but for me it doesn't do what it should. That is why I wrote my own daemon. Freddie Cash wrote: > On Monday 06 February 2006 01:27 am, [LoN]Kamikaze wrote: >> Dhclient does not work through wpa_supplicant when the connection has >> been established with WEP encryption. You can hand connect without >> wpa_supplicant and dhclient will most likely succeed. >=20 > dhclient works just fine in conjunction with wpa_supplicant. I find it= to=20 > be a lot easier to do with wpa_supplicant, as you can put all the=20 > wireless config info (ssid, channel, wep mode, wep key, etc) into a=20 > single file, and edit /etc/rc.conf to use ifconfig_ath0=3D"WPA DHCP" an= d=20 > have the rc scripts take care of everything automatically. >=20 > wpa_supplicant.conf support no-encryption, wep, wpa, wpa-psk, wpa-eapol= ,=20 > and a few others. >=20 > DHCP support is separate from the wireless link support, same as DHCP=20 > support is separate from wired link support. Once devd sees the link u= p=20 > event from the NIC driver, it starts dhclient on that interface. How=20 > that link up even is generated does not really matter. >=20 >> If you wish I can send you my self-brewed daemon to automatically >> establish connections. It doesn't support wpa, though. >=20 > wpa_supplicant is a daemon that handle no-encryption, wep, and wpa=20 > connections, automatically for you. And it comes free with FreeBSD 6+,= =20 > and as a port in 5.x. >=20 --------------enig46304881715E87BDE36CCAED Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD532gfMDIb41/+S0RAhyrAJ9XOw4v3Ivgz17dsA6F4LBoxuaP2ACfVPmo eObYmme+Wpio/9X4BJd23qA= =m7RY -----END PGP SIGNATURE----- --------------enig46304881715E87BDE36CCAED--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43E77D98.2010602>