Bug #2412

wlan0 fails to get address via dhclient

Added by nonsolosoft about 2 years ago. Updated about 2 years ago.

Status:NewStart date:08/27/2012
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

I'm not able to connect via Atheros 2413 to TP-Link wifi router.
In attachment there is the shell session log.

wlan0_dhclient.log (4.71 KB) nonsolosoft, 08/27/2012 01:09 AM

wlan_dhclient.tcpdump - tcpdump file (4.36 KB) nonsolosoft, 08/30/2012 02:05 AM

History

#1 Updated by nonsolosoft about 2 years ago

uname -a
DragonFly lap.diff.org 3.1-DEVELOPMENT DragonFly v3.1.0.1313.g19230-DEVELOPMENT #36: Wed Aug 15 22:09:18 CEST 2012 :/usr/obj/usr/src/sys/GENERIC i386

#2 Updated by Johannes.Hofmann about 2 years ago

With some AP I had to set net.wlan.force_swcrypto=1 for ath(4) to connect properly.
Could be worth a try.

#3 Updated by nonsolosoft about 2 years ago

Thank you Johannes, I've tried:

lap# sysctl net.wlan.force_swcrypto=1
net.wlan.force_swcrypto: 0 -> 1
lap# ifconfig wlan0
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::211:f5ff:fe64:1662%wlan0 prefixlen 64 scopeid 0x8
ether 00:11:f5:64:16:62
media: IEEE 802.11 Wireless Ethernet DS/1Mbps mode 11g
status: associated
ssid NOVELLAWiFi_Spot2 channel 11 (2462 MHz 11g) bssid f8:d1:11:75:7d:fc
regdomain 100 indoor ecm authmode WPA privacy ON deftxkey 1
TKIP 2:128-bit txpower 17.5 bmiss 7 scanvalid 450 protmode CTS wme
burst roaming MANUAL
lap# dhclient wlan0
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPNACK from 192.168.1.1 (f4:ec:38:ba:2b:b6)
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

It seems not resolve, sorry.

#4 Updated by justin about 2 years ago

That DHCPNAK line in the output is the wireless base station saying "no, I don't want to give you an IP address." Can you try a different wireless AP?

#5 Updated by nonsolosoft about 2 years ago

Justin C. Sherrill wrote:
> That DHCPNAK line in the output is the wireless base station saying "no, I don't want to give you an IP address." Can you try a different wireless AP?

Hi Justin,

in this hotel I see three access points: the only one that answer to wpa_supplicant seems only the my floor's one, while
with iPad I'm able to connect to each of them.

It's strange, I've tried also to set dfbsd laptop MAC address with the same of my iPad but I've not got any new result.

In attachment there is the tcpdump file of the dhclient wlan0 session:

#6 Updated by thomas.nikolajsen about 2 years ago

>in this hotel I see three access points: the only one that answer to wpa_supplicant seems only the >my floor's one, while with iPad I'm able to connect to each of them.

You really need to use your own dhcp server, or at least with known setup, for testing:
a dhcp server can use any information that it has to decide if lease shall be offered or not,
so if you don't know dhcp server setup, test is not saying much about client.

We have a (silly IMO) example in our tree:
http://gitweb.dragonflybsd.org/dragonfly.git/blob/HEAD:/nrelease/root/etc/dhcpd.conf

Also available in: Atom PDF