<< | Thread Index | >> ]    [ << | Date Index | >> ]


the two routing tables are :

[blitter@callisto blitter]$ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.0.252   *      255.255.255.255 UH    0      0        0 cipcb0
255.255.255.255 *    255.255.255.255 UH    0      0        0 eth1
192.168.1.45    *       255.255.255.255 UH    0      0        0 eth1
194.7.177.163   *      255.255.255.255 UH    0      0        0 eth0
192.168.1.0     *        255.255.255.0   U     0      0        0 eth1
192.168.0.0     *       255.255.255.0   U     0      0        0 cipcb0
127.0.0.0       *         255.0.0.0       U     0      0        0 lo
default   uu194-7-177-161 0.0.0.0         UG    0      0        0 eth0

[root@crux /root]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.0.10    localhost  255.255.255.255 UGH   0      0        0 lo
192.168.0.15    localhost  255.255.255.255 UGH   0      0        0 lo
192.168.1.252   *       255.255.255.255 UH    0      0        0 cipcb0
192.168.0.131   localhost  255.255.255.255 UGH   0      0        0 lo
192.168.254.0   *         255.255.255.240 U     0      0        0 eth0
192.168.1.0     *       255.255.255.0   U     0      0        0 cipcb0
192.168.0.0     *       255.255.255.0   U     0      0        0 eth1
127.0.0.0       *         255.0.0.0       U     0      0        0 lo
default   192.168.254.1   0.0.0.0         UG    0      0        0 eth0

The roughly sketch the network : callisto is visible on the internet, crux
is behind a router which isn't owned by us and for which I demanded to open
a port for the cipe connection to work in the first place

And on the clients in the network, even if the gateway is set correctly,
pinging does not work to the internal adres on the server (which works
on the opposite server :

On  the 192.168.1.0 network :

c:\>ping 192.168.0.18

Pinging 192.168.0.18 with 32 bytes of data:

Request timed out.
Request timed out.

In fact it is like the cipe interface doesn't know where to find the
internal network ... although kernel forwarding is active, firewalls on the
cipe connection are very loose and firewall on the real interface seem okay
because that pinging works.

Can anyone indicate to me in which direction to continue ? Do I have to
continue to explore the route command ?
In an attempt to correct this problem, I pointed all internal traffic
through the cipe interface but this did seem to crash our internal network
;-)

Best of greetings and thank you in advance !!





<< | Thread Index | >> ]    [ << | Date Index | >> ]