On Saturday 10 April 2004 7:54 pm, Jee J.Z. wrote:
> Dear all,
>
> I am trying to setup three PCs and do some simple filter+nat jobs. The
> situation is specified below:
>
> 1.PC1 has one NIC with a global IP connected to a Switch;
> 2.PC2 has two NICs, eth0 with a global IP connected to the Switch and eth1
> with an internal IP (192.168.0.1/24) directly connected to PC3's eth1;
> 3.PC3 has two NICs, eth0 with a global IP connected to the Switch and eth1
> with an internal IP (192.168.0.2/24) directly connected to PC2's eth1.
!? Why !?
(Either, why are PC2 and PC3 connected, or, why are both PC2 and PC3 connected
to the switch?)
> I am trying to send packets from PC1 to PC3, via PC1/eth0(global
> IP)-->PC2/eth0(global IP)-->PC2/eth1(192.168.0.1)-->PC3/eth1(192.168.0.2).
> Actually, PC3/eth0 is not in used in the case.
So, what's PC3/eth0 for?
I think your problem is a routing table (almost certainly the one on PC3, but
possibly the one on PC2).
Look at the routing table of each machine the packets are going through, and
then the replies trying to get back again, and see if (a) there is a path,
and (b) it makes sense.
I think once you've done this you will find the source of your problem, but I
really do recommend you think about your network setup, and the path you are
trying to get packets to take, and ask yourself "why do it like this?"
For your benefit I have specifically selected the sig on this email :)
Regards,
Antony.
--
90% of networking problems are routing problems.
9 of the remaining 10% are routing problems in the other direction.
The remaining 1% might be something else, but check the routing anyway.
Please reply to the list;
please don't CC me.
