Date: Mon, 01 Aug 2005 20:34:51 -0700 From: Sam Leffler <sam@errno.com> To: Eric Schuele <e.schuele@computer.org> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: dhclient and wpa_supplicant Message-ID: <42EEE9DB.80408@errno.com> In-Reply-To: <42ECD7E7.3000801@computer.org> References: <42EAD325.60707@errno.com> <42EAD80C.9060707@errno.com> <42EBC41E.4070102@computer.org> <42EBC77F.1010601@errno.com> <42EBD3A0.5070407@computer.org> <42EBF80C.7030702@errno.com> <42ECD7E7.3000801@computer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Eric Schuele wrote: > Sam Leffler wrote: > >> Eric Schuele wrote: >> >>> Sam Leffler wrote: >>> >>>> Eric Schuele wrote: >>>> >>> >>> <big-snip> >>> >>> >>> Both my APs (home and office) hide their ssids. One is a wrt54g >>> (home), the other is linksys as well... though I forget the model at >>> the moment (FWIW its a/b/g). What can I do to provide the info you >>> need? >> >> >> >> These should work; I've had reports of problems with certain Cisco >> ap's. Note however that configuring an ap to hide it's ssid adds no >> real security. >> > > FWIW... I set my AP to broadcast the ssid. It then quickly associated > with it. But then dhclient 'broke the association' when it tried to > acquire a lease (I have removed the media lines from dhclient.conf)? and > subsequent wpa_supplicant attempts would no longer detect or associate > with the AP... till I reboot. > > Attached is that log. > > What else can I provide to help. I'll look into this; thanks. Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42EEE9DB.80408>