When I attempt to connect to my wrouter, wlassistant cogitates for a second and then tells me that the connection failed. What's strange about this is that the wrouter actually does lease an ip to the wireless client, and I'm able to get out on the internet just fine. In addition, if I close and re-open wlassistant, it will show that I'm connected.
Here's some amplifying data courtesy of tcpdump:
It seems as if after getting an IP, wlassistant attempts to ping 192.168.0.1 for some reason. In my setup, where the wireless clients and wired hosts are separated into two subnets (by my smoothwall), that's the IP of the "Green" network. I imagine that wlassistant is trying to ping the DHCP server that gave it the IP or something, but that IP value appears to be hardcoded, which is silly.
Can anyone further explain this behavior to me, or perhaps offer a workaround or fix? It's just an annoying and useless message to have to put up with.
Here's some amplifying data courtesy of tcpdump:
tcpdump: WARNING: ath0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ath0, link-type EN10MB (Ethernet), capture size 96 bytes
17:06:11.001517 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request
from 00:15:e9:72:e0:fd (oui Unknown), length: 300
17:06:11.005751 arp who-has 192.168.2.101 tell 192.168.2.1
17:06:12.660698 IP 192.168.2.1.bootps > 192.168.2.101.bootpc: BOOTP/DHCP, Reply,
length: 290
17:06:12.661423 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request
from 00:15:e9:72:e0:fd (oui Unknown), length: 300
17:06:12.666211 arp who-has 192.168.2.101 tell 192.168.2.1
17:06:14.327291 IP 192.168.2.1.bootps > 192.168.2.101.bootpc: BOOTP/DHCP, Reply,
length: 290
17:06:14.725065 arp who-has 192.168.2.1 tell 192.168.2.101
17:06:14.737956 arp reply 192.168.2.1 is-at 00:0f:b5:68:42:88 (oui Unknown)
17:06:14.738004 IP 192.168.2.101 > 192.168.0.1: ICMP echo request, id 50193, seq
1, length 64
17:06:14.738688 IP 192.168.2.101.1024 > ns1.hr.cox.net.domain: 25741+ PTR? 1.0.
168.192.in-addr.arpa. (42)
17:06:14.742322 IP 192.168.0.1 > 192.168.2.101: ICMP 192.168.0.1 protocol 1 port
53622 unreachable, length 92
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ath0, link-type EN10MB (Ethernet), capture size 96 bytes
17:06:11.001517 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request
from 00:15:e9:72:e0:fd (oui Unknown), length: 300
17:06:11.005751 arp who-has 192.168.2.101 tell 192.168.2.1
17:06:12.660698 IP 192.168.2.1.bootps > 192.168.2.101.bootpc: BOOTP/DHCP, Reply,
length: 290
17:06:12.661423 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request
from 00:15:e9:72:e0:fd (oui Unknown), length: 300
17:06:12.666211 arp who-has 192.168.2.101 tell 192.168.2.1
17:06:14.327291 IP 192.168.2.1.bootps > 192.168.2.101.bootpc: BOOTP/DHCP, Reply,
length: 290
17:06:14.725065 arp who-has 192.168.2.1 tell 192.168.2.101
17:06:14.737956 arp reply 192.168.2.1 is-at 00:0f:b5:68:42:88 (oui Unknown)
17:06:14.738004 IP 192.168.2.101 > 192.168.0.1: ICMP echo request, id 50193, seq
1, length 64
17:06:14.738688 IP 192.168.2.101.1024 > ns1.hr.cox.net.domain: 25741+ PTR? 1.0.
168.192.in-addr.arpa. (42)
17:06:14.742322 IP 192.168.0.1 > 192.168.2.101: ICMP 192.168.0.1 protocol 1 port
53622 unreachable, length 92
Can anyone further explain this behavior to me, or perhaps offer a workaround or fix? It's just an annoying and useless message to have to put up with.