All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julian Anastasov <ja@ssi.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Src IP for outgoing packet with multiple defaults routes
Date: Thu, 07 Mar 2002 16:27:24 +0000	[thread overview]
Message-ID: <marc-lartc-101551847229675@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101551599620984@msgid-missing>


	Hello,

On Thu, 7 Mar 2002, =?ISO-8859-2?Q?Andrés Griñó Brandt?= wrote:

> Hi:
>
> Abstract: Linux connected to two different ISP. Outgoing packets seems to peek randomly it's source IP address, without regards to the router choosen.

	Not possible with plain kernel, check this URL:

http://www.linuxvirtualserver.org/~julian/#routes

	after patching nexthops with same outdevs are supported

>            nexthop via 200.27.214.225 dev eth0 weight 1
>            nexthop via 200.72.44.225  dev eth0 weight 3

> This is wrong. Packets with source IP 200.72.44.226 must not reach router 200.27.214.226. AFIK, an outgoing packet must have a source address in the same subnet that the router being used.

	To be honest, NAT in current kernels does not work correctly
with multipath routes, even if you are using different outdevs in all
nexthops. Read the docs mentioned above.

> Ideas?
>
> Andrés Griñó Brandt
> Santiago, Chile

Regards

--
Julian Anastasov <ja@ssi.bg>

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2002-03-07 16:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-07  7:37 [LARTC] Src IP for outgoing packet with multiple defaults routes Andrés Grińó Brandt
2002-03-07 16:27 ` Julian Anastasov [this message]
2002-03-07 19:42 ` bert hubert

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-101551847229675@msgid-missing \
    --to=ja@ssi.bg \
    --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.