From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] A basic setup question
Date: Sun, 20 Jan 2002 13:06:59 +0000 [thread overview]
Message-ID: <marc-lartc-101153211119001@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101148367932480@msgid-missing>
Did you enaled ip-forwarding on machine C ?
echo "1" > /proc/sys/net/ipv4/ip_forward
Stef
On Saturday 19 January 2002 23:49, Ali badilli wrote:
> Hi,
>
> I have just started to build a small linux network. I
> have the following question. If anybody helps I will
> be really appreciated.
>
> I have installed linux 7.2 in machine A, B, C and
> connected them as follows.
>
> A-----------C----------B
> eth0 eth0 eth1 eth0
>
> As it is shown in figure C has two ethernet interfaces
> eth0 connected to A and eth1 connected to B.
>
> I have assigned the addresses as follows:
>
> A: 192.20.1.3 (eth0) mask:255.255.255.0 default
> gw:192.20.1.1
>
> B: 192.20.2.3 (eth0) mask:255.255.255.0 default
> gw:192.20.2.1
>
> C: 192.20.1.1 (eth0) mask:255.255.255.0
> default gw:192.20.2.1
>
> and 192.20.2.1 (eth1) mask:255.255.255.0
> default gw:192.20.1.1
>
> C acts as gateway between between A and B.
>
>
> I configure routing table as follows:
>
>
> A: destination network network mask gateway
> 0.0.0.0 0.0.0.0 92.20.1.1
>
> 192.20.1.0 255.255.255.0 192.20.1.3
>
>
> B:destination network network mask gateway
> 0.0.0.0 0.0.0.0 92.20.2.1
>
> 192.20.2.0 255.255.255.0 192.20.2.3
>
> C:destination network network mask gateway
> 192.20.2.0 255.255.255.0 192.20.2.1
> (eth0)
> 192.20.1.0 255.255.255.0 192.20.1.1
> (eth1)
>
> I can ping from A to 192.20.2.1 but I cannot ping to
> 192.20.2.3(which is B)
>
> similarly,
>
> I can ping from B to 192.20.1.1 but cannot ping to
> 192.20.1.3 (which is A).
>
> In other word, Both A and B can ping the interfaces of
> C which belong to different subnets, but A and B
> cannot ping each other.
>
> Am I missing some basic configuration things?, Should
> I install any other patch or etc?,
>
> I will be really appreciated If some body give me
> clear explanation. Sorry for asking a simple question.
>
> Haci
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Send FREE video emails in Yahoo! Mail!
> http://promo.yahoo.com/videomail/
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
--
stef.coene@docum.org
More QOS info : http://www.docum.org/
Title : "Using Linux as bandwidth manager"
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
prev parent reply other threads:[~2002-01-20 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-19 22:49 [LARTC] A basic setup question Ali badilli
2002-01-20 2:17 ` Greg Scott
2002-01-20 13:06 ` Stef Coene [this message]
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=marc-lartc-101153211119001@msgid-missing \
--to=stef.coene@docum.org \
--cc=lartc@vger.kernel.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