Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Ramin Dousti <ramin@cannon.eng.us.uu.net>
To: Jeffrey Laramie <JALaramie@Loudoun-Fairfax.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: TWO ROUTING
Date: Thu, 20 Nov 2003 13:25:53 -0500	[thread overview]
Message-ID: <20031120182553.GC21892@cannon.eng.us.uu.net> (raw)
In-Reply-To: <3FBCE8C8.6070100@Loudoun-Fairfax.com>

On Thu, Nov 20, 2003 at 11:16:08AM -0500, Jeffrey Laramie wrote:

> Interesting. I take it you're referring to the "TEQL" device?

Isn't TEQL for loadbalancing (bundling two or more interfaces terminating
on the same remote device)? No, I was referring to the "ip ro ..."
command which gives you tons of options, including multiple default
routes, routing dicision based on other stuff than only the dst addr...


> Is this 
> installed by a kernel module? From the iptables perspective (trying to 
> stay at least marginally on topic!) if you used this would you use -i 
> eth0 or -i teql0 to identify the interface?

If you bundled eth0 and eth1 to have teql0 then the rules should
reference teql0.

Also, please note that the TEQL stuff is linux specific (interoperability
issues).

Ramin

> Jeff


  reply	other threads:[~2003-11-20 18:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19 15:17 TWO ROUTING José Gomes
2003-11-19 15:24 ` Sylvain BERTRAND
2003-11-20 13:28 ` Jeffrey Laramie
2003-11-20 13:40   ` Antony Stone
2003-11-20 14:43     ` Jeffrey Laramie
2003-11-20 14:59       ` Antony Stone
2003-11-20 16:42       ` Ramin Dousti
2003-11-20 16:16         ` Jeffrey Laramie
2003-11-20 18:25           ` Ramin Dousti [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-20 15:27 Miguel Laborde
2003-11-20 21:44 George Vieira
2003-11-20 22:34 ` Antony Stone
2003-11-19 23:58   ` Marco Shaw

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=20031120182553.GC21892@cannon.eng.us.uu.net \
    --to=ramin@cannon.eng.us.uu.net \
    --cc=JALaramie@Loudoun-Fairfax.com \
    --cc=netfilter@lists.netfilter.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