Re: wicd trouble -- continued

[Lisi Reisz <lisi.reisz@gmail.com>]

On Thursday 28 July 2016 22:15:52 Glenn English wrote:
> > On Jul 28, 2016, at 1:27 PM, David Wright <deblis@lionunicorn.co.uk>
> > wrote:
> >
> > The answer may lie in the logs. Mine contains the lines
> >
> > 2016/07/28 07:35:36 :: Setting false IP...             ←----------
>
> Ah! They set an IP that will get to the DHCP server. I assume that the AP
> will send out something on the Ethernet that makes some sense to the DHCP
> server.

Here is a snippet from my routers log while wicd was trying - and failing to 
connect.  
         
[WLAN access allowed]from MAC: xxxx Saturday, July 02,2016 
23:00:40          
[WLAN access allowed]from MAC: xxxx Saturday, July 02,2016 
23:00:37          
[WLAN access allowed]from MAC: xxxx Saturday, July 02,2016 
23:00:17 

 When it finally succeeded it was because the router gave it an IP.

[WLAN access allowed]from MAC: xxxx Sunday, July 03,2016 00:08:31            
[WLAN access allowed]from MAC: xxxx Sunday, July 03,2016 00:06:42            
[WLAN access allowed]from MAC: xxxx Sunday, July 03,2016 00:06:29            
[WLAN access allowed]from MAC: xxxx Sunday, July 03,2016 00:06:12            
[WLAN access allowed]from MAC: xxxx Sunday, July 03,2016 00:06:01            
[WLAN access allowed]from MAC: xxxx Sunday, July 03,2016 00:05:47            
[WLAN access allowed]from MAC: xxxx Sunday, July 03,2016 00:05:14            
[DHCP IP: (192.168.0.6)] to MAC address xxxx Sunday, July 03,2016 00:04:30   

Lisi
   





>
> Might be nice if the log said what the false IP was.
>
> > 2016/07/28 07:35:36 :: Flushing the routing table...
>
> And that's when wicd deletes the routes. But if the table had been set up
> by wicd to use the eth0 interface, it would have been useless. I know this
> isn't correct because I switch back and forth between WiFi and Ethernet all
> the time. So wicd doesn't use the routing table?
>
> > 2016/07/28 07:35:47 :: not verifying                   ←----------
>
> Not verifying *what*? Its new IP? The routing table? Pinging the AP?
>
> > 2016/07/28 07:35:47 :: Connecting thread exiting.
> > 2016/07/28 07:35:51 :: Sending connection attempt result success
>
> Looks like it may work on DHCP since it doesn't verify something...