From: tc lewis <tcl@bunzy.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Serious Routing problem
Date: Sat, 06 Jul 2002 03:46:11 +0000 [thread overview]
Message-ID: <marc-lartc-102592718624736@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102591830520569@msgid-missing>
er, i didn't really read this whole thing, so this reply is probably
worthless, but...
> I have a server with two interfaces 128.187.2.0/16 and 128.187.1.0/16 that
> was setup by a vendor (I dont think there is any ip routing enabled).
doesn't 128.187.1.0/16 bleed into 128.187.2.0/16? i would think there
would be problems with that right there. y/n?
-tcl.
On Fri, 5 Jul 2002, Segree, Gareth wrote:
> It might seem like I'm asking this question in vain but let me post it for
> the last time.
>
> I have a server with two interfaces 128.187.2.0/16 and 128.187.1.0/16 that
> was setup by a vendor (I dont think there is any ip routing enabled).
>
> I have a hosts on two hubs (server card 1 is on hub 1 128.187.2.1 and server
> card 2 is on hub 2 128.187.1.1)
>
> I have a firewall with two interface cards with the following eth1:
> 128.187.3.1/24 [hub 1] and eth2: 128.187.4.1/24 [hub 2].
>
> I want each side to talk to the other in the event that one of the network
> card goes down.
>
> 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.
>
> 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.
>
> How can I allow hosts on the eth1: 128.187.3.1/24 to ping 128.187.2.1 and
> hosts on eth2: 128.187.4.1/24 to ping 128.187.1.1.
>
> Thanks in Advance.
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-07-06 3:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-06 1:12 [LARTC] Serious Routing problem Segree, Gareth
2002-07-06 3:46 ` tc lewis [this message]
2002-07-06 6:12 ` Julian Anastasov
2002-07-06 15:39 ` Segree, Gareth
2002-07-06 16:04 ` Julian Anastasov
2002-07-06 16:57 ` Segree, Gareth
2002-07-06 17:45 ` Julian Anastasov
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-102592718624736@msgid-missing \
--to=tcl@bunzy.net \
--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.