Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Rio Martin <rio@martin.mu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multihomed Masquerading, routing and iptables
Date: Tue, 06 Jan 2004 01:49:38 +0000	[thread overview]
Message-ID: <200401060849.38380.rio@martin.mu> (raw)
In-Reply-To: <200312311649.36278.lartc@bobich.net>

On Monday 05 January 2004 19:06, Gordan Bobic wrote:
> On Monday 05 Jan 2004 11:54, Gordan Bobic wrote:
> > On Monday 05 Jan 2004 11:28, Artūras Šlajus wrote:
> > > Gordan Bobic wrote:
> > > > Hmm. Just replace -j MASQUERADE with -j SNAT? Will that not break
> > > > other things?
> > > -j SNAT your_ip
> > Or rather -j SNAT --to-source your_ip. I get it. I'll check if that works
> > better than masquerading.
> Just tried it - no difference. Packets still come out with source IP
> address not matching the interface. :-(

Try it switch manually, first you set up without iproute. Remove all the 
tables you have created and flush it. Try with ISP1 first. Do SNAT --to 
ip.of.ISP1
Is it work? Okay, now switch to the ISP2. Do SNAT --to ip.of.ISP2. 
It should be work, otherwise something wrong with the kernel or iptables you 
had on your machine.

Finish this step first, report back to the list.

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

  parent reply	other threads:[~2004-01-06  1:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-31 16:49 [LARTC] Multihomed Masquerading, routing and iptables Gordan Bobic
2004-01-05  2:04 ` Rio Martin
2004-01-05  2:55 ` Rio Martin
2004-01-05 11:17 ` Gordan Bobic
2004-01-05 11:28 ` Artūras Šlajus
2004-01-05 11:54 ` Gordan Bobic
2004-01-05 12:06 ` Gordan Bobic
2004-01-05 20:32 ` andybr
2004-01-05 21:43 ` Gordan Bobic
2004-01-06  1:49 ` Rio Martin [this message]
2004-01-06  9:25 ` Gordan Bobic
2004-01-06 16:57 ` R. Steve McKown

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=200401060849.38380.rio@martin.mu \
    --to=rio@martin.mu \
    --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