[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: wicd trouble -- continued



On Sat 30 Jul 2016 at 12:45:50 +0100, Brian wrote:

> On Fri 29 Jul 2016 at 16:44:43 -0600, ghe wrote:
> 
> > When I set up a static IP, wicd fills in the net mask and the default router
> > automatically. I don't know where it gets the info, but the values and the
> > table are the same as the table on a known working, E'net host on the net
> > (sbox) built at boot from /e/n/i:
> 
> It was worth asking because the netmask and gateway can be edited from
> the values provided by wicd. It gets the netmask from the IP address. I
> do not know how it determines the gateway.

That was a bit of a guess about how wicd fills in the netmask field; I
had in mind it *computed" it from the IP address. Looking at netentry.py
in /usr/usr/share/wicd/gtk it appears its approach is less sophisticated.
An IP beginning with 172 get 255.240.0.0. 255.0.0.0 is allocated for IPs
eginning with 10. Everything else (including 192.168) gets 255.255.255.0.

The gateway IP is formed by adding .1 at the end. So you have the nice
situation that an interface IP of 192.168.7.1 (which could be valid) has
192.168.7.1 as a gateway. That will do wonders for getting out on the
internet! Wicd would indicate it has successfully connected (which it
sort of has) but it would be head scratching time.


Reply to: