All of lore.kernel.org
 help / color / mirror / Atom feed
From: LIEVEN <LIEVEN@terra.es>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] advanced routing for traffic generator-like setup
Date: Thu, 04 Jul 2002 17:48:31 +0000	[thread overview]
Message-ID: <marc-lartc-102580593504412@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102548174524204@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]

You can enable Zebra routing because both host are in different networks
maybe ripd a possible solution this issue


http://www.guadawireless.net
-.-.LievenX..--.

----- Mensaje Original -----
De: bert hubert <ahu@ds9a.nl>
Fecha: Jueves, Julio 4, 2002 4:49 pm
Asunto: Re: [LARTC] advanced routing for traffic generator-like setup

> On Mon, Jul 01, 2002 at 02:14:22AM +0200, Filip Sneppe wrote:
> 
> > How does one set up advanced routing so that when
> > HostA sends a packet from 1.1.1.1 to 2.2.2.1, it
> > goes via HostB, and vice versa: a packet from
> > 2.2.2.1 to 1.1.1.1 also goes via HostB.
> 
> Only by doing NAT at HostB. Linux is way to smart for this to work 
> otherwise:-)
> 
> Regards,
> 
> bert
> 
> -- 
> http://www.PowerDNS.com          Versatile DNS Software & Services
> http://www.tk                              the dot in .tk
> http://lartc.org           Linux Advanced Routing & Traffic 
> Control HOWTO
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> 


[-- Attachment #2: Card for LIEVEN <LIEVEN@terra.es> --]
[-- Type: text/x-vcard, Size: 51 bytes --]

begin:vcard
n:;LievenX
version:2.1
end:vcard


      parent reply	other threads:[~2002-07-04 17:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-01  0:14 [LARTC] advanced routing for traffic generator-like setup Filip Sneppe
2002-07-04 14:49 ` bert hubert
2002-07-04 17:48 ` LIEVEN [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-102580593504412@msgid-missing \
    --to=lieven@terra.es \
    --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.