OK so it's not such a trauma now, after great help from Neill and "Fozzy" - my routing still doesn't work but at least I'm now in a position to provide more intelligent information than my last post.
OK here's a summary, LAN with 3 machines 1 x Win2k 10.10.10.100 1 x win98 10.10.10.99 1 x Mandrake 7.1 10.10.10.200 (called it route66 optimistically) netmask for all of these is 255.255.255.0
10.10.10.200 connects via external modem (ttyS1) to internet (ppp0)
route gives me this......
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface ba3-cvx3.cablei * 255.255.255.255 UH 0 0 0 ppp0 route66 * 255.255.255.255 UH 0 0 0 eth0 10.10.10.0 * 255.255.255.0 U 0 0 0 eth0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo default ba3-cvx3.cablei 0.0.0.0 UG 0 0 0 ppp0
now, if I understand this right the first 3 lines of this output should be doing the job so can anybody tell from this why I can't get to the outside world from 10.10.10.100 or 10.10.10.99 - network comms are fine as SMB, Telnet, FTP HTTP all work to the 10.10.10.200 box but not beyond it
hopefully :)
Dave david@davidhowe.co.uk
David Howe wrote:
now, if I understand this right the first 3 lines of this output should be doing the job.
the routing table is for the local machine, you need to instruct the kernel that you wish to forward the 10.10.10.0 packets out over the ppp0 device, BUT that is not enough, IF the 10.10.10.0 packets do get out over the internet, where does the reply packets go ?? This is why you need NAT, it basically masquerades the connection so it apears to come from the local machine, but when the kernel recieves a packet destined to another network, it re-writes the packets headers and forwards the packet over the correct interface... A simple route will not work!! NAT is the way to go...
hth Sz
-
David Howe -
Neill Newman