Wireless gets link-local inet6 address

[chili555]

I just changed the config to what you said, but again a "sudo dhclient wlan0" doesn't give me an IP address...

Are there any clues here?

sudo ifdown wlan0 && sudo ifup -v wlan0
cat /var/log/syslog | grep wlan0 | tail -n20

Ideally run consecutively.

I agree with and use this configuration myself without any problems:

auto wlan0
iface wlan0 inet dhcp
wpa-ssid yourssid
wpa-psk yourpassphrase

[chili555]

sudo dhclient -v wlan0

I think this says to the system to get an IP address for wlan0. I think the following is preferred, since it asks for the details in /etc/network/interfaces to be used:

sudo ifdown wlan0 && sudo ifup -v wlan0

...or am I corn-fused, steeldriver?? (Always a possibility!)

[steeldriver]

You are probably right chili - I have used dhclient -r / dhclient -v in the past but I don't know that it's the 'right' way

As you say it makes more sense to let ifup decide what to do based on the config file

[chili555]

You are probably right chili - I have used dhclient -r / dhclient -v in the past but I don't know that it's the 'right' way

As you say it makes more sense to let ifup decide what to do based on the config file

@yadeki--

Please try BOTH methods and give us your results. Both use the '-v' switch so that we can see informative messages.

[yadeki]

We should probably also take a step back and check exactly what device (PCI ID) you have and what driver it's trying to use

It's an USB dongle Realtek rt2870usb (built in driver).

[yadeki]

sudo dhclient -v wlan0

Gives me:

yannick@HTPC:~$ sudo dhclient -v wlan0
Internet Systems Consortium DHCP Client 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/00:1c:df:92:7a:a5
Sending on   LPF/wlan0/00:1c:df:92:7a:a5
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
...

And so on...

sudo ifdown wlan0 && sudo ifup -v wlan0

Gives me:

ifdown: interface wlan0 not configured
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/ethtool
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile  /var/run/wpa_suppl                                                                                                                       icant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 2164).
wpa_supplicant: removing  /lib/init/rw/sendsigs.omit.d/wpasupplicant.wpa_supplica                                                                                                                       nt.wlan0.pid
wpa_supplicant: wpa-driver nl80211,wext (default)
wpa_supplicant: /sbin/wpa_supplicant -s -B -P  /var/run/wpa_supplicant.wlan0.pid                                                                                                                        -i wlan0 -D nl80211,wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: creating sendsigs omission pidfile:  /lib/init/rw/sendsigs.omit.d                                                                                                                       /wpasupplicant.wpa_supplicant.wlan0.pid
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "DeKinderWIFI" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: enabling network block 0 -- OK

Then it fails.

yannick@HTPC:~$ cat /var/log/syslog | grep wlan0 | tail -n20

Gives me:

Apr 20 18:12:22 HTPC kernel: [ 1409.610608] wlan0: authenticated
Apr 20 18:12:22 HTPC kernel: [ 1409.628312] wlan0: associate with 00:07:7d:14:80:d4 (try 1)
Apr 20 18:12:22 HTPC kernel: [ 1409.631486] wlan0: RX ReassocResp from 00:07:7d:14:80:d4 (capab=0x411 status=0 aid=1)
Apr 20 18:12:22 HTPC kernel: [ 1409.631496] wlan0: associated
Apr 20 18:12:24 HTPC dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Apr 20 18:12:32 HTPC kernel: [ 1419.739880] wlan0: disassociating from 00:07:7d:14:80:d4 by local choice (reason=3)
Apr 20 18:12:32 HTPC kernel: [ 1419.787211] wlan0: deauthenticating from 00:07:7d:14:80:d4 by local choice (reason=3)
Apr 20 18:12:33 HTPC kernel: [ 1421.048896] wlan0: authenticate with 00:07:7d:14:80:d4 (try 1)
Apr 20 18:12:33 HTPC kernel: [ 1421.050564] wlan0: authenticated
Apr 20 18:12:33 HTPC kernel: [ 1421.068278] wlan0: associate with 00:07:7d:14:80:d4 (try 1)
Apr 20 18:12:33 HTPC kernel: [ 1421.071441] wlan0: RX ReassocResp from 00:07:7d:14:80:d4 (capab=0x411 status=0 aid=1)
Apr 20 18:12:33 HTPC kernel: [ 1421.071451] wlan0: associated
Apr 20 18:12:43 HTPC dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Apr 20 18:12:43 HTPC kernel: [ 1431.119923] wlan0: disassociating from 00:07:7d:14:80:d4 by local choice (reason=3)
Apr 20 18:12:43 HTPC kernel: [ 1431.170080] wlan0: deauthenticating from 00:07:7d:14:80:d4 by local choice (reason=3)
Apr 20 18:12:44 HTPC kernel: [ 1432.428858] wlan0: authenticate with 00:07:7d:14:80:d4 (try 1)
Apr 20 18:12:44 HTPC kernel: [ 1432.430502] wlan0: authenticated
Apr 20 18:12:44 HTPC kernel: [ 1432.448371] wlan0: associate with 00:07:7d:14:80:d4 (try 1)
Apr 20 18:12:44 HTPC kernel: [ 1432.451534] wlan0: RX ReassocResp from 00:07:7d:14:80:d4 (capab=0x411 status=0 aid=1)
Apr 20 18:12:44 HTPC kernel: [ 1432.451544] wlan0: associated

[Iowan]

That's right. Here's the output of this file:

#auto lo
#iface lo inet loopback
...

A bit off-topic at the moment, but you will eventually want to re-enable the "lo" configuration.

[steeldriver]

I'm not seeing any red flags - it looks like the device is authenticating AND associating OK - just the DHCP is failing to get a response. Are you sure the router's DHCP server is enabled/configured? Are you sure you don't have any kind of wireless MAC filtering set up on your router that might be rejecting DHCP requests from the dongle device?

[yadeki]

I'm not seeing any red flags - it looks like the device is authenticating AND associating OK - just the DHCP is failing to get a response. Are you sure the router's DHCP server is enabled/configured? Are you sure you don't have any kind of wireless MAC filtering set up on your router that might be rejecting DHCP requests from the dongle device?

I'm 100% sure that I don't have MAC filtering enabled. The DHCP service is running on the router.

I just assigned a static IP for wlan0, even then I can't ping the IP address.

interfaces config file:

#localhost
auto lo
iface lo inet loopback
#wired 
auto eth0
iface eth0 inet dhcp
#WLAN 
auto wlan0
iface wlan0 inet static
address 192.168.1.5
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
wpa-ssid DeKinderWIFI
wpa-psk <MyPSK(too long for typing :))>

Am I doing something wrong here?

[steeldriver]

Actually I DO see red flags now I look at it closer - the persistent

wlan0: disassociating from 00:07:7d:14:80:d4 by local choice (reason=3)

are a problem I think - may indicate a driver bug? I will see what I can dig up (although chili555 and others on this forum know a lot more about wireless devices than I do)