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

Calling all Linux wizards to summon their powers and HELP!

The Problem:
================================================== ======================
I have LAN access but cannot access any remote (WAN) host (or website).

Examples:
--------
What I CAN do:
a) Able to ping router on 192.168.2.1
b) Able to ping colleague's PC 192.168.2.2
c) Able to configure router using web interface on 192.168.2.1 fine.

What I CANNOT do:
http://www.google.co.uk (Error = "www.google.co.uk could not be found.
Please check the name and try again.")
================================================== ======================


Configuration:
--------------
Linux Suse 9.2

Belkin ADSL Modem with Built-in Wireless Router
Model: F5D7630-4A (ver 1212uk)

D-Link DWL-610 Wireless PCMCIA Card
Driver: DriverLoader

Network:
DHCP Enabled
Infrastructure
Channel 11
IP Forwarding ON
128 bit WEP (enabled) HEX
Gateway 192.168.2.1
ESSID belkin54g


Troubleshooting
----------------
Failed attempts:
X) I've disabled the firewall.
X) I've disabled WEP.
x) I've upgraded router's firmware.
x) Various command-line utilities (see below)


(Console Output):

Traceroute
----------

(Using DNS)
localhost:~# traceroute www.google.co.uk <return>
www.google.co.uk: Temporary failure in name resolution

(Using IP Address)
localhost:~# traceroute 66.102.9.104 <return>
traceroute to 66.102.9.104 (66.102.9.104), 30 hops max, 40 byte packets
Unable to connect to 66.102.9.104: Network is unreachable


IWCONFIG
---------
localhost:~# iwconfig <return>

wlan0 IEEE 802.11-DS ESSID:"belkin54g" Nickname:"atlantis"
Mode:Managed Frequency:2.462 GHz Access Point:
00:20:E14:1C:B2
Bit Rate=11 Mb/s Tx-Power=20 dBm
RTS thrff Fragment thrff
Encryption key:<KEY> Security mode:restricted
Power Managementff
Link Quality:35/94 Signal level:-51 dBm Noise level:-154
dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

IFCONFIG
---------
localhost:~# ifconfig <return>

wlan0 Link encap:Ethernet HWaddr 00:12:66:58:23:1C
inet addr:192.168.2.3 Bcast:192.168.2.255
Mask:255.255.255.0
inet6 addr: fe80::20d:88ff:fe58:531c/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:530 errors:0 dropped:0 overruns:0 frame:0
TX packets:590 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:195057 (190.4 Kb) TX bytes:56885 (55.5 Kb)

IFUP
-----
localhost:~# ifup wlan0 <return>

wlan0 device: D-Link System Inc DWL-510 2.4GHz Wireless PCI Adapter
(rev 20)
wlan0 configuration: wlan-id-00:12:66:58:23:1C
Starting DHCP Client Daemon on wlan0... . IP/Netmask: 192.168.2.3 /
255.255.255.0

RESOLV.CONF
Contents of /etc/resolv.conf (actual IP addresses are of course
different):
search home
nameserver 192.168.168.1
nameserver 192.168.168.8



godffreypratt@yahoo.co.uk

(E-Mail Removed) wrote:
> Calling all Linux wizards to summon their powers and HELP!
>
> The Problem:
> ================================================== ======================
> I have LAN access but cannot access any remote (WAN) host (or website).
>
> Examples:
> --------
> What I CAN do:
> a) Able to ping router on 192.168.2.1
> b) Able to ping colleague's PC 192.168.2.2
> c) Able to configure router using web interface on 192.168.2.1 fine.
>
> What I CANNOT do:
> http://www.google.co.uk (Error = "www.google.co.uk could not be found.
> Please check the name and try again.")
> ================================================== ======================

--- clip clip ---

> RESOLV.CONF
> Contents of /etc/resolv.conf (actual IP addresses are of course
> different):
> search home
> nameserver 192.168.168.1
> nameserver 192.168.168.8
>

This has the feel of a name service problem.

Can you ping your name servers?

The addresses look suspect, but can be OK. If you have a problem
with them, there is no sense in obscuring them.

--

Tauno Voipio
tauno voipio (at) iki fi

Hiya Tauno

No I can't ping the (real) nameservers. The hosts are "unreachable".

(Obscuring the real IP addresses is just a precaution).
Can you (or anyone else) offer anything more?

Thank you.

(E-Mail Removed) wrote:
>
> Belkin ADSL Modem with Built-in Wireless Router
> Model: F5D7630-4A (ver 1212uk)
>
> Network:
> DHCP Enabled
> Infrastructure
> Channel 11
> IP Forwarding ON
> 128 bit WEP (enabled) HEX
> Gateway 192.168.2.1
> ESSID belkin54g
> [...]
> localhost:~# traceroute 66.102.9.104 <return>
> traceroute to 66.102.9.104 (66.102.9.104), 30 hops max, 40 byte packets
> Unable to connect to 66.102.9.104: Network is unreachable

Did you enable Network Address Translation on your w/less router?

--
andrei

(E-Mail Removed) wrote:
> Hiya Tauno
>
> No I can't ping the (real) nameservers. The hosts are "unreachable".
>
> (Obscuring the real IP addresses is just a precaution).
> Can you (or anyone else) offer anything more?
>

OK.

There is no danger in showing the real nameservers,
if they belong to the ISP, they are pretty public anyway.

Does the router report that it has an ADSL connection?

Is the router set up as the default gateway in the
local net (WLAN) ?

The first task is to ensure that the router has
a connection to the upstream companion router. If
there is a way to force the router to make a ping
to the ISP next-hop router, it should be used to
veirfy the network connectivity.

It seems that you have an internal network using
RFC 1918 private addresses 192.168.2.x. There is no
danger in publishing them: they are inaccessible
from the outside world anyway.

Please show the results of

route -n

when the WLAN link is up.

Sorry, I do not know the details of the Belkin
router set-up. Someone better knowledgeable may
give the details.

--

Tauno Voipio
tauno voipio (at) iki fi

(E-Mail Removed) wrote:

> Calling all Linux wizards to summon their powers and HELP!
>

Check your dns settings and default route. What happens if you try an
external site, by using the IP address, instead of host name?