> On Jul 28, 2016, at 5:36 AM, Brian <a...@cityscape.co.uk> wrote: > > Indeed; presumably it has decided association and authentication with > the access point has successfully taken place and the interface has got > an IP number. However, there does not appear to be routing between the > interface and the AP.
When I turned on the laptop, the table was empty -- no default, no localnet. I asked wicd to connect to one of my wireless networks and watched the table. It was empty for a while, then was populated with what looked to me like a reasonable routing table. The firewall downstairs (192.168.3.1/32) as default, and the proper network as localnet (192.168.3.0/24). wlan0 as the interface for both. Then after a while, it was emptied again. ifconfig -a : All three interfaces (lo, eth0, wlan0); lo set to 127.0.0.1, no IPs on the others. wlan0 showed 8 RX packets (816 B) and 100 TX (17.2 B). No errors in either direction. systemctl stop wicd.service: Your standard *nix answer -- nothing. In a few seconds, wicd threw up a window saying the wicd daemon had shut down. wpa_suplicant -i wlan0 -C /run/wpa_supplicant: "Successfully initialized wpa_supplicant" Then it hung (hanged). When I ctl-c'ed, it said "wlan0: CTRL-EVENT-TERMINATING" wpi_cli (2.3) ... "Could not connect to wpa_supplicant: (null) - re-trying" And hang. add_network Nothing. It did let me type, and I expected nothing from the frozen program, but I was hoping. > How does that go? It didn't go too well. 'ps aux | egrep wpa' shows that WS doesn't seem to be running. Ah! When I ran WS on one terminal, lets it run, and open another terminal, wpa_cli gives a '>' prompt. add-network "0" set_network 0 ssid "slsware.wif.2T" OK set_network psk "<PW>" (didn't like that, but was happy when I inserted a '0') OK enable_network 0 OK <3>CTRL-EVENT-STARTED <3>CTRL-EVENT-RESULTS <3>WPS-AP-AVAILABLE > Same thing over and over... At an '>' I entered status 0. It said: wpa_state=SCANNING address=00:1f:3c:cd:69:9f uuid=6754040b-09ff-57cb-ab53-ae8cfb180455 Then went back to the scanning again. dhclient -v wlan0 "No working leases in persistent database - sleeping" That doesn't seem too odd since nobody that I know of asked anything from DHCP. But. When I tried again after telling wicd to use DHCP instead of a static IP, it successfully connected. It even got the IP I'd set up for the laptop over on the DHCP server's config. Now dhclient -v wlan0 talks about how the server received a request and fulfilled it. The wicd icon has that green bar saying WiFi is on. The routing table looks reasonable. And I can ssh around the LAN, the DMZ, and get out to the WAN. That went pretty well, and I thank you very much for the guidance. But why? Why does DHCP work and a static IP doesn't? That's not too cool for a machine I use for admin'ing the servers. I'm moving in a few weeks, and I really need this connectivity to get things working. I'd appreciate you guys telling me what's going on here, but I'll probably just settle for DHCP WiFi for a while. I'm thinking of trying to build a localhost DHCP server... Or maybe even going so far as figuring out how to use /.../interfaces. -- Glenn English
