Re: dlink dwa-556



On Tue, 8 Dec 2009 23:18:42 +0100
lee <lee@xxxxxxxxxxxxxxx> wrote:

...

a) output of 'iwlist wlan0 [or whatever it's called] scan'

yun:/home/lee# iwlist wlan0 scan
wlan0 Scan completed :
Cell 01 - Address: 00:23:08:17:73:A9
Channel:5
Frequency:2.432 GHz (Channel 5)
Quality=53/70 Signal level=-57 dBm
Encryption key:on
ESSID:"WLAN-177334"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
18 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 12 Mb/s; 24 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=00000004e7d2a174
Extra: Last beacon: 480ms ago
IE: Unknown: 000B574C414E2D313737333334
IE: Unknown: 010882848B961224486C
IE: Unknown: 030105
IE: Unknown: 2A0104
IE: Unknown: 32040C183060
IE: Unknown: 2D1AEE1117FFFF0000010000000000000000000000000C0000000000
IE: Unknown: 3D1605070100000000000000000000000000000000000000
IE: Unknown: 3E0100
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
IE: Unknown: 7F0101
IE: Unknown: DD8C0050F204104A00011010440001021041000100103B00010310470010000000000000000110000023081773A71021000B436F72706F726174696F6E1023000941525634353235505710240008312E30372E3030301042000A4A3833343033363030341054000800060050F204000110110014576972656C65737320526F757465722857464129100800020004
IE: Unknown: 0706444520010D10
IE: Unknown: DD1E00904C33EE1117FFFF0000010000000000000000000000000C0000000000
IE: Unknown: DD1A00904C3405070100000000000000000000000000000000000000

yun:/home/lee#


Hm, at least wicd seems to have set the ESSID and to have found a
cell.

?? This output has nothing to do with wicd.

b) output of syslog when you try to connect

Anything in particular I should be looking for? There are messages


Dec 8 17:33:58 yun dhclient: isc-dhclient-V3.1.3
Dec 8 17:33:58 yun dhclient: isc-dhclient-V3.1.3


... but I'm not using dhcp. And there's a bunch of messages from
"NetworkManager":

If you're not using dhcp, then no dhclient process should be running.
You should find out what's invoking it and stop it.

...

When debugging, we really don't want anything running except the most
basic of command line utilities - I recommend that you stop all the
higher level managers while we try to figure out the basic issues. In
any event, you should never have multiple network managers running -
they can (and probably will) interfere with each other and you'll get
chaos.

c) run wpa_supplicant in the foreground with debugging enabled
('wpa_supplicant -c/etc/wpa_supplicant.conf -iwlan0 -d') and report the
output and syslog, as well as your wpa_supplicant.conf (sanitized)

There's no configuration file for wpa_supplicant at all. It seemed to
me that the Debian way of using it is by some scripts that refer to
entries in /etc/network/interfaces. I have no way of knowing if the
Debian version of wpa_supplicant is modified in some way.

AFAIK, Debian doesn't modify wpa_supplicant, but when you properly
configure /etc/network/interfaces, then the Debian network scripts will
create the appropriate wpa_supplicant config file (on the fly?) and
properly invoke wpa_supplicant, pointing it at the appropriate config
file. When this works, you can see what Debian's done by grepping
through the output of 'ps ax' for 'wpa_supplicant'.

...

It also creates some messages in the syslog:


Dec 8 22:43:27 yun avahi-daemon[2934]: Interface wlan0.IPv4 no longer relevant for mDNS.
Dec 8 22:43:27 yun avahi-daemon[2934]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.2.199.
Dec 8 22:43:27 yun avahi-daemon[2934]: Withdrawing address record for 192.168.2.199 on wlan0.
Dec 8 22:43:27 yun avahi-daemon[2934]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.2.199.
Dec 8 22:43:27 yun avahi-daemon[2934]: New relevant interface wlan0.IPv4 for mDNS.
Dec 8 22:43:27 yun avahi-daemon[2934]: Registering new address record for 192.168.2.199 on wlan0.IPv4.
Dec 8 22:43:27 yun avahi-daemon[2934]: Interface wlan0.IPv4 no longer relevant for mDNS.
Dec 8 22:43:27 yun avahi-daemon[2934]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.2.199.
Dec 8 22:43:27 yun avahi-daemon[2934]: Withdrawing address record for
192.168.2.199 on wlan0.

These are coming from avahi-daemon, which I'd suggest you turn off while we troubleshoot.

yun:/home/lee# iwconfig
lo no wireless extensions.

eth4 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11bgn ESSID:""
Mode:Managed Frequency:2.432 GHz Access Point: Not-Associated
Tx-Power=20 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

yun:/home/lee#

Well, that just shows that you're not connected, as we realized ...

Now what does this tell me? Is WPA-PSK supposed to work for WPA2? I

Yes.

tried it with the router set to "WPA-Personal" and "WPA / WPA2", but I
got the same output from wpa_supplicant each time.

Hm, googling about the error message ("socket(PF_PACKET): Address
family not supported by protocol") finds: http://lists.shmoo.com/pipermail/hostap/2006-June/013571.html

Checking the kernel configuration shows that "Packet socket" in the
networking options is indeed disabled. I've enabled it, and now
wpa_supplicant seems to get a connection:

...

yun:/home/lee# iwconfig
lo no wireless extensions.

eth4 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11bgn ESSID:"WLAN-177334"
Mode:Managed Frequency:2.432 GHz Access Point: 00:23:08:17:73:A9
Bit Rate=0 kb/s Tx-Power=20 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Encryption key:6A25-499D-B4B3-B856-75B0-AC0F-61D1-247A [2] Security mode:open
Power Management:off
Link Quality=64/70 Signal level=-46 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Excellent! We're up and running!

yun:/home/lee# route
Kernel-IP-Routentabelle
Ziel Router Genmask Flags Metric Ref Use Iface
localnet * 255.255.255.0 U 0 0 0 eth4
localnet * 255.255.255.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 1000 0 0 eth4
default router.yagibdah 0.0.0.0 UG 0 0 0 eth4


This isn't right yet, but it seems to work :) I'll unplug the cable
from eth4 and check if it does ...

I take it that it should work now the Debian way by making entries in
/etc/network/interfaces?

I'd assume so.

Thanks for your help!

Sure! Good luck going forward.

Celejar
--
foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx