George Borisov wrote:
Freddy Freeloader wrote:
No. I just listed the ssid in wpa_supplicant.conf. I didn't set the
channel or the ssid with iwconfig as I've never had to do that before.
I'll try it, but what's the reasoning behind using iwconfig for that
when wpa_supplicant is supposed
H.S. wrote:
Freddy Freeloader wrote:
Well, that was a good idea, but it didn't work. I simply cannot
connect with any type of encryption. There is a line in dmesg that
says "Cleared all keys" before the card starts sending out sending
out dhcp requests, so I'm guessing that is what the p
Freddy Freeloader wrote:
>
> No. I just listed the ssid in wpa_supplicant.conf. I didn't set the
> channel or the ssid with iwconfig as I've never had to do that before.
> I'll try it, but what's the reasoning behind using iwconfig for that
> when wpa_supplicant is supposed to take care of it?
Freddy Freeloader wrote:
George Borisov wrote:
Freddy Freeloader wrote:
I haven't, however, gotten this to work with or without any
security. It goes through the motions but it never recieves a dhcp
offer from the router.
Just to check, did you set the channel / ssid with iwconfig?
George Borisov wrote:
Freddy Freeloader wrote:
I haven't, however, gotten this to work with or without any
security. It goes through the motions but it never recieves a dhcp
offer from the router.
Just to check, did you set the channel / ssid with iwconfig?
No. I just listed t
Freddy Freeloader wrote:
Well, that was a good idea, but it didn't work. I simply cannot connect
with any type of encryption. There is a line in dmesg that says
"Cleared all keys" before the card starts sending out sending out dhcp
requests, so I'm guessing that is what the problem is. An
Freddy Freeloader wrote:
>
> I haven't, however, gotten this to work with or without any
> security. It goes through the motions but it never recieves a dhcp
> offer from the router.
Just to check, did you set the channel / ssid with iwconfig?
--
George Borisov
DXSolutions Ltd
signature.a
H.S. wrote:
Freddy Freeloader wrote:
Thanks for your reply.
Well, I've made some progess on this since I posted last time. I
have found out that you must use the bcm43xx-fwcutter utility from
berlios.de to extract all the *.fw (firmware) files from the
bcmlw.sys windows
Ah yes, I had
Freddy Freeloader wrote:
Thanks for your reply.
Well, I've made some progess on this since I posted last time. I have
found out that you must use the bcm43xx-fwcutter utility from berlios.de
to extract all the *.fw (firmware) files from the bcmlw.sys windows
Ah yes, I had to do that too.
H.S. wrote:
Freddy Freeloader wrote:
Is anyone else having problems with the new Broadcom bcm43xx module?
I get the following error in dmesg when the wireless interface is
configured in /etc/network/interfaces, /etc/default/ifplugd,
etc/default/wpasupplicant, and /etc/wpa_supplicant.conf.
Freddy Freeloader wrote:
Is anyone else having problems with the new Broadcom bcm43xx module? I
get the following error in dmesg when the wireless interface is
configured in /etc/network/interfaces, /etc/default/ifplugd,
etc/default/wpasupplicant, and /etc/wpa_supplicant.conf. The error is
r
Is anyone else having problems with the new Broadcom bcm43xx module? I
get the following error in dmesg when the wireless interface is
configured in /etc/network/interfaces, /etc/default/ifplugd,
etc/default/wpasupplicant, and /etc/wpa_supplicant.conf. The error is
repeated about 30 times.
12 matches
Mail list logo
