Problems with routing
There are three computers in this LAN: two with Linux and the other
one with Windows. Things got a little complicated when the
Windows-box replaced another Linux-system and I had to buy a second
ethernet card for the central server. Now the configuration is as
follows:
192.168.65.72 [L], 192.168.65.65 and 192.168.64.64 [L server],
192.168.64.1 [W].
The Windows box is connected to the central server's ethernet card
with the address 192.168.64.64.
Currently, only 192.168.65.72 has a modem. I want to transfer it to
the server shortly, but I've been playing with it as it is now. So
192.168.65.72 connects to the Internet and 192.168.65.65 can use it
as a gateway. That's OK. Now the Windows box can only connect to the
server, but cannot ping 192.168.65.72 and it cannot connect to the
Internet -- I think the problem is that I don't know how to add the
correct route to it. Can anyone suggest what to do?
route -n on 192.168.65.72:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
217.72.64.28 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
192.168.65.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 217.72.64.28 0.0.0.0 UG 0 0 0 ppp0
route -n on 192.168.65.65:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.65.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.64.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.65.72 0.0.0.0 UG 0 0 0 eth1
I don't know what to add in Windows. With this configuration,
192.168.65.72 cannot ping 192.168.64.1, but it is able to when I add
this route: route add default gw 192.168.65.65. Of course, this way
192.168.65.72 cannot ping google.com.
Thanks,
andrej
--
echo ${girl_name} > /etc/dumpdates
Reply to: