[Sheflug] Re: Re: Routing Problem

[Richard <nospam [at] sheflug.co.uk>]

Alex

Alex Hudson wrote:

 Bring up the isdn connection. From *that* machine
> (not one on the network), attempt to ping your isp,

Yes, done that and it's fine :)

>     /sbin/traceroute 200.199.199.200 -i ippp0

missing out the /sbin bit because it doesn't work that way on my
machine....

"traceroute 200.199.199.200 -i ippp0" reveals...

"traceroute to 200.199.199.200, 30 hops max, 40 byte packets
1 amundssen.rack.access.zetnet.net  (194.247.47.251) 39ms 40ms 40ms
1 manrouter.zetnet.net 41ms 41ms 41ms
3 zet-manap2.zetnet.net
4 
5   More of it here
6 
7 if-12-1-0.bb2.Manchester.Teleglobe.net (195.219.67.133) 45ms 45ms
44ms

> So, onto the network problem. Firstly, on the client machines, get rid of
> any non-default route information: that means default gateways, static
> routes, anything else you might have in there. Just make sure the machine is
> configured with the correct ip address in the 192.168.1.n range, being
> careful that n is *not* 0 or 255 ;) No gateway, no nothing else, it won't
> need it. A 'netstat -r' will again show the eth0 route to the 192.168.1.*
> network. A 'ping 192.168.1.1' definitely ought to work.

Done that and I can ping 192.168.1.0 but not 192.168.1.1 from the
notebook to the gateway.

Since I did......

ipchains -F forward
ipchains -P forward ACCEPT

as Stephen suggested I've not been able to ping 192.168.1.1 from the
notebook to the gateway machine.  Haven't been able to ping
192.168.1.3 from the gateway to the notebook either.  Do I need to do
something to flush these rules from the gateway machine ?

 Set ping going, and
> if nothing is coming back, see if the lights are flashing on the hub & isdn
> machine.

 If it's not working, on one virtual console run '/sbin/tcpdump -i
> eth0', and on the other run ping again. Go back to the tcpdump console  - if
> stuff is happening, and every line has a '>' in it, your machine is working
> fine. If there's an equal number of lines containing '<' then you have some
> dodgy packet filtering rules or something which are stopping you seeing the
> pings on the local machine. Assuming they're all '>' lines, then the problem
> is with the other machine (given the netstat output previously, though, I
> don't think this is the case, unless again you have dodgy packet filtering
> rules in place).

Done this and put 'tcpdump -i eth0' on the gateway box.  Tried pinging
with 192.168.1.1 or 0 and nothing happens anywhere.  How do I get rid
of the ipchains rules ?

Thanks

-- 
Richard

---------------------------------------------------------------------
Sheffield Linux User's Group - http://www.sheflug.co.uk
To unsubscribe from this list send mail to
- <sheflug-request [at] vuw.ac.nz> - with the word 
 "unsubscribe" in the body of the message. 

  GNU the choice of a complete generation.