All of lore.kernel.org
 help / color / mirror / Atom feed
From: Whit Blauvelt <whit@transpect.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Jan Engelhardt <jengelh@computergmbh.de>, netfilter@vger.kernel.org
Subject: Re: Why does ipv6 enabled interfere with ipv4 SNAT?
Date: Thu, 27 Mar 2008 10:15:02 -0400	[thread overview]
Message-ID: <20080327141502.GB3288@transpect.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0803261036220.3620@blackhole.kfki.hu>

On Wed, Mar 26, 2008 at 10:45:29AM +0100, Jozsef Kadlecsik wrote:

> But which netfilter modules are loaded in? Again, there can be some 
> auto-loading problem which we cannot figure out without the list of the 
> modules. And as Patrick suggested: do you see the connections in 
> /proc/net/nf_conntrack? Or you have got /proc/net/ip_conntrack instead?

I've just posted the modules list. What should I be looking for between
/proc/net/nf_conntrack vs /proc/net/ip_conntrack? Anything that matches the
internal or external IP? What should be there so I can check for anomoly,
since I don't want to just put raw data to the list.

Thanks,
Whit

  reply	other threads:[~2008-03-27 14:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-25  1:28 Why does ipv6 enabled interfere with ipv4 SNAT? Whit Blauvelt
2008-03-25  1:58 ` Jan Engelhardt
2008-03-25  2:44   ` Whit Blauvelt
2008-03-25  2:57     ` Jan Engelhardt
2008-03-25  3:57       ` Whit Blauvelt
2008-03-25 11:03     ` Jozsef Kadlecsik
2008-03-25 14:25       ` Whit Blauvelt
2008-03-25 15:53         ` Patrick McHardy
2008-03-27 14:10           ` Whit Blauvelt
2008-04-02 10:26             ` Patrick McHardy
2008-03-26  9:45         ` Jozsef Kadlecsik
2008-03-27 14:15           ` Whit Blauvelt [this message]
2008-03-26 11:03       ` Pascal Hambourg
2008-03-26 11:12         ` Jozsef Kadlecsik

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=20080327141502.GB3288@transpect.com \
    --to=whit@transpect.com \
    --cc=jengelh@computergmbh.de \
    --cc=kadlec@blackhole.kfki.hu \
    --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.