From: Bart De Schuymer <bdschuym@pandora.be>
To: Tim Verhoeven <tim.verhoeven.be@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Compiling ebtables statically or dynamically results in different behaviour
Date: Mon, 20 Apr 2009 19:43:03 +0200 [thread overview]
Message-ID: <49ECB427.7030303@pandora.be> (raw)
In-Reply-To: <2a7fce340904200227j42e07fd3gbf507539809a4e08@mail.gmail.com>
Hi,
I'm currently lacking the time, but if you have some programming
experience, a dump of the data sent to the kernel for the static and
dynamic version of the code would be great. See ebt_deliver_table() in
communication.c: the data pointed to by repl and repl->entries
specifically. Please use a simple table: start with an empty one before
issuing the command.
cheers,
Bart
Tim Verhoeven schreef:
> On Wed, Apr 8, 2009 at 11:57 AM, Tim Verhoeven
> <tim.verhoeven.be@gmail.com> wrote:
>
>> On Wed, Apr 8, 2009 at 11:49 AM, bdschuym@pandora.be
>> <bdschuym@telenet.be> wrote:
>>
>>> What is your exact command and what type of processor are you using?
>>>
>>>
>> The command run is "ebtables -N 1000"
>>
>> This is /proc/cpuinfo :
>> processor : 0
>> vendor_id : GenuineIntel
>> cpu family : 6
>> model : 23
>> model name : Intel(R) Xeon(R) CPU E5430 @ 2.66GHz
>>
> ...snip...
>
> Hi again,
>
> Is there any update about this issue ? Can I do anything to help debug
> the problem ? I have test machines available.
>
> Thanks,
> Tim
>
>
next prev parent reply other threads:[~2009-04-20 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 9:49 Compiling ebtables statically or dynamically results in different behaviour bdschuym@pandora.be
2009-04-08 9:57 ` Tim Verhoeven
2009-04-20 9:27 ` Tim Verhoeven
2009-04-20 17:43 ` Bart De Schuymer [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-07 13:53 Tim Verhoeven
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=49ECB427.7030303@pandora.be \
--to=bdschuym@pandora.be \
--cc=netfilter-devel@vger.kernel.org \
--cc=tim.verhoeven.be@gmail.com \
/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).