Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Peter Rabbitson <rabbit+list@rabbit.us>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] One machine, two net feeds, outbound route selection
Date: Thu, 25 Oct 2007 17:03:48 +0000	[thread overview]
Message-ID: <4720CC74.2090102@rabbit.us> (raw)
In-Reply-To: <59f980d60710241725p5ca9cca2ueb5edc12675f62e3@mail.gmail.com>

Ben Scott wrote:
>   Now, for the sake of knowledge, let us say that a piece of needed
> software didn't have an option to bind to a specific interface.  Would
> it be possible to control the outgoing route/interface anyway, by
> using iptables or some other mechanism external to the software?  For
> example, what if Sendmail didn't have a ClientPortOptions directive
> (heh, I know, use Postfix, but work with me here)?
> 

Unfortunately not easy without doing local NAT (from the local interface 
to another local interface). The problem lies in how the kernel sends 
packets without a specified source. I wrote an explanation some time 
ago: http://mailman.ds9a.nl/pipermail/lartc/2007q2/020941.html
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2007-10-25 17:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25  0:25 [LARTC] One machine, two net feeds, outbound route selection Ben Scott
2007-10-25  9:09 ` Peter Rabbitson
2007-10-25 15:39 ` Ben Scott
2007-10-25 17:03 ` Peter Rabbitson [this message]
2007-10-25 18:00 ` Ben Scott
2007-10-25 21:16 ` Alex Samad
2007-10-25 21:25 ` Peter Rabbitson

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=4720CC74.2090102@rabbit.us \
    --to=rabbit+list@rabbit.us \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox