(Wireless) LAN access fine but WAN (web) access not working!

Just to update those who are following this thread and offering
whatever help they can, the following troubleshooting info maybe
helpful:

PING
-----

(LAN):
localhost:~# ping friendsPC <return>
Works perfectly.

localhost:~# ping 192.168.2.4 <return>
Works perfectly.


(WAN):
localhost:~# ping www.google.co.uk <return>
unknown host www.google.co.uk

localhost:~# ping 66.102.9.104 <return>
connect: Network is unreachable.

ROUTE -N
------------
localhost:~# route -n <return>

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0
0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0
0 wlan0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
0 lo

Please note, for network controller wlan0 I have indeed configured my
router (IP) 192.168.2.1 as the default gateway. I have no idea how
"route -n" works or what it purports to show (above).


Godffrey

Godffrey wrote:
> localhost:~# ping 66.102.9.104 <return>
> connect: Network is unreachable.
>
> ROUTE -N
> ------------
> localhost:~# route -n <return>
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref
> Use Iface
> 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0
> 0 wlan0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0
> 0 wlan0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
> 0 lo
>
> Please note, for network controller wlan0 I have indeed configured my
> router (IP) 192.168.2.1 as the default gateway. I have no idea how
> "route -n" works or what it purports to show (above).

It show you haven't a default route. You should have something like:
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 wlan0

Try "route add default gw 192.168.2.1"


--
Paul Black mailto(E-Mail Removed)
Oxford Semiconductor Ltd http://www.oxsemi.com
25 Milton Park, Abingdon, Tel: +44 (0) 1235 824 909
Oxfordshire. OX14 4SH Fax: +44 (0) 1235 821 141

(E-Mail Removed) (Godffrey) wrote:
>Just to update those who are following this thread and offering
>whatever help they can, the following troubleshooting info maybe
>helpful:
>
>PING
>-----
>
>(LAN):
>localhost:~# ping friendsPC <return>
>Works perfectly.
>
>localhost:~# ping 192.168.2.4 <return>
>Works perfectly.
>
>(WAN):
>localhost:~# ping www.google.co.uk <return>
>unknown host www.google.co.uk
>
>localhost:~# ping 66.102.9.104 <return>
>connect: Network is unreachable.
>
>ROUTE -N
>------------
>localhost:~# route -n <return>
>
>Kernel IP routing table
>Destination Gateway Genmask Flags Metric Ref
>Use Iface
>192.168.2.0 0.0.0.0 255.255.255.0 U 0 0
>0 wlan0
>169.254.0.0 0.0.0.0 255.255.0.0 U 0 0
>0 wlan0
>127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
>0 lo
>
>Please note, for network controller wlan0 I have indeed configured my
>router (IP) 192.168.2.1 as the default gateway. I have no idea how
>"route -n" works or what it purports to show (above).

"route -n" shows your route table, and the -n option causes it
to use dotted quad numbers to display the IP addresses rather
than looking up the "names" of these hosts (which you want,
because your ability to do the lookups is non-functional).

What the above tells you is that you have a loopback interface
correctly configured (I won't bother with what that details),
and two other possible routes, both going to device wlan0.

Any IP address in the range of 192.168.2.x, where x can be any
valid number, will be routed by the first entry in your table.
That is because of the combination of the "Destination" IP
address and the "Genmask". The 255 entries in the mask mean it
will have to be the exact same number as in the Destination.
The 0 means that one can be any valid number.

The second line provides a route for any IP address 169.254.x.x,
which will also be sent to the wlan0 interface.

The problem for the addresses you've mentioned trying to ping is
that no route matches either of them, nor is there a route to
whatever name server you might be trying to use to get the
dotted quad addresses from the hostnames.

ping 192.168.2.4

This one works because it is routed by the first line, to device
wlan0.

ping www.google.co.uk

This one cannot determine the actual address, because there is
no route for whatever the address of the name server is.

ping 66.102.9.104

This one fails because there is no route table entry that
matches.

What you need is a default route, one that grabs anything
not matching one of the above. It almost certainly *must*
include a gateway too. Hence a command something like this will
do the trick:

route add default gw <router_IP> wlan0

Replace the <route_IP> with either a hostname found in
/etc/hosts, or a dotted quad IP address. It should of course be
the address of some host that will forward packets to the
Internet. It might be a router or a firewall. Note that it
*must* have a route set that works for it, hence if it matches
either of the 192.168.2.x or 169.254.x.x routes already there,
it will work. However, if it has some other address you'll need
to first provide a route for it. For example, if it has an
address of 192.168.3.4, it won't match either of the existing
routes, and before it would work you'd need something like this,

route add -host <router IP> dev wlan0

Another way to add exactly the same route, is

route add -net <router IP> netmask 255.255.255.255 dev wlan0

Put the appropriate commands into the right init scripts (which
depend on which distribution you have), and it should all fly.

Note too, that I am assuming your wireless access point is able
to correctly route already. It needs to have the ability to
forward IP packets and must have routes to the particular
devices that you've listed in the route table on this wireless
client.

--
Floyd L. Davidson <http://web.newsguy.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska) (E-Mail Removed)

Godffrey wrote:
>
> route -n
> --------
> localhost:~# route -n <return>
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref
> Use Iface
> 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0
> 0 wlan0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0
> 0 wlan0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
> 0 lo
>
> Please note, for network controller wlan0 I have indeed configured my
> router (IP) 192.168.2.1 as the default gateway. I have no idea how
> "route -n" works or what it purports to show (above).

The only thing is that the default gateway is not in the
routing table.

Try

route add default gw 192.168.2.1

--

Tauno Voipio
tauno voipio (at) iki fi