public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Kevin Buhr <buhr@telus.net>
Cc: Maciej Soltysiak <solt@dns.toxicfilms.tv>,
	netfilter-devel@lists.samba.org, linux-kernel@vger.kernel.org
Subject: Re: BUG somewhere in NAT mechanism [was: my linux box does not learn from redirects]
Date: Sun, 13 Apr 2003 15:41:15 +0200	[thread overview]
Message-ID: <3E9968FB.8050409@trash.net> (raw)
In-Reply-To: <3E99574B.5060306@trash.net>



Patrick McHardy wrote:

>> Maciej Soltysiak <solt@dns.toxicfilms.tv> writes:
>>  
>> It looks like the relevant bit of code is:
>>
>> ip_nat_core.c:881 (in 2.4.20)
>>        /* Redirects on non-null nats must be dropped, else they'll
>>           start talking to each other without our translation, and be
>>           confused... --RR */
>>        if (hdr->type == ICMP_REDIRECT) {
>>                /* Don't care about races here. */
>>                if (info->initialized
>>                    != ((1 << IP_NAT_MANIP_SRC) | (1 << 
>> IP_NAT_MANIP_DST))
>>
>
> Apart from what you're saying, it should be:
>
>                            if (info->initialized
>                                 & ((1 << IP_NAT_MANIP_SRC) | (1 << 
> IP_NAT_MANIP_DST))
>
> otherwise (maybe that's what Maciej is seeing) redirects for 
> connections without natbindings
> will be dropped too. 


Sorry this was wrong, it seems because of null_bindings every connection 
has at least one
binding per direction.

Bye
Patrick



      reply	other threads:[~2003-04-13 13:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-12 13:40 BUG somewhere in NAT mechanism [was: my linux box does not learn from redirects] Maciej Soltysiak
2003-04-13  5:00 ` Kevin Buhr
2003-04-13 12:25   ` Patrick McHardy
2003-04-13 13:41     ` Patrick McHardy [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=3E9968FB.8050409@trash.net \
    --to=kaber@trash.net \
    --cc=buhr@telus.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfilter-devel@lists.samba.org \
    --cc=solt@dns.toxicfilms.tv \
    /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