[TAG] LG 127 Wifi
jeff@jeffroot.us
jeff
Thu Aug 17 11:04:33 MSD 2006
Ben;
OK, I've gotten some more time in on the troubleshoot. I'm still
not connecting, but I now have some log files and tcpdumps.
I found my MN-520 stopped working at work, so I borrowed an Orinoco
Gold (aka "old reliable"). This worked at work. I carefully
cleaned all my /etc/network/interface and /etc/pcmcia/config.opts
files, then visited my troublesome coffee shop.
I thought I was making some progress: when I inserted the card, I
got a "New connection" message, followed by some "martian source"
lines (I was running from a VT, so these were wall messages from,
IIRC, the kernel). But it was _traffic_. I got a "failed to bring
up eth1" message.
I rebooted with Knoppix (3.9 -- I tried the latest, but that turned
my LCD into a lava lamp and locked the machine). Knoppix recognized
and configured the card. I tried to bring up the interface with no
success: same symptoms as my Sarge installation.
The one thing I've noticed, though, is that when I get "close
enough" to the AP, I can see:
Aug 16 08:50:21 localhost pumpd[1278]: PUMP: sending discover
Aug 16 08:50:27 localhost pumpd[1278]: got dhcp offer
Aug 16 08:50:27 localhost pumpd[1278]: PUMP: sending second discover
Aug 16 08:50:57 localhost cardmgr[1067]: + Operation failed.
Aug 16 08:50:57 localhost cardmgr[1067]: + Failed to bring up eth1.
This seems consistent; I get an answer to the first discover but not
the second. The RFC for DHCP doesn't seem to require 2 discovers,
so I'm not sure what pump is doing here.
And I tried tcpdump. If eth1 was not up, tcpdump would exit. So I
tried a machine-gun approach, starting "pump -i eth1" followed by a
tcpdump. Here's the result:
----------------------------------------------------------------------
15:08:58.385577 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:02:2d:74:4a:fa, length: 300
15:08:58.395954 arp who-has 169.254.1.51 tell 169.254.1.1
15:08:58.397085 arp who-has 169.254.1.51 tell 169.254.1.1
15:08:58.398200 arp who-has 169.254.1.51 tell 169.254.1.1
15:09:02.080455 IP 169.254.1.1.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length: 293
15:09:02.083702 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:02:2d:74:4a:fa, length: 548
15:09:06.083860 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:02:2d:74:4a:fa, length: 548
15:09:13.082798 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:02:2d:74:4a:fa, length: 548
15:09:19.895539 IP 169.254.1.31.53127 > 255.255.255.255.2222: UDP, length: 106
15:09:21.896457 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:02:2d:74:4a:fa, length: 548
For comparison, here's a successful sequence from my work (closed)
connection: (I replaced my employer's real domain with "example.com")
12:02:01.448556 IP localhost.localdomain.32791 > localhost.localdomain.bootpc: S 1462952572:1462952572(0) win 32767 <mss 16396,sackOK,timestamp 278840 0,nop,wscale 0>
12:02:01.448601 IP localhost.localdomain.bootpc > localhost.localdomain.32791: R 0:0(0) ack 1462952573 win 0
12:02:01.454701 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:02:2d:74:4a:fa, length: 300
12:02:01.675489 IP 172.16.8.234 > 224.0.0.1: igmp query v2 [max resp time 1]
12:02:01.679408 snap ui/C len=207
12:02:02.669519 snap ui/C len=33
12:02:04.146455 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:02:04.351467 IP 172.16.8.41.netbios-ns > 172.16.11.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
12:02:05.170266 IP 172.16.8.41.netbios-ns > 172.16.11.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
12:02:05.170637 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:02:2d:74:4a:fa, length: 300
12:02:07.218283 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:02:07.627667 arp who-has 172.16.8.176 tell 172.16.8.253
12:02:08.651576 arp who-has 172.16.8.58 tell 172.16.8.253
12:02:10.494677 IP 172.16.9.150.netbios-ns > 172.16.11.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
12:02:10.699380 arp who-has 172.16.8.58 tell 172.16.8.253
12:02:11.314061 arp who-has 172.16.8.254 tell 172.16.9.196
12:02:11.928130 IP 172.16.9.150.netbios-ns > 172.16.11.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
12:02:12.920623 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:02:2d:74:4a:fa, length: 300
12:02:13.361956 IP 172.16.8.104.netbios-dgm > 172.16.11.255.netbios-dgm: NBT UDP PACKET(138)
12:02:13.567017 arp who-has 172.16.8.254 tell 172.16.9.119
12:02:19.095644 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:02:22.986615 arp who-has 172.16.8.254 tell 172.16.8.182
12:02:23.192098 arp who-has 172.16.9.107 tell 172.16.9.107
12:02:26.059446 arp who-has 172.16.8.129 tell 172.16.8.253
12:02:26.090627 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:02:2d:74:4a:fa, length: 300
12:02:27.286858 arp who-has 172.16.8.254 tell 172.16.9.182
12:02:31.090638 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:02:2d:74:4a:fa, length: 300
12:02:31.091234 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:02:2d:74:4a:fa, length: 300
12:02:54.558355 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:02:2d:74:4a:fa, length: 300
12:02:54.730818 IP 172.16.8.235 > 224.0.0.1: igmp query v2 [max resp time 1]
12:02:54.731492 snap ui/C len=103
12:02:55.260117 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:02:55.727927 snap ui/C len=33
12:02:55.874608 IP 172.16.9.154.netbios-dgm > 172.16.11.255.netbios-dgm: NBT UDP PACKET(138)
12:02:56.079146 arp who-has 172.16.8.254 tell 172.16.9.154
12:02:57.308356 IP 172.16.9.154.netbios-dgm > 172.16.11.255.netbios-dgm: NBT UDP PACKET(138)
12:02:57.308711 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:02:2d:74:4a:fa, length: 300
12:02:57.514184 IP 172.16.8.253.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length: 362
12:02:57.514681 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:02:2d:74:4a:fa, length: 548
12:02:57.719136 IP 172.16.8.252.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length: 341
12:02:57.719804 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:02:2d:74:4a:fa, length: 548
12:03:01.710620 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:02:2d:74:4a:fa, length: 548
12:03:01.814242 IP 172.16.8.252.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length: 341
12:03:01.975074 IP 172.16.8.234 > 224.0.0.1: igmp query v2 [max resp time 1]
12:03:01.976026 snap ui/C len=207
12:03:02.101203 IP 172.16.9.30.netbios-dgm > 172.16.11.255.netbios-dgm: NBT UDP PACKET(138)
12:03:02.101599 IP 172.16.9.180.netbios-dgm > 172.16.11.255.netbios-dgm: NBT UDP PACKET(138)
12:03:02.101867 arp who-has 172.16.8.254 tell 172.16.8.112
12:03:02.105809 arp reply 172.16.8.254 is-at 00:00:0c:07:ac:08
12:03:02.105829 IP 172.16.8.112.32836 > pkyad01.pc.example.com.domain: 36724+ PTR? 30.9.16.172.in-addr.arpa. (42)
12:03:02.120388 IP pkyad01.pc.example.com.domain > 172.16.8.112.32836: 36724 NXDomain* 0/1/0 (119)
12:03:02.120795 IP 172.16.8.112.32836 > pkyad01.pc.example.com.domain: 36725+ PTR? 180.9.16.172.in-addr.arpa. (43)
12:03:02.123587 IP pkyad01.pc.example.com.domain > 172.16.8.112.32836: 36725 NXDomain* 0/1/0 (120)
12:03:02.123886 IP 172.16.8.112.32836 > pkyad01.pc.example.com.domain: 36726+ PTR? 112.8.16.172.in-addr.arpa. (43)
12:03:02.127015 IP pkyad01.pc.example.com.domain > 172.16.8.112.32836: 36726 NXDomain 0/0/0 (43)
12:03:02.127329 IP 172.16.8.112.32836 > pkyad01.pc.example.com.domain: 36727+ PTR? 1.89.16.172.in-addr.arpa. (42)
12:03:02.129944 IP pkyad01.pc.example.com.domain > 172.16.8.112.32836: 36727* 1/0/0 (75)
12:03:02.305496 IP 172.16.8.32.netbios-dgm > 172.16.11.255.netbios-dgm: NBT UDP PACKET(138)
12:03:02.305733 IP 172.16.8.112.32836 > pkyad01.pc.example.com.domain: 36728+ PTR? 32.8.16.172.in-addr.arpa. (42)
12:03:02.308838 IP pkyad01.pc.example.com.domain > 172.16.8.112.32836: 36728 NXDomain* 0/1/0 (100)
12:03:02.715501 IP 172.16.8.182.netbios-dgm > 172.16.11.255.netbios-dgm: NBT UDP PACKET(138)
12:03:02.966491 snap ui/C len=33
12:03:03.124667 IP 172.16.9.180.netbios-dgm > 172.16.11.255.netbios-dgm: NBT UDP PACKET(138)
12:03:04.148333 IP 172.16.9.180.netbios-dgm > 172.16.11.255.netbios-dgm: NBT UDP PACKET(138)
12:03:04.148675 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:03:04.557888 IP 172.16.9.190.netbios-dgm > 172.16.11.255.netbios-dgm: NBT UDP PACKET(138)
12:03:04.558348 IP 172.16.8.112.32836 > pkyad01.pc.example.com.domain: 36729+ PTR? 190.9.16.172.in-addr.arpa. (43)
12:03:04.570752 IP pkyad01.pc.example.com.domain > 172.16.8.112.32836: 36729 NXDomain* 0/1/0 (120)
12:03:04.968184 arp who-has 172.16.8.254 tell 172.16.9.200
12:03:04.968505 IP 172.16.8.112.32836 > pkyad01.pc.example.com.domain: 36730+ PTR? 200.9.16.172.in-addr.arpa. (43)
12:03:04.971970 IP pkyad01.pc.example.com.domain > 172.16.8.112.32836: 36730 NXDomain* 0/1/0 (120)
12:03:05.172841 IP 172.16.9.180.netbios-dgm > 172.16.11.255.netbios-dgm: NBT UDP PACKET(138)
12:03:06.196174 IP 172.16.9.180.netbios-dgm > 172.16.11.255.netbios-dgm: NBT UDP PACKET(138)
12:03:07.219906 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:03:09.267629 arp who-has cabletbacklap.wireless.example.com tell 172.16.8.253
12:03:09.267988 IP 172.16.8.112.32836 > pkyad01.pc.example.com.domain: 36731+ PTR? 245.8.16.172.in-addr.arpa. (43)
12:03:09.273231 IP pkyad01.pc.example.com.domain > 172.16.8.112.32836: 36731 1/0/0 (88)
12:03:10.291684 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:03:11.520200 arp who-has 172.16.8.254 tell cblthall1200.wireless.example.com
12:03:11.520569 IP 172.16.8.112.32836 > pkyad01.pc.example.com.domain: 36732+ PTR? 246.8.16.172.in-addr.arpa. (43)
12:03:11.524402 IP pkyad01.pc.example.com.domain > 172.16.8.112.32836: 36732 1/0/0 (87)
12:03:11.929977 IP 172.16.8.49.2081 > 172.16.11.255.2190: UDP, length: 133
12:03:11.930784 IP 172.16.8.112.32836 > pkyad01.pc.example.com.domain: 36733+ PTR? 49.8.16.172.in-addr.arpa. (42)
12:03:11.933992 IP pkyad01.pc.example.com.domain > 172.16.8.112.32836: 36733 NXDomain* 0/1/0 (100)
12:03:12.953879 arp who-has 172.16.8.254 tell 172.16.8.170
12:03:12.954243 IP 172.16.8.112.32836 > pkyad01.pc.example.com.domain: 36734+ PTR? 170.8.16.172.in-addr.arpa. (43)
12:03:12.958714 IP pkyad01.pc.example.com.domain > 172.16.8.112.32836: 36734 NXDomain* 0/1/0 (101)
12:03:14.387229 arp who-has cabletbacklap.wireless.example.com tell 172.16.8.253
12:03:16.230408 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:03:19.302156 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:03:19.506857 arp who-has 172.16.8.254 tell 172.16.9.89
12:03:19.507157 IP 172.16.8.112.32836 > pkyad01.pc.example.com.domain: 36735+ PTR? 89.9.16.172.in-addr.arpa. (42)
12:03:19.515401 IP pkyad01.pc.example.com.domain > 172.16.8.112.32836: 36735 NXDomain* 0/1/0 (119)
12:03:20.124088 arp who-has 172.16.8.254 tell 172.16.9.200
12:03:21.349916 IP 172.16.9.198.netbios-ns > 172.16.11.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
12:03:21.350443 IP 172.16.8.112.32836 > pkyad01.pc.example.com.domain: 36736+ PTR? 198.9.16.172.in-addr.arpa. (43)
12:03:21.353639 IP pkyad01.pc.example.com.domain > 172.16.8.112.32836: 36736 NXDomain* 0/1/0 (120)
12:03:21.964843 IP 172.16.9.198.netbios-ns > 172.16.11.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
12:03:22.169298 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:03:28.312962 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:03:30.361050 IP 172.16.9.198.netbios-ns > 172.16.11.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
12:03:30.974892 IP 172.16.9.198.netbios-ns > 172.16.11.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
12:03:31.180799 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:03:31.793884 IP 172.16.9.198.netbios-ns > 172.16.11.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
12:03:33.432570 arp who-has 172.16.8.254 tell 172.16.9.82
12:03:33.432933 IP 172.16.8.112.32836 > pkyad01.pc.example.com.domain: 36737+ PTR? 82.9.16.172.in-addr.arpa. (42)
12:03:33.436183 IP pkyad01.pc.example.com.domain > 172.16.8.112.32836: 36737 NXDomain* 0/1/0 (119)
12:03:34.251786 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:03:34.252288 IP 172.16.9.180.netbios-dgm > 172.16.11.255.netbios-dgm: NBT UDP PACKET(138)
12:03:34.660804 arp who-has 172.16.8.254 tell 172.16.9.128
12:03:34.661117 IP 172.16.8.112.32836 > pkyad01.pc.example.com.domain: 36738+ PTR? 128.9.16.172.in-addr.arpa. (43)
12:03:34.667384 IP pkyad01.pc.example.com.domain > 172.16.8.112.32836: 36738 NXDomain* 0/1/0 (120)
12:03:35.275197 arp who-has 172.16.8.254 tell 172.16.9.200
12:03:36.095414 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:7d:08:ae:f9, length: 315
12:03:36.299728 IP 172.16.8.252.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length: 374
12:03:36.300058 arp who-has 172.16.8.118 tell 172.16.8.118
12:03:36.300576 IP 172.16.8.112.32836 > pkyad01.pc.example.com.domain: 36739+ PTR? 118.8.16.172.in-addr.arpa. (43)
12:03:36.306593 IP pkyad01.pc.example.com.domain > 172.16.8.112.32836: 36739 NXDomain* 0/1/0 (101)
12:03:36.708710 arp who-has 172.16.8.118 tell 172.16.8.118
12:03:37.323238 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:03:38.961383 arp who-has 172.16.8.254 tell 172.16.8.118
12:03:39.780405 arp who-has 172.16.8.254 tell 172.16.8.140
12:03:39.780771 IP 172.16.8.112.32836 > pkyad01.pc.example.com.domain: 36740+ PTR? 140.8.16.172.in-addr.arpa. (43)
12:03:39.784928 IP pkyad01.pc.example.com.domain > 172.16.8.112.32836: 36740 NXDomain* 0/1/0 (101)
12:03:40.190776 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:03:44.490432 arp who-has 172.16.8.254 tell 172.16.9.101
12:03:44.491056 IP 172.16.8.112.32836 > pkyad01.pc.example.com.domain: 36741+ PTR? 101.9.16.172.in-addr.arpa. (43)
12:03:44.501956 IP pkyad01.pc.example.com.domain > 172.16.8.112.32836: 36741 NXDomain* 0/1/0 (120)
12:03:49.200616 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:03:50.429154 arp who-has 172.16.8.254 tell 172.16.9.200
12:03:52.272422 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:03:55.344141 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:03:58.211513 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:04:01.282914 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:04:02.307689 arp who-has 172.16.8.254 tell 172.16.8.156
12:04:02.308055 IP 172.16.8.112.32836 > pkyad01.pc.example.com.domain: 36742+ PTR? 156.8.16.172.in-addr.arpa. (43)
12:04:02.311307 IP pkyad01.pc.example.com.domain > 172.16.8.112.32836: 36742 NXDomain 0/1/0 (101)
12:04:04.354706 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:04:05.587814 arp who-has 172.16.8.254 tell 172.16.9.200
12:04:07.221974 IP 172.16.8.182.1718 > 255.255.255.255.192: UDP, length: 116
12:04:09.269663 arp who-has 172.16.8.254 tell 172.16.8.114
12:04:09.269963 arp who-has 172.16.8.254 tell 172.16.8.114
12:04:09.270150 IP 172.16.8.112.32836 > pkyad01.pc.example.com.domain: 36743+ PTR? 114.8.16.172.in-addr.arpa. (43)
12:04:09.273267 IP pkyad01.pc.example.com.domain > 172.16.8.112.32836: 36743 NXDomain* 0/1/0 (101)
----------------------------------------------------------------------
There's undoubtedly a lot of other traffic mixed in here. My card's
MAC is: 00:02:2d:74:4a:fa, and I eventually got IP: 172.16.8.112.
I also tried KWifimanager under Knoppix: once I hit the "scan"
button, it popped up a list of one AP (the name of the coffee shop),
and when I hit OK, iwconfig showed this ESSID set, but I still got
the "Failed to bring up eth1" message and no IP.
I'm convinced the first discover is what sets the ESSID (which I've
seen happen several times), but somehow the second discover is not
working.
But I have rudimentary knowledge of tcpdump (I've debugged some rarp
stuff years ago under VMS, but we never had DHCP to contend with,
and BOOTP just worked). So if anyone knows how to get more detail,
and how to get it to capture only dhcp-related info, I'd appreciate
it.
FWIW, I also tried some other live CD's. Gentoo won't even give me
an "unsupported card in slot 1" error; it seems to notice insert and
remove events, but doesn't _do_ anything about them. Basilisk (FC3)
didn't recognize the (MN-520) card. Kanotix (Debian sid based)
recognized it and used the "hostap_cs" driver.
So, some progress, and I believe this is a DHCP negotiation problem.
But I don't know how to see _what_ is failing. Hopefully, someone
can decode something from the tcpdump.
Cheers,
Jeff Root
More information about the TAG
mailing list