Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: network setup help
Date: Sat, 10 Apr 2004 23:50:24 +0100	[thread overview]
Message-ID: <200404102350.24148.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <008301c41f2d$4be932e0$68892090@grouse>

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.



  reply	other threads:[~2004-04-10 22:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-10 18:54 network setup help Jee J.Z.
2004-04-10 22:50 ` Antony Stone [this message]
2004-04-10 23:33   ` Jee J.Z.
2004-04-10 23:59     ` Antony Stone
2004-04-11  2:00       ` Jee J.Z.
2004-04-11  2:52         ` Antony Stone
2004-04-11 16:01           ` Jee J.Z.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200404102350.24148.Antony@Soft-Solutions.co.uk \
    --to=antony@soft-solutions.co.uk \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox