i'm embarrassed to admit that i can't, for the life of me, get a wireless connection at a friend's house at the moment. updated fedora 8, and a stock linksys WRT54GL. i have the SSID, i have the WEP key, i even have the router password, so i've logged in and checked everything -- no MAC filtering, no DHCP client limit, etc.
but when i try to bring up wireless, /var/log/messages shows me:
Feb 8 08:37:59 localhost dhclient: wmaster0: unknown hardware address type 801 Feb 8 08:37:59 localhost dhclient: wmaster0: unknown hardware address type 801 Feb 8 08:37:59 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 Feb 8 08:38:07 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11 ... Feb 8 08:39:00 localhost dhclient: No DHCPOFFERS received.
i can certainly see the WAP:
# iwlist wlan0 scan ... Cell 02 - Address: 00:18:39:6A:01:EF ESSID:"XXXXXXXX" Mode:Master Channel:6 Frequency:2.437 GHz (Channel 6) Quality=83/100 Signal level=-46 dBm Noise level=-67 dBm Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s 12 Mb/s; 48 Mb/s ...
i'm pretty much out of ideas here -- any thoughts?
rday --
======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA
Home page: http://crashcourse.ca Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook ========================================================================
Robert P. J. Day wrote:
i'm embarrassed to admit that i can't, for the life of me, get a wireless connection at a friend's house at the moment. updated fedora 8, and a stock linksys WRT54GL. i have the SSID, i have the WEP key, i even have the router password, so i've logged in and checked everything -- no MAC filtering, no DHCP client limit, etc.
but when i try to bring up wireless, /var/log/messages shows me:
Feb 8 08:37:59 localhost dhclient: wmaster0: unknown hardware address type 801 Feb 8 08:37:59 localhost dhclient: wmaster0: unknown hardware address type 801 Feb 8 08:37:59 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 Feb 8 08:38:07 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11 ... Feb 8 08:39:00 localhost dhclient: No DHCPOFFERS received.
i can certainly see the WAP:
# iwlist wlan0 scan ... Cell 02 - Address: 00:18:39:6A:01:EF ESSID:"XXXXXXXX" Mode:Master Channel:6 Frequency:2.437 GHz (Channel 6) Quality=83/100 Signal level=-46 dBm Noise level=-67 dBm Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s 12 Mb/s; 48 Mb/s ...
i'm pretty much out of ideas here -- any thoughts?
rday
======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA
Home page: http://crashcourse.ca Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook ========================================================================
I get the exact same situation at home with my linksys router (probably not router related) when I do not have broadcast ssid on. Start broadcating the ssid and I make a connection no problem.
Alan
On Fri, 8 Feb 2008, Alan J. Gagne wrote:
Robert P. J. Day wrote:
i'm embarrassed to admit that i can't, for the life of me, get a wireless connection at a friend's house at the moment. updated fedora 8, and a stock linksys WRT54GL. i have the SSID, i have the WEP key, i even have the router password, so i've logged in and checked everything -- no MAC filtering, no DHCP client limit, etc.
but when i try to bring up wireless, /var/log/messages shows me:
Feb 8 08:37:59 localhost dhclient: wmaster0: unknown hardware address type 801 Feb 8 08:37:59 localhost dhclient: wmaster0: unknown hardware address type 801 Feb 8 08:37:59 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 Feb 8 08:38:07 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11 ... Feb 8 08:39:00 localhost dhclient: No DHCPOFFERS received.
i can certainly see the WAP:
# iwlist wlan0 scan ... Cell 02 - Address: 00:18:39:6A:01:EF ESSID:"XXXXXXXX" Mode:Master Channel:6 Frequency:2.437 GHz (Channel 6) Quality=83/100 Signal level=-46 dBm Noise level=-67 dBm Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s 12 Mb/s; 48 Mb/s ...
i'm pretty much out of ideas here -- any thoughts?
rday
I get the exact same situation at home with my linksys router (probably not router related) when I do not have broadcast ssid on. Start broadcating the ssid and I make a connection no problem.
it's already broadcasting.
rday
p.s. one of the other people here is gleefully making fun of me since she has a winders system that connects no problem. this is not the time for me to be evangelizing about the benefits of OSS, trust me. :-)
-- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA
Home page: http://crashcourse.ca Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook ========================================================================
Robert P. J. Day wrote:
i'm embarrassed to admit that i can't, for the life of me, get a wireless connection at a friend's house at the moment. updated fedora 8, and a stock linksys WRT54GL. i have the SSID, i have the WEP key, i even have the router password, so i've logged in and checked everything -- no MAC filtering, no DHCP client limit, etc.
but when i try to bring up wireless, /var/log/messages shows me:
Feb 8 08:37:59 localhost dhclient: wmaster0: unknown hardware address type 801 Feb 8 08:37:59 localhost dhclient: wmaster0: unknown hardware address type 801 Feb 8 08:37:59 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 Feb 8 08:38:07 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11 ... Feb 8 08:39:00 localhost dhclient: No DHCPOFFERS received.
i can certainly see the WAP:
# iwlist wlan0 scan ... Cell 02 - Address: 00:18:39:6A:01:EF ESSID:"XXXXXXXX" Mode:Master Channel:6 Frequency:2.437 GHz (Channel 6) Quality=83/100 Signal level=-46 dBm Noise level=-67 dBm Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s 12 Mb/s; 48 Mb/s ...
i'm pretty much out of ideas here -- any thoughts?
How exactly are you using the WRT54GL? What operating system is it running? I am using a WRT54GL (running dd-wrt) as an access point attached to my desktop. I had to make some changes to the WRT setup, eg stopping dhcpd on it (as I rely on dhcpd on the desktop). But it is not clear to me how you are using it.
I would suspect the settings in /etc/dhcpd.conf in whatever you are trying to connect to.
On Fri, 8 Feb 2008, Timothy Murphy wrote:
Robert P. J. Day wrote:
i'm embarrassed to admit that i can't, for the life of me, get a wireless connection at a friend's house at the moment. updated fedora 8, and a stock linksys WRT54GL. i have the SSID, i have the WEP key, i even have the router password, so i've logged in and checked everything -- no MAC filtering, no DHCP client limit, etc.
but when i try to bring up wireless, /var/log/messages shows me:
Feb 8 08:37:59 localhost dhclient: wmaster0: unknown hardware address type 801 Feb 8 08:37:59 localhost dhclient: wmaster0: unknown hardware address type 801 Feb 8 08:37:59 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 Feb 8 08:38:07 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11 ... Feb 8 08:39:00 localhost dhclient: No DHCPOFFERS received.
i can certainly see the WAP:
# iwlist wlan0 scan ... Cell 02 - Address: 00:18:39:6A:01:EF ESSID:"XXXXXXXX" Mode:Master Channel:6 Frequency:2.437 GHz (Channel 6) Quality=83/100 Signal level=-46 dBm Noise level=-67 dBm Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s 12 Mb/s; 48 Mb/s ...
i'm pretty much out of ideas here -- any thoughts?
How exactly are you using the WRT54GL? What operating system is it running? I am using a WRT54GL (running dd-wrt) as an access point attached to my desktop.
it's a straight stock WRT54GL, connected to a cable modem. i'm currently connected only because i moved my laptop close enough to the linksys to use the wired connection, so the router is more than happy to give me an IP address that way.
but "system-config-network" is absolutely unable to make a wireless connection, no matter what i do. the appropriate b43-related modules appear to be loaded. /var/log/dmesg shows that the Broadcom 4311 WLAN was identified properly.
like i said, i'm out of ideas.
rday --
======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA
Home page: http://crashcourse.ca Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook ========================================================================
Robert P. J. Day wrote:
# iwlist wlan0 scan ... Cell 02 - Address: 00:18:39:6A:01:EF ESSID:"XXXXXXXX" Mode:Master Channel:6 Frequency:2.437 GHz (Channel 6) Quality=83/100 Signal level=-46 dBm Noise level=-67 dBm Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s 12 Mb/s; 48 Mb/s ...
i'm pretty much out of ideas here -- any thoughts?
What does iwconfig (as root) say?
On Fri, 8 Feb 2008, Timothy Murphy wrote:
Robert P. J. Day wrote:
# iwlist wlan0 scan ... Cell 02 - Address: 00:18:39:6A:01:EF ESSID:"XXXXXXXX" Mode:Master Channel:6 Frequency:2.437 GHz (Channel 6) Quality=83/100 Signal level=-46 dBm Noise level=-67 dBm Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s 12 Mb/s; 48 Mb/s ...
i'm pretty much out of ideas here -- any thoughts?
What does iwconfig (as root) say?
# iwconfig lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:"xxxxxxx" Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Tx-Power=27 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Encryption key:3431-... Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 #
the ESSID displayed is correct, and the encryption key is five of those four-digit strings which exactly match the underlying 10-digit numeric WEP key.
so all of that looks reasonable. doesn't it?
rday --
======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA
Home page: http://crashcourse.ca Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook ========================================================================
On Fri, Feb 08, 2008 at 08:44:25AM -0500, Robert P. J. Day wrote:
i'm embarrassed to admit that i can't, for the life of me, get a wireless connection at a friend's house at the moment. updated fedora 8, and a stock linksys WRT54GL. i have the SSID, i have the WEP key, i even have the router password, so i've logged in and checked everything -- no MAC filtering, no DHCP client limit, etc.
but when i try to bring up wireless, /var/log/messages shows me:
Feb 8 08:37:59 localhost dhclient: wmaster0: unknown hardware address type 801 Feb 8 08:37:59 localhost dhclient: wmaster0: unknown hardware address type 801 Feb 8 08:37:59 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 Feb 8 08:38:07 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11 ... Feb 8 08:39:00 localhost dhclient: No DHCPOFFERS received.
i can certainly see the WAP:
# iwlist wlan0 scan ... Cell 02 - Address: 00:18:39:6A:01:EF ESSID:"XXXXXXXX" Mode:Master Channel:6 Frequency:2.437 GHz (Channel 6) Quality=83/100 Signal level=-46 dBm Noise level=-67 dBm Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s 12 Mb/s; 48 Mb/s ...
i'm pretty much out of ideas here -- any thoughts?
I'd have to see more of /var/log/messages, as well as iwconfig output. Are they using shared-key authentication instead of open? Or perhaps vice versa?
Are you setting the WEP key before setting the SSID?
Are you doing this manually? Did you stop NetworkManager before doing any manual configuration?
John
On Fri, 8 Feb 2008, John W. Linville wrote:
I'd have to see more of /var/log/messages, as well as iwconfig output.
# iwconfig lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:"xxxxxxx" Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Tx-Power=27 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Encryption key:3431-xxxx-xxxx-xxxx-xxxx Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
where the ESSID is correct and the key is the ASCII representation of the 10-digit WEP key, which is precisely what can be read from the linksys wireless security page.
from /var/log/messages, upon running system-config-network and trying to activate wlan0:
... Feb 8 13:13:47 localhost dhclient: wmaster0: unknown hardware address type 801 Feb 8 13:13:47 localhost dhclient: wmaster0: unknown hardware address type 801 Feb 8 13:13:47 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 Feb 8 13:13:55 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12 Feb 8 13:14:07 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10 Feb 8 13:14:17 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19 Feb 8 13:14:36 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12 Feb 8 13:14:48 localhost dhclient: No DHCPOFFERS received. ...
Are they using shared-key authentication instead of open? Or perhaps vice versa?
the stock linksys firmware doesn't offer that kind of choice -- you can pick either straight WEP or a number of WPA variations or RADIUS. i'm not sure what the connecting windows system has.
Are you setting the WEP key before setting the SSID?
i'm not sure what this means -- in system-config-network, i've simply filled in the appropriate values in the dialog screen.
Mode: Managed SSID: Specified XXXXXXX Key: xxxxxxxxxxx
and no manual selection of channel or transmit rate. this has always worked before.
Are you doing this manually? Did you stop NetworkManager before doing any manual configuration?
yes, manually, and NM and NMD are both disabled.
rday --
======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA
Home page: http://crashcourse.ca Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook ========================================================================
On Fri, Feb 08, 2008 at 01:19:29PM -0500, Robert P. J. Day wrote:
On Fri, 8 Feb 2008, John W. Linville wrote:
I'd have to see more of /var/log/messages, as well as iwconfig output.
# iwconfig lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:"xxxxxxx" Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Tx-Power=27 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Encryption key:3431-xxxx-xxxx-xxxx-xxxx Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Presuming the key is correct, you might try an additional "iwconfig wlan0 essid xxxxxxx" (where xxxxxxx is changed appropriatedly) to trigger a new association attempt. Sometimes multiple tries are necessary, YMMV.
where the ESSID is correct and the key is the ASCII representation of the 10-digit WEP key, which is precisely what can be read from the linksys wireless security page.
That looks longer than 10-digits to me...? Anyway, please re-check the WEP key just to be sure. You might also ensure that the key is configured as a hex value at the router, and not as a passphrase. Just because it looks like hex doesn't mean it is being treated that way.
from /var/log/messages, upon running system-config-network and trying to activate wlan0:
... Feb 8 13:13:47 localhost dhclient: wmaster0: unknown hardware address type 801 Feb 8 13:13:47 localhost dhclient: wmaster0: unknown hardware address type 801 Feb 8 13:13:47 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 Feb 8 13:13:55 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12 Feb 8 13:14:07 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10 Feb 8 13:14:17 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19 Feb 8 13:14:36 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12 Feb 8 13:14:48 localhost dhclient: No DHCPOFFERS received.
I was hoping to see something other than the dhclient messages. Is there no other pertinent information?
Are they using shared-key authentication instead of open? Or perhaps vice versa?
the stock linksys firmware doesn't offer that kind of choice -- you can pick either straight WEP or a number of WPA variations or RADIUS. i'm not sure what the connecting windows system has.
Don't confuse encryption with authentication.
ftp://ftp.linksys.com/pdf/wrt54g_ug.pdf
See page 49 under "Authentication Type".
On the linux box, use "iwconfig wlan0 key open" or "iwconfig wlan0 key restricted" as appropriate for how the AP is configured.
Are you setting the WEP key before setting the SSID?
i'm not sure what this means -- in system-config-network, i've simply filled in the appropriate values in the dialog screen.
Mode: Managed SSID: Specified XXXXXXX Key: xxxxxxxxxxx
and no manual selection of channel or transmit rate. this has always worked before.
Are you doing this manually? Did you stop NetworkManager before doing any manual configuration?
yes, manually, and NM and NMD are both disabled.
You might try this sequence:
killall dhclient ifconfig wlan0 up iwconfig wlan0 key xxxxxxxxxx open # or restricted, if appropriate iwconfig wlan0 essid XXXXXXX
Then check the output of "iwconfig wlan0", do you get an entry for "Access Point"? If not, try that last command another time or two. If you still get no association, then try "modprobe -r b43 ; modprobe b43" and repeat.
If you finally get an association, then try:
dhclient wlan0
If that doesn't help, I don't know what to suggest. You might try to capture some wireless traffic during an association using wireshark and open a bugzilla.
Hth!
John
On Fri, 8 Feb 2008, John W. Linville wrote:
On Fri, Feb 08, 2008 at 01:19:29PM -0500, Robert P. J. Day wrote:
On Fri, 8 Feb 2008, John W. Linville wrote:
I'd have to see more of /var/log/messages, as well as iwconfig output.
# iwconfig lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:"xxxxxxx" Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Tx-Power=27 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Encryption key:3431-xxxx-xxxx-xxxx-xxxx Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Presuming the key is correct, you might try an additional "iwconfig wlan0 essid xxxxxxx" (where xxxxxxx is changed appropriatedly) to trigger a new association attempt. Sometimes multiple tries are necessary, YMMV.
ok, i'll give that a shot.
where the ESSID is correct and the key is the ASCII representation of the 10-digit WEP key, which is precisely what can be read from the linksys wireless security page.
That looks longer than 10-digits to me...? Anyway, please re-check the WEP key just to be sure. You might also ensure that the key is configured as a hex value at the router, and not as a passphrase. Just because it looks like hex doesn't mean it is being treated that way.
i thought it looked curious as well, but it's apparently just the "ASCII" rep of the actual 10-digit numeric WEP key:
'34' = 4 '31' = 1
which are the first 2 digits of the WEP key. is iwconfig *supposed* to print the WEP key that way?
more later.
rday
p.s. when you run system-config-network, the dialog screen to enter the WEP key states to use a prefix of "0x" to designate hex, but i tried it both ways and the output from iwconfig is the same either way. go figure.
======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA
Home page: http://crashcourse.ca Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook ========================================================================
Robert P. J. Day wrote:
wlan0 IEEE 802.11g ESSID:"xxxxxxx" Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Tx-Power=27 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Encryption key:3431-xxxx-xxxx-xxxx-xxxx Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
where the ESSID is correct and the key is the ASCII representation of the 10-digit WEP key, which is precisely what can be read from the linksys wireless security page.
That looks longer than 10-digits to me...? Anyway, please re-check the WEP key just to be sure. You might also ensure that the key is configured as a hex value at the router, and not as a passphrase. Just because it looks like hex doesn't mean it is being treated that way.
i thought it looked curious as well, but it's apparently just the "ASCII" rep of the actual 10-digit numeric WEP key:
'34' = 4 '31' = 1
which are the first 2 digits of the WEP key. is iwconfig *supposed* to print the WEP key that way?
I don't think so. I get ------------------------------- eth1 IEEE 802.11b ESSID:"dd-wrt" Nickname:"mary.gayleard.com" Mode:Managed Frequency:2.437 GHz Access Point: 00:16:B6:DA:56:B4 Bit Rate:11 Mb/s Sensitivity:1/3 Retry limit:4 RTS thr:off Fragment thr:off Encryption key:0000-0000-00 Security mode:open Power Management:off Link Quality=47/92 Signal level=-51 dBm Noise level=-99 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:7 Tx excessive retries:1 Invalid misc:0 Missed beacon:0 ------------------------------- when I try a rather simple 10-digit WEP key.
On Fri, 8 Feb 2008, John W. Linville wrote:
On Fri, Feb 08, 2008 at 01:19:29PM -0500, Robert P. J. Day wrote:
from /var/log/messages, upon running system-config-network and trying to activate wlan0:
... Feb 8 13:13:47 localhost dhclient: wmaster0: unknown hardware address type 801 Feb 8 13:13:47 localhost dhclient: wmaster0: unknown hardware address type 801 Feb 8 13:13:47 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 Feb 8 13:13:55 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12 Feb 8 13:14:07 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10 Feb 8 13:14:17 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19 Feb 8 13:14:36 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12 Feb 8 13:14:48 localhost dhclient: No DHCPOFFERS received.
I was hoping to see something other than the dhclient messages. Is there no other pertinent information?
that is the *entire* contents being dumped to /var/log/messages from the time i try to activate wlan0 to the time it fails and gives up. nothing else.
i'll try more of your suggestions and report back shortly.
rday
Robert P. J. Day wrote:
Feb 8 13:14:36 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12 Feb 8 13:14:48 localhost dhclient: No DHCPOFFERS received.
Isn't this a slightly curious DHCPDISCOVER? I have something like ---------------------------------- Feb 9 01:04:06 mary dhclient: DHCPREQUEST on eth1 to 192.168.2.1 port 67 Feb 9 01:04:06 mary dhclient: DHCPACK from 192.168.2.1 ---------------------------------- I suspect your routing table is wrong. What does "route -n" say? Mine says ---------------------------------- [tim@mary ~]$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth1 ----------------------------------
I would guess that the only thing wrong with your setup is the routing table and /etc/dhcpd on the desktop.
Ps I am not an expert.
On Fri, 8 Feb 2008, John W. Linville wrote:
On Fri, Feb 08, 2008 at 01:19:29PM -0500, Robert P. J. Day wrote:
Don't confuse encryption with authentication.
ftp://ftp.linksys.com/pdf/wrt54g_ug.pdf
See page 49 under "Authentication Type".
right, sorry -- i believe from earlier that the windows system had "open", so that's what i'm trying.
You might try this sequence:
killall dhclient ifconfig wlan0 up iwconfig wlan0 key xxxxxxxxxx open # or restricted, if appropriate iwconfig wlan0 essid XXXXXXX
Then check the output of "iwconfig wlan0", do you get an entry for "Access Point"? If not, try that last command another time or two. If you still get no association, then try "modprobe -r b43 ; modprobe b43" and repeat.
If you finally get an association, then try:
dhclient wlan0
If that doesn't help, I don't know what to suggest. You might try to capture some wireless traffic during an association using wireshark and open a bugzilla.
tried it all ... nothing. the interface can certainly *see* the WAP using "iwlist wlan0 scan".
# iwconfig lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:"XXXXXXX" Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Tx-Power=27 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Encryption key:xxxx-xxxx-xx Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
(note that, since i used iwconfig to set the key, now it's printing it as the actual 10 digit key, as opposed to that weird ASCII format. hmmmmm ....)
i've never had this much trouble before. weird. i'll go at it again on the weekend. thanks.
rday
======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA
Home page: http://crashcourse.ca Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook ========================================================================
On Fri, Feb 08, 2008 at 03:21:44PM -0500, Robert P. J. Day wrote:
i've never had this much trouble before. weird. i'll go at it again on the weekend. thanks.
FWIW, I never use system-config-network. Why are you not using NetworkManager? It has a lot more curb appeal to impress your Windows friends... :-)
Anyway, s-c-n still doesn't seem to handle mac80211 drivers quite right. I think there is a problem with how it tries to determine if the link is "up" (which in this case should be when there is an association). FWIW, I can't get s-c-n to work at all on my simple WEP network, but NM and manual configuration work first time, everytime...YMMV.
I would suggest not using s-c-n at all. If NM doesn't work, then you should just using the ifconfig/iwconfig/dhclient sequence described earlier in this thread.
Hth!
John
On Fri, Feb 08, 2008 at 04:13:54PM -0500, John W. Linville wrote:
Anyway, s-c-n still doesn't seem to handle mac80211 drivers quite right. I think there is a problem with how it tries to determine if the link is "up" (which in this case should be when there is an association). FWIW, I can't get s-c-n to work at all on my simple WEP network, but NM and manual configuration work first time, everytime...YMMV.
I found a mechanism for patching the ifup scripts that makes s-c-n work in my environment with a mac80211-based device. I'm attaching a file called "network-functions.patch" to this email. It is generated against the network-functions file in initscripts-8.60.1 in Fedora 8.
In case you need a tutorial on how to apply it:
cd /etc/sysconfig/network-scripts patch < network-functions.patch
I would recommend a reboot after applying the patch. Does this help you to use s-c-n?
Good luck!
John