All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martijn Lievaart <m@rtij.nl>
To: Amin Azez <azez@ufomechanic.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Strange MASQUERADING behaviour, bug or feature?
Date: Wed, 19 Apr 2006 18:28:03 +0200	[thread overview]
Message-ID: <44466513.8080000@rtij.nl> (raw)
In-Reply-To: <444610DD.9000807@ufomechanic.net>

Amin Azez wrote:

> Martijn Lievaart wrote:
>
>> Hey, that is the wrong source address! Now when I kill the null0 
>> interface, suddenly the source address changes to the correct 
>> (169.254.1.1) address. Also when I stop the ping and restart it, the 
>> source address is correct.
>
>
> Thats how NAT works.
>
> The address mappings are setup when the conntrack is created.
>
> You observed that this is less obviously-right for generally stateless 
> streams like ping, but it is certainly consistent and makes sense, and 
> is neccessary for tcp or udp connections, or they would break 
> everytime other routes went up or down.


For SNAT, I can understand this. For MASQUERADE, this is probably also 
the correct behaviour. However, why is this "ping stream" seen as one 
contrack?

But other than that, yes I see now that I cannot use this form  of dial 
on demand with MASQUERADING. Too bad.

Thanks,
M4

  reply	other threads:[~2006-04-19 16:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-17 21:46 Strange MASQUERADING behaviour, bug or feature? Martijn Lievaart
2006-04-19 10:28 ` Amin Azez
2006-04-19 16:28   ` Martijn Lievaart [this message]
2006-04-20  8:00     ` Yasuyuki KOZAKAI
2006-04-20  8:11     ` Amin Azez
2006-04-20 10:40       ` Martijn Lievaart
     [not found]         ` <44476A21.7070609@ufomechanic.net>
2006-04-20 11:16           ` Martijn Lievaart

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=44466513.8080000@rtij.nl \
    --to=m@rtij.nl \
    --cc=azez@ufomechanic.net \
    --cc=netfilter-devel@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 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.