From: "Segree, Gareth" <Gareth.Segree@gleanerjm.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Routing Question?
Date: Mon, 24 Jun 2002 22:18:07 +0000 [thread overview]
Message-ID: <marc-lartc-102495741809976@msgid-missing> (raw)
I have a network 128.187.2.0/24 and 128.187.1.0/24 that was setup by a
vendor.
I'm not too sure about the subnet mask above might be 16.
I have a host on 128.187.2.1 and 128.187.1.1 that I need a network to talk
to.
I have a firewall setup like the following.
eth1: 128.187.3.1/24 and eth2: 128.187.4.1/24 - with clients on each side of
the lan with default gateway being the interface that it is connected to.
The 128.187.2.1 is on the hub that eth2 is connected to and 128.187.1.1 is
on the hub that eth1 is connected to.
I have done the following:
echo 1 > /proc/sys/net/ipv4/ip_forward
ip route replace 128.187.1.1 dev eth1
ip route replace 128.187.2.1 dev eth2
From the firewall I can ping 128.187.1.1 & 128.187.2.1.
clients from the 128.187.3.0 side can't ping 128.187.2.1 and clients from
the 128.187.4.0 side can't ping 128.187.1.1
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-06-24 22:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-102495741809976@msgid-missing \
--to=gareth.segree@gleanerjm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.