netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: "Damien Thébault" <damien.thebault@gmail.com>
Cc: linux-net@vger.kernel.org, netfilter-devel@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: conntrack doesn't always work when a bridge is used
Date: Thu, 20 Dec 2007 12:07:19 +0100	[thread overview]
Message-ID: <476A4CE7.4070607@trash.net> (raw)
In-Reply-To: <9a4a382a0712200306m1260e21ahf89cf528c172bd6d@mail.gmail.com>

Damien Thébault wrote:
> Yes, when I'm using ip addresses with the same length, the conntrack
> -E output is similar, and it's working.
> But if I change the router's "wan"-side ip address to be longer or
> shorter than the client's ip address, then it's non-working again.
> 
> I don't think it's something in the configuration : the results are
> present on two different computers, one being a x86 little endian
> debian laptop where I did the bisect, the other being an arm xscale
> big endian board with a custom distro (nothing funny here, just
> kernel, drivers, busybox and  some utilities).
> 
> Well, I'm sorry, I don't want to bother anyone, but those are really
> the results I'm seeing.


Don't worry. I was just wondering because I asked for the output
of the *non-working* case :) Please post that and I'll look into it.
-
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2007-12-20 11:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9a4a382a0712180648i7fc958edt6f0d9db83f574c77@mail.gmail.com>
2007-12-19 17:00 ` conntrack doesn't always work when a bridge is used Damien Thébault
2007-12-19 19:03   ` Patrick McHardy
2007-12-20  8:30     ` Damien Thébault
2007-12-20 10:06       ` Patrick McHardy
2007-12-20 11:06         ` Damien Thébault
2007-12-20 11:07           ` Patrick McHardy [this message]
2007-12-20 11:20             ` Damien Thébault
2007-12-20 11:25               ` Patrick McHardy
2007-12-20 13:21                 ` Damien Thébault
2007-12-20 16:08                   ` Damien Thébault
2007-12-22  7:56                   ` Patrick McHardy
2007-12-26  9:54                     ` Damien Thébault
2007-12-30 17:53                       ` Patrick McHardy
     [not found]                         ` <9a4a382a0801020118n4166e505l5eb84a9f07f620be@mail.gmail.com>
2008-01-11  8:10                           ` Damien Thébault
2008-01-11 12:24                             ` Patrick McHardy
2008-01-11 12:53                               ` Damien Thébault
2008-01-11 12:57                                 ` Patrick McHardy
2008-01-11 13:25                                   ` Patrick McHardy
2008-01-11 15:16                                     ` Damien Thébault
2008-01-11 17:33                                       ` Patrick McHardy
2007-12-28 14:39   ` Damien Thébault

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=476A4CE7.4070607@trash.net \
    --to=kaber@trash.net \
    --cc=damien.thebault@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-net@vger.kernel.org \
    --cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).