All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Segree, Gareth" <Gareth.Segree@gleanerjm.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Serious Routing problem
Date: Sat, 06 Jul 2002 16:57:54 +0000	[thread overview]
Message-ID: <marc-lartc-102597506813991@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102591830520569@msgid-missing>

             [128.187.1.1] gw none          [128.187.2.1] gw none
      __________________[eth1--  Server  -- eth2]__________________
     /                                                             \
24-port Hub 1                                                 24 port Hub 2
+-----------+                                                 +-----------+
+-----------+                                                 +-----------+
    /\______________[eth1-- Linux Firewall --eth2]__________________/\
   /              [128.187.3.1]        [128.187.4.1]                  \
[clients1]                                                        [clients2]
128.187.3.0/24 gw eth1                              128.187.4.0/24 gw eth2


I want clients1 to be able to reach eth2 on server [128.187.2.1] if eth1 on
Server goes down and visa versa.

Does this explain better.

-----Original Message-----
From: Julian Anastasov [mailto:ja@ssi.bg]
Sent: Saturday, July 06, 2002 2:05 PM
To: Segree, Gareth
Cc: 'lartc@mailman.ds9a.nl'
Subject: RE: [LARTC] Serious Routing problem



	Hello,

On Sat, 6 Jul 2002, Segree, Gareth wrote:

> > Well, do you have picture of this setup: wires, hosts, hubs, IPs,
> > Subnets. It will help for selecting the right solution. Is the problem
> > that rp_filter drops the packets?
> No I can ping both hosts and server from the firewall .
>
> I thought that if you created host routes on the firewall and enable
> ip_forwarding thats all that would be needed.

	Not so easy if you connect one Linux box to another host by using
2 or more devices....

	ping can work because by default selects as src IP the preferred 
source address to the targat host. But from the information provided I 
assume you have a problem with talks between different subnets. No? At
least, I don't have a clear picture of your setup which is essential
step before continuing further.

Regards

--
Julian Anastasov <ja@ssi.bg>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2002-07-06 16:57 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
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 [this message]
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-102597506813991@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.