All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Shambarger <scott-netfilter@shambarger.net>
To: netfilter@vger.kernel.org
Subject: Re: Returning nat packets vanishing after mangle:PREROUTING and conntrack processing
Date: Sun, 20 Dec 2009 12:43:29 -0800	[thread overview]
Message-ID: <11be91d1da3dc8853975cdcda341cd26@localhost> (raw)
In-Reply-To: <4B2D1DF7.1060105@plouf.fr.eu.org>


On Sat, 19 Dec 2009 19:39:51 +0100, Pascal Hambourg

<pascal.mail@plouf.fr.eu.org> wrote:

> (Searching in kernel changelogs...)



Guess I need to read those more closely to catch subtle but important

changes in kernel behavior :)



> changing rp_filter type from boolean to integer and assigning the value

> 2 to the new loose mode (see Documentation/networking/ip-sysctl.txt for

> details).

[...]

> Notes :

> 1) "Loose" reverse path filtering may be a bit better than no reverse

> path filtering and should work with your setup.



Tried "loose" and it worked great on my multi-homed setup, thanks for the

tip.



> 2) Reverse path filtering in kernel 2.6.32 uses the mark as in policy

> routing, so strict reverse path filtering may work better in multihomed

> setups like yours.



Looking forward to it, I'll give it a try once I upgrade to .32



Cheers,

Scott



      reply	other threads:[~2009-12-20 20:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18 18:23 Returning nat packets vanishing after mangle:PREROUTING and conntrack processing Scott Shambarger
2009-12-19 13:12 ` Pascal Hambourg
2009-12-19 14:37   ` Scott Shambarger
2009-12-19 18:39     ` Pascal Hambourg
2009-12-20 20:43       ` Scott Shambarger [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=11be91d1da3dc8853975cdcda341cd26@localhost \
    --to=scott-netfilter@shambarger.net \
    --cc=netfilter@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.