From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Source Routing on a multihomed host
Date: Fri, 01 Mar 2002 10:07:46 +0000 [thread overview]
Message-ID: <marc-lartc-101497740802988@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101473414514335@msgid-missing>
On Thu, Feb 28, 2002 at 10:32:19AM -0500, STEVE CASTRO wrote:
>
> > > Will the Simple Source routing example shown in "LARTC HOWTO" work
> > > for a multihomed host (not a router) application that simply "binds"
> > > to the address associated with the interface or does the source
> > > routing decision only effect packets coming in over the interface and
> not
> > > from a local application?
> >
> > It effects all packets.
> >
> > > Basically, I want an application to choose which interface to use (i.e.
> > > override the default route) by doing something similar to the old days
> > > (Kernel 2.0.31 I think) when there was a socket option called
> > > SO_BINDTODEVICE.
> >
> > Can't you just let the application bind to the ip address of the
> interface?
>
> yes...this is exactly what I want to do. BUT....I am just beginning to learn
> about the
> "advanced routing" capabilities AND it is not clear to me how (or even
> if its possible) to set it up a multihomed linux host (not a router) to
> ensure that the
> outgoing interface is chosen based upon the bound to address and NOT the
> destination address.
>
> Prior to "advanced routing" the outgoing interface
> on a multi-homed host (not router) was chosen strictly on the destination
> address.
> The binding simply fixed the source address of the packet....regardless of
> the
> interface actually used. (One could thus have packets sent out eth0 whose
> source
> address were actually eth1) There was no source routing capability on a
> linux host, only
> linux routers. The SO_BINDTODEVICE was an early socket option to get around
> this.
I suggest you read 'Unix Network Programming 1&2' by Stevens, or peruse the
source of any program with a 'bind to address' option.
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/
prev parent reply other threads:[~2002-03-01 10:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 14:36 [LARTC] Source Routing on a multihomed host STEVE CASTRO
2002-02-28 9:01 ` bert hubert
2002-02-28 15:32 ` STEVE CASTRO
2002-03-01 10:07 ` bert hubert [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-101497740802988@msgid-missing \
--to=ahu@ds9a.nl \
--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.