On Mon, 11 Dec 2006, in the Usenet newsgroup comp.os.linux.networking, in
article <eljflk$lb7$(E-Mail Removed)>, AAW wrote:
>As part of my continuing adventures with trying to get a linux box to
>act as a router I have set up routing on a server and I am testing it
>using a laptop. Looks like routing is ok but I?m not getting any web
>access on the laptop.
In your post last week, you stated that you had change some DHCP options
are were able to ping both NICs of the router. Please show the routing
table on the laptop so that we know it's OK. Also, can you display the
routing table on the modem? What does it look like?
>What I have:
OK
>The laptop gets its address via DHCP from the PS server. I set the DNS
>server to 192.168.1.1 and the laptop sets this up as its primary DNS server.
Is the laptop able to resolve names?
>Any idea why the laptop has no web access?
The next tool you want to learn to use is a packet sniffer. FC5 came with
ethereal-0.10.14-3.2, ethereal-gnome-0.10.14-3.2, and tcpdump-3.9.4-2.2.
Please see that one of these is installed, and read the documentation.
Sniff all of the traffic on the eth2 side. Do you see the laptop make
a DNS query? Does it get a reply? Does the laptop make a connection
attempt to a remote host like
www.uio.no? Does the remote host reply?
Then look again on the eth1 side. There may be a DNS query/response if
the caching nameserver doesn't have the answer. Then you should see the
connection attempt from the laptop to the remote. Do you see a reply?
You are using two RFC1918 network addresses (192.168.0.x and 192.168.1.x).
Does the modem connected to eth1 know of the existence of 192.168.1.x?
Does it know how to reach the laptop? (There has to be an entry in it's
routing table with your 'router' listed as the gateway to this network,
OR your router must be doing proxyarp).
Old guy