Date: Sat, 8 Jan 2011 23:22:02 +0100 From: Paul B Mahol <onemda@gmail.com> To: Chris Brennan <xaero@xaerolimit.net> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: WPA Supplicant issue (maybe) Message-ID: <AANLkTi=0ofPGCt1NyfmdvZaxMjEhXZENTn4H_gbNgCzU@mail.gmail.com> In-Reply-To: <AANLkTintdKRZhTGo-PjyABtTqJE4rSWgfc=MHcN%2Bn2uW@mail.gmail.com> References: <AANLkTi=PQU7t7gG06SiT6jf8ABzYkEbjL2=WiDmRFKHe@mail.gmail.com> <AANLkTikM9p1keFbDLh_EPJnws7fk0473DFCmJhP4gtuF@mail.gmail.com> <AANLkTintdKRZhTGo-PjyABtTqJE4rSWgfc=MHcN%2Bn2uW@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/8/11, Chris Brennan <xaero@xaerolimit.net> wrote: > On Sat, Jan 8, 2011 at 3:57 PM, Paul B Mahol <onemda@gmail.com> wrote: > >> Try to load lp firmware instead of non-lp. > > > > Paul thanks for getting back to me so quickly. That did the trick. Once I > loaded the lp driver, it powered up correctly and negotiated with my AP. The > problem now is I can't route ... which is odd because > > defaultrouter="192.168.0.1" > > should cover both interfaces or do I need to do > > defaultrouter_wlan0="192.168.0.1" ? I do not know your AP setup so I can not answer this. Perhaps AP use DHCP and you want to bridge wired and wireless device?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=0ofPGCt1NyfmdvZaxMjEhXZENTn4H_gbNgCzU>