From: "Jee J.Z." <jz105@york.ac.uk>
To: netfilter@lists.netfilter.org
Subject: Re: network setup help
Date: Sun, 11 Apr 2004 00:33:03 +0100 [thread overview]
Message-ID: <00d001c41f54$2b238ac0$68892090@grouse> (raw)
In-Reply-To: 200404102350.24148.Antony@Soft-Solutions.co.uk
Hi Antony,
Thanks for your reply. Please see inline:
> 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?
You are right. PC3/eth0 is a redundancy in this setup. That's why I tried
disabling PC3/eth0. I am just curious that when more than one NIC are
activated, which one will the PC choose to send packets? I guess one of them
should be a default NIC, right? How do I know or set one as default?
> I think your problem is a routing table (almost certainly the one on PC3,
but
> possibly the one on PC2).
Right. I am quite new to setting up routing tables. That should be the
reason... :(
> 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.
Both PC2 and PC3's routing look like:
Destination Gateway Genmask
Flags Metric Ref Iface
192.168.0.0 0.0.0.0 255.255.255.0
U 0 0 eth1
144.32.xxx.0 0.0.0.0 255.255.254.0
U 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0
U 0 0 lo
0.0.0.0 144.32.xxx.yyy 0.0.0.0
UG 0 0 eth0
I haven't added anything to the routing tables, and not quite sure what
rules I should add. I have ever tried adding a default gateway, but it
doesn't seem to work. I know I must be missing something obvious. Could you
show me your thoughts?
> 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?"
Once getting rid of PC3/eth0, four NICs remained are involved:
PC1/eth0-->PC2/eth0-->(filter,nat)-->PC2/eth1-->PC3/eth1. Then any problems?
> For your benefit I have specifically selected the sig on this email :)
Thank you!:)
> 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.
>
>
>
next prev parent reply other threads:[~2004-04-10 23:33 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
2004-04-10 23:33 ` Jee J.Z. [this message]
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='00d001c41f54$2b238ac0$68892090@grouse' \
--to=jz105@york.ac.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