dhclient doesn't work over wireless

[Michael]

Hello,

My FreeBSD laptop is unable to get IP address over DHCP but the same
network works fine on Windows, Ubuntu and Android so I believe the
problem lies in my FreeBSD configuration and not on the router/access
point. Problem occurs only for wireless interface.

FreeBSD 8.1 amd64 with Atheros interface. Wireless networking was
working fine on that system (the same config files) until I had to
replace my wireless router.

My rc.conf file:
wlans_ath0="wlan0"
ifconfig_wlan0="WPA SYNCDHCP"

I'm using standard dhclient.conf file.

My wpa_supplicant.conf file:
network={
ssid="wifi"
scan_ssid=1
bssid=XX:XX:XX:XX:XX:XX
priority=9
mode=0
proto=RSN
key_mgmt=WPA-PSK
auth_alg=OPEN
pairwise=CCMP
group=CCMP
psk="xxxxx"
}

Now after reboot I'm geting wlan0 connection (status associated):
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether xx:xx:xx:xx:xx:xx
inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
media: IEEE 802.11 Wireless Ethernet DS/11Mbps mode 11g
status: associated
ssid wifi channel 9 (2452 MHz 11g) bssid d8:5d:4c:ea:cb:ee
regdomain 103 indoor ecm authmode WPA2/802.11i privacy ON
deftxkey UNDEF AES-CCM 2:128-bit txpower 20 bmiss 7 scanvalid 450
bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5
protmode CTS wme burst roaming MANUAL

But for some reason it doesn't get the IP address!
And whrn I manually try to: dhclient wlan0
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Again, other systems doesn't seem to have any trouble with getting IP
from this DHCP server and wired interface (em0) works fine too.

Any ideas please?
_______________________________________________
freebsd-...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questi...@freebsd.org"

[Chris Brennan]

On Wed, Dec 8, 2010 at 6:01 PM, Michael <mlmic...@gmail.com> wrote:

>
> Again, other systems doesn't seem to have any trouble with getting IP from
> this DHCP server and wired interface (em0) works fine too.
>
> Any ideas please?
>

A question first, is this a VirtualBox VM? If so, you'll need to either
install the bridging adapter from vBox or use a NAT configuration, in which
case you will get a 10.0.0.x IP address.

[Adam Vande More]

On Wed, Dec 8, 2010 at 5:01 PM, Michael <mlmic...@gmail.com> wrote:

>
> Again, other systems doesn't seem to have any trouble with getting IP from
> this DHCP server and wired interface (em0) works fine too.
>
> Any ideas please?
>

Your answer lies within:

http://www.freebsd.org/cgi/query-pr-summary.cgi

--
Adam Vande More

[Michael]

On 09/12/2010 02:51, Adam Vande More wrote:
> On Wed, Dec 8, 2010 at 5:01 PM, Michael<mlmic...@gmail.com> wrote:
>
>>
>> Again, other systems doesn't seem to have any trouble with getting IP from
>> this DHCP server and wired interface (em0) works fine too.
>>
>> Any ideas please?
>>
>
> Your answer lies within:
>
> http://www.freebsd.org/cgi/query-pr-summary.cgi

Ok it looks like PR number 145269. Unfortunately there is no fix yet.
Thank you for your help, at least I know it's not just me.

Michael

[krad]

you could try isc-dhcp31-client or another client as a stop gap until the pr
is resolved

[Paul B Mahol]

On 12/9/10, Michael <mlmic...@gmail.com> wrote:
> On 09/12/2010 02:51, Adam Vande More wrote:
>> On Wed, Dec 8, 2010 at 5:01 PM, Michael<mlmic...@gmail.com> wrote:
>>
>>>
>>> Again, other systems doesn't seem to have any trouble with getting IP
>>> from
>>> this DHCP server and wired interface (em0) works fine too.
>>>
>>> Any ideas please?
>>>
>>
>> Your answer lies within:
>>
>> http://www.freebsd.org/cgi/query-pr-summary.cgi
>
> Ok it looks like PR number 145269. Unfortunately there is no fix yet.
> Thank you for your help, at least I know it's not just me.

That PR is invalid/useless. If you want feedback give more.

You have wpa_supplicant.conf?

[Michael]

On 09/12/2010 10:16, Paul B Mahol wrote:
> On 12/9/10, Michael<mlmic...@gmail.com> wrote:
>>
>> Ok it looks like PR number 145269. Unfortunately there is no fix yet.
>> Thank you for your help, at least I know it's not just me.
>
> That PR is invalid/useless. If you want feedback give more.
>
> You have wpa_supplicant.conf?
>

Yes, this is my wpa_supplicant.conf file:

network={
ssid="wifi"
scan_ssid=1
bssid=XX:XX:XX:XX:XX:XX
priority=9
mode=0
proto=RSN
key_mgmt=WPA-PSK
auth_alg=OPEN
pairwise=CCMP
group=CCMP
psk="xxxxx"
}

Just to remind you - ifconfig says that wlan0 is associated with my
access point.
I'm happy to provide all details needed, just tell me what you need. I'm
running FreeBSD 8.1-RELEASE with all SA+errata patches. Standard
dhclient.conf file.

Michael

[Robert Bonomi]

> From owner-freeb...@freebsd.org Wed Dec 8 16:31:12 2010
> Date: Wed, 08 Dec 2010 23:01:30 +0000
> From: Michael <mlmic...@gmail.com>
> To: freebsd-...@freebsd.org
> Subject: dhclient doesn't work over wireless

>
> Hello,
>
> My FreeBSD laptop is unable to get IP address over DHCP but the same
> network works fine on Windows, Ubuntu and Android so I believe the
> problem lies in my FreeBSD configuration and not on the router/access
> point. Problem occurs only for wireless interface.
>
> FreeBSD 8.1 amd64 with Atheros interface. Wireless networking was
> working fine on that system (the same config files) until I had to
> replace my wireless router.

you replaced the "wireless router". Presumably this is also the wireless
'Access point', to which the laptop connects.

What are the chances that it doesn't support WPA, but *ONLY* supports WPA2?
May need to tweak the ifconfig params, and/or the supplicant 'key_mgmt' type.

>
> My rc.conf file:
> wlans_ath0="wlan0"
> ifconfig_wlan0="WPA SYNCDHCP"
>
> I'm using standard dhclient.conf file.
>

> My wpa_supplicant.conf file:

> network={
> ssid="wifi"
> scan_ssid=1
> bssid=XX:XX:XX:XX:XX:XX
> priority=9
> mode=0
> proto=RSN
> key_mgmt=WPA-PSK
> auth_alg=OPEN
> pairwise=CCMP
> group=CCMP
> psk="xxxxx"
> }
>

> Now after reboot I'm geting wlan0 connection (status associated):
> wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> ether xx:xx:xx:xx:xx:xx
> inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
> media: IEEE 802.11 Wireless Ethernet DS/11Mbps mode 11g
> status: associated
> ssid wifi channel 9 (2452 MHz 11g) bssid d8:5d:4c:ea:cb:ee
> regdomain 103 indoor ecm authmode WPA2/802.11i privacy ON
> deftxkey UNDEF AES-CCM 2:128-bit txpower 20 bmiss 7 scanvalid 450
> bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5
> protmode CTS wme burst roaming MANUAL
>
> But for some reason it doesn't get the IP address!
> And whrn I manually try to: dhclient wlan0
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
> No DHCPOFFERS received.
> No working leases in persistent database - sleeping.
>

> Again, other systems doesn't seem to have any trouble with getting IP
> from this DHCP server and wired interface (em0) works fine too.
>
> Any ideas please?