[Gllug] wicd manager

Tue Oct 27 16:27:26 UTC 2009

On Mon, 26 Oct 2009, Lucy Peters wrote:

> > There you go - no DNS address! A quick fix is to log in to the free
> > option at http://www.opendns.com and create a free account, then use
> > the DNS addresses provided. Another option is to use the DNS servers
> > at 4.2.2.x, where x is 1 to 6 (ping each of them to see which is
> > fastest), though you'll find that they are a lot slower than using
> > openDNS.
> 
> These are the readings after I have inserted the Primary DNS address
> 208.67.220.222 and Secondary DNS address 208.67.220.220 from
> www.opendns.com 

As your traceroute -n test doesn't work, let's ignore DNS entirely for
the short term it's a wild goose chase at this point.

> Connection 
> 
> DHCP
> Client Disconnected   

This is an issue if using your wifi router as the main NAT router for
your home network.  This could be a disconnection in the wan<->cable
router, maybe bad network cable.  I already asked you to confirm it was
okay by using that same cable when using wired in to the cable router,
you've not commented on that in that previous email.  There were other
things to try too, please go over the older emails from me and try all
the stuff.

It could possibly also be a configuration option, basically this is
supposed to have gained an IP from your cable router via dhcp.

> default via 86.1.108.1 dev eth0 

> > Okay so when you connect a computer to the cable router it's
> > probably doing some direct passthrough, it's not likely to be
> > providing you with a small subnet of direct Internet routeable IPs.
> > This could be pppoa pppoe or just the router letting you have the
> > valid IP updating via dhcp and keeping something else internal
> > itself to its def.gw (the 10.  address we saw before presumably).

> > These details:
> > 
> > IP: 86.1.111.198 (mask 255.255.252.0 - this is important due to the
> > gw)
> > gw: 86.1.108.1
> > DNS: 194.168.4.100 and 194.168.8.100
> 
> how do you get the def.gw readings?

The netstat -nr and ip route sh commands, both pointed us at a def.gw
(default gateway) of 86.1.108.1.

I recommend checking you've followed previous suggestions in earlier
emails, on your reply emails you've sometimes not commented on some of
the stuff suggested.

Here is a quick summery of where we've got to:

 - The hard part of getting wifi working on Linux works, we know this as
   you've shown us the output of ping from your eth1 containing
   192.168.0.104 to its gateway 192.168.0.1.

 - We know you don't have any issues with Virginmedia's network* or DNS
   as when you use wired you get DNS resolution and traceroutes succeed.

 - When wired, your device (laptop?) gains an IP of 86.1.111.198
   (probably dynamic and likely to vary in the 86.1.something range).
   With a default gateway of: 86.1.108.1

 - When connected wirelessly to your wifi router you're in the
   192.168.0.x range, so it's maintaining its own network complete with
   DHCP server (which we suggested to disable, but that's not
   necessarily what we need to do here).

 - A traceroute you showed before (while wired) started:
traceroute to www.wikipedia.com (91.198.174.2), 30 hops max, 60 byte packets
1 10.219.60.1 (10.219.60.1) 26.547 ms 26.505 ms 26.445 ms 
   This shows working DNS and indicates you pass through a 10.something
   range.  This is not routable on the Internet and so presumably is the
   Internal range used by Virgin between your cable router and their
   main Internet gateways**.

Things to try and what should work:

 - Plugging the network cable from the cable router in to a non WAN port
   of the wifi router should mean the wireless network at the house
   doesn't relate to anything the wifi router is trying to do which is
   fancy or routery.  This should let your eth1 pickup, via dhcp, the
   86.1.something IP and GW and start working as before.

 - Plugging a cable in to the wifi router ports in the same combination
   as before (not using wan) should treat the wifi router as just a
   switch.  This is also a test of that connection from cable router to
   wifi router.

 - Using the wifi router as a router would be useful, albeit VERY slight
   disadvantage of being NATed (for games/torrent maybe).  This needs
   the wifi router to be your connected device to the cable router and
   will need the WAN port used, DHCP should let the wifi router pick up
   its master IP, if this doesn't work you could use the web UI and put
   in the IP/GW/DNS settings as seen when your laptop was plugged in
   (86.1. etc).

*This doesn't mean they're not rubbish as an ISP or have crap DNS, they
might, but this isn't your issue.

**It would help if others with a VM Cable router could step in and
comment about how these work at this point.

Damion
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug