dhclient can not get ip with wpa ccmp !

miniqq

Member

Reaction score: 4
Messages: 47

Hi,
if the ap set to WEP, dhclient can automatic get ip from ap router. but when i change ap router to wpa+psk+ccmp, the dhclient not working ! os = freebsd 8 stable
I have never met that before freebsd 8.0 .
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 9,286
Messages: 33,826

Make sure the client is associating correctly with the AP.
 
OP
M

miniqq

Member

Reaction score: 4
Messages: 47

Yes , wpa get connection with AP correctly ! and a windows xp client hadn't any problem to connect to AP too .

dhclient get a DHCPNOOFFERS message but no ip.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 9,286
Messages: 33,826

psycho said:
[CMD=""]iwconfig[/CMD] ?
That's a linux command my friend. Try [cmd=]ifconfig[/cmd].
 
OP
M

miniqq

Member

Reaction score: 4
Messages: 47

I said everything was ok but dhclient. and the linux box ,windows had no problem to connect the AP.
my card now connect the AP,but the dhclient can't get ip. this is the question !
i try
Code:
 dhclient wlan0
it give me:
Code:
host# dhclient wlan0
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
And the thing has not been happened on my freebsd 7.0 7.2 boxes!


Who make the vlan?
It 's not so stable!

There is another question when i switch AP, if i restart netif, the system panic and auto reboot, if i restart wpa_suppliant , the thing happend again -- Reboot !
and the driver report :
Code:
 Association request to the driver failed
 

DeliciousD

New Member

Reaction score: 2
Messages: 9

I'm having this same issue while using the ral driver and wpa2-psk. I am not getting an IP address via DHCP even though wpa_supplicant has successfully associated with the AP. tcpdump on the wlan interface shows it is working as I see traffic from all the other hosts associated with the same AP. Perusing the documentation hasn't helped me yet, but I just upgraded to 8-STABLE (binary upgrade and then built from source 2/29/10) and I may have missed a configuration change from 7.2 to 8.0. Any pointers would be appreciated.
 

richardpl

Aspiring Daemon

Reaction score: 68
Messages: 841

miniqq said:
Who make the vlan?
It 's not so stable!
Works for me.TM

You are using buggy driver. Before continuing using it, report bugs and aid developers to fix them.

Driver is buggy because nobody cared to test it in CURRENT.
 

DeliciousD

New Member

Reaction score: 2
Messages: 9

I have been able to get the interface working by using a static IP address. The line I used in rc.conf was:

Code:
ifconfig_wlan0="WPA inet 192.168.x.y/24"
defaultrouter="192.168.x.z" # I have 2 nics, no not a router
Don't forget to manually add the correct information to resolv.conf

I tried implementing synchronous_dhclient="YES", as has been reported by some people to solve the problem, but my system hung on boot waiting for dhclient until I hit the power button. In one instance the wait was around 12 hours.

dhclient created a lease for the interface successfully, however the IP address is not being assigned to it. I have submitted a PR for dhclient.
 
Top