No IP Address from DHCP Server on Wireless Network

[naimesh.thakkar]

Hello,

I have installed Fedora 10 on my A860 Dell Vostrol Laptop with AR242X Atheros Wireless card. Wireless card worked out of the box and i could detect wireless network and connect to it. But i have a problem that, my wireless connection is not able to get IP address from the DHCP server. Please help me out what can i do to get this working. I am using WEP security and authentication is open system.

I have windows 7 beta installed on the same machine and on that wireless network works fine so i am sure that there is no problem with the wirless network.

I am using DIR-300 router from D-LINK.

I tried to see packet log on wireshark and there i see that there is no reply to the DHCP discover message. Actually i don't see any RX packets at all. Which is not normal as there is traffic on the network.

Please let me know if any other information is required.

Regards,
Naimesh

[David Becker]

Hello,

Hi


...

Please let me know if any other information is required.

lsmod | grep ath

ifconfig

iwconfig

David

[naimesh.thakkar]

lsmod | grep ath

dm_multipath 17164 0
ath5k 112520 0
mac80211 173668 1 ath5k
cfg80211 23816 2 ath5k,mac80211


ifconfig

eth0 Link encap:Ethernet HWaddr 00:21:70:8B:48:FE
inet addr:123.238.136.130 Bcast:123.238.143.255 Mask:255.255.248.0
inet6 addr: fe80::221:70ff:fe8b:48fe/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:275782 errors:0 dropped:0 overruns:0 frame:0
TX packets:62487 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:133412640 (127.2 MiB) TX bytes:5711719 (5.4 MiB)
Interrupt:17 Base address:0x6000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:44 errors:0 dropped:0 overruns:0 frame:0
TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6599 (6.4 KiB) TX bytes:6599 (6.4 KiB)

wlan0 Link encap:Ethernet HWaddr 00:17:C4:45:D0:65
inet6 addr: fe80::217:c4ff:fe45:d065/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:8136 (7.9 KiB)

wmaster0 Link encap:UNSPEC HWaddr 00-17-C4-45-D0-65-F4-BF-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:11 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Power Management:off
Link Quality=117/100 Signal level:-26 dBm Noise level=-101 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

pan0 no wireless extensions.

[nyjetshead]

From CLI also post the output of nm-tool

[David Becker]

It (iwconfig) says that you're not associated with an access point. Did you run these commands while being (seemingly) associated with the access point?

From the looks of it your driver/device isn't functioning or being handled properly, you're not receiving any packets.

How did you setup your WEP connection?

David

[naimesh.thakkar]

From CLI also post the output of nm-tool

NetworkManager Tool

State: connected

- Device: eth0 ----------------------------------------------------------------
Type: Wired
Driver: r8169
State: connected
Default: yes
HW Address: 00:21:70:8B:48:FE

Capabilities:
Supported: yes
Carrier Detect: yes
Speed: 100 Mb/s

Wired Settings

IPv4 Settings:
Address: 123.238.136.130
Prefix: 21 (255.255.248.0)
Gateway: 123.238.136.1

DNS: 124.124.5.141
DNS: 124.124.5.140
DNS: 220.225.236.85
DNS: 220.225.236.84


- Device: wlan0 ----------------------------------------------------------------
Type: 802.11 WiFi
Driver: ath5k_pci
State: disconnected
Default: no
HW Address: 00:17:C4:45:D0:65

Capabilities:
Supported: yes

Wireless Settings
WEP Encryption: yes
WPA Encryption: yes
WPA2 Encryption: yes

Wireless Access Points
Thakkar Network: Infra, 00:21:91:2C:99:D3, Freq 2412 MHz, Rate 54 Mb/s, Strength 46 WEP

[naimesh.thakkar]

It (iwconfig) says that you're not associated with an access point. Did you run these commands while being (seemingly) associated with the access point?


Hello,

Yes i was not associated with access point while i ran this commands.

Here is the output when associated

iwconfig
wlan0 IEEE 802.11bg ESSID:"Thakkar Network"
Mode:Managed Frequency:2.412 GHz Access Point: 00:21:91:2C:99:D3
Bit Rate=2 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Power Management:off
Link Quality=120/100 Signal level:-24 dBm Noise level=-101 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

ifconfig
wlan0 Link encap:Ethernet HWaddr 00:17:C4:45:D0:65
inet6 addr: fe80::217:c4ff:fe45:d065/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:9936 (9.7 KiB)

wmaster0 Link encap:UNSPEC HWaddr 00-17-C4-45-D0-65-F4-BF-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)



How did you setup your WEP connection?

?? I left click on the network connection icon in the task bar, select wireless network. Then i enter the key and then it gets connected but can not get the IP address.

[David Becker]

Everything seems to be setup properly. Very strange. Have you tried disabling/enabling the wireless (right click on the network icon in your panel, and disable/enable wireless there)?

Does it work with a static IP address? You can set that up by right clicking the same network panel icon and edit the (wireless) connection.

David

[nyjetshead]

Please post the output of nm-tool while associated with the AP

Edit: Better yet... As root check the output of /var/log/messages related to Network Manager and dhclient for wlan0 while you are associating.

[Iron_Mike]

It is showing you're associated with the AP but not authenticated. Disable the WEP on the router and see if it works. That will verify that the card and driver are working properly. On a side note, you will not receive a ip address until you are authenticated with the AP

Mike

[naimesh.thakkar]

Have you tried disabling/enabling the wireless

I tried but it did not help


Does it work with a static IP address? You can set that up by right clicking the same network panel icon and edit the (wireless) connection.


With static IP address, it shows as connected but i can not ping the other PC (other PC also with static IP address in the same subnet) :(

[naimesh.thakkar]

Please post the output of nm-tool while associated with the AP

- Device: wlan0 ----------------------------------------------------------------
Type: 802.11 WiFi
Driver: ath5k_pci
State: connecting (getting IP configuration)
Default: no
HW Address: 00:17:C4:45:D0:65

Capabilities:
Supported: yes

Wireless Settings
WEP Encryption: yes
WPA Encryption: yes
WPA2 Encryption: yes

Wireless Access Points
Thakkar Network: Infra, 00:21:91:2C:99:D3, Freq 2412 MHz, Rate 54 Mb/s, Strength 51 WEP


Edit: Better yet... As root check the output of /var/log/messages related to Network Manager and dhclient for wlan0 while you are associating.


Feb 14 02:56:18 localhost NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Feb 14 02:56:19 localhost NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Feb 14 02:56:19 localhost NetworkManager: <info> (wlan0): supplicant connection state: associating -> associated
Feb 14 02:56:19 localhost NetworkManager: <info> (wlan0): supplicant connection state: associated -> completed
Feb 14 02:56:19 localhost NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'Thakkar Network'.
Feb 14 02:56:19 localhost NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Feb 14 02:56:19 localhost NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Feb 14 02:56:19 localhost NetworkManager: <info> (wlan0): device state change: 5 -> 7
Feb 14 02:56:19 localhost NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction.
Feb 14 02:56:19 localhost NetworkManager: <info> dhclient started with pid 4519
Feb 14 02:56:19 localhost NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Feb 14 02:56:19 localhost dhclient: Internet Systems Consortium DHCP Client 4.0.0
Feb 14 02:56:19 localhost dhclient: Copyright 2004-2007 Internet Systems Consortium.
Feb 14 02:56:19 localhost dhclient: All rights reserved.
Feb 14 02:56:19 localhost dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Feb 14 02:56:19 localhost dhclient:
Feb 14 02:56:19 localhost NetworkManager: <info> DHCP: device wlan0 state changed normal exit -> preinit
Feb 14 02:56:19 localhost dhclient: Listening on LPF/wlan0/00:17:c4:45:d0:65
Feb 14 02:56:19 localhost dhclient: Sending on LPF/wlan0/00:17:c4:45:d0:65
Feb 14 02:56:19 localhost dhclient: Sending on Socket/fallback
Feb 14 02:56:23 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Feb 14 02:56:26 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Feb 14 02:56:29 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Feb 14 02:56:36 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
Feb 14 02:56:45 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Feb 14 02:56:55 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
Feb 14 02:57:04 localhost NetworkManager: <info> Device 'wlan0' DHCP transaction took too long (>45s), stopping it.
Feb 14 02:57:04 localhost NetworkManager: <info> wlan0: canceled DHCP transaction, dhcp client pid 4519
Feb 14 02:57:04 localhost NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) scheduled...
Feb 14 02:57:04 localhost NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) started...
Feb 14 02:57:04 localhost NetworkManager: <info> Activation (wlan0/wireless): could not get IP configuration for connection 'Auto Thakkar Network'.
Feb 14 02:57:04 localhost NetworkManager: <info> (wlan0): device state change: 7 -> 6
Feb 14 02:57:04 localhost NetworkManager: <info> Activation (wlan0/wireless): asking for new secrets
Feb 14 02:57:04 localhost NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) complete.

[naimesh.thakkar]

Disable the WEP on the router and see if it works. That will verify that the card and driver are working properly.
Mike

I tried disabling WEP and after that everything works fine. Of course, i don't want to keep it disabled.

Is there some other wireless drivers that i can try to make it work with encryption?

Regards,
Naimesh

[nyjetshead]

Its not the driver..

Feb 14 02:56:55 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16


This message should be followed by an DHCPOFFER from the router (123.238.136.1) , the router is not responding to the request made by wlan0.

Reset your router.
Look at the firmware and see if there is an update.

Do you have WPA/WPA2 capabilities? WEP is weak security.

Edit:
Set up a static IP as a test.
Right click on NM Icon in the tray> Edit connections>Wireless>Add

Connection name: Static IP test
Wireless tab:
Enter your network SSID
Mode: Infrastructure
MTU: Automatic

Wireless Security Tab:
Enter your info as you did previously.

IPv4 Tab:
Method: Manual
Address:123.238.136.101
Netmask:255.255.255.0
Gateway:123.238.136.1
DNS:208.67.220.220, 208.67.222.222

Apply

Click on the NM Icon and select the new connection and see if it works

[ReachingFarr]

Did you ever find a solution to this? I'm having the same problem with my Intel PRO/Wireless 3945ABG card. DHCP works on any open network but fails (timesout) when I try to get an address from a secured network (both WEP and WPA).

[Sicinthemind]

Check IPTables and SELinux for any rules.
DHCP/BOOTP both use UDP 67 I believe.
BootP Server = UDP 67 Multicast
BootP Client = UDP 68 Multicast
DHCP Server/Client UDP 67