From: Florian Westphal <fw@strlen.de>
To: Sharat Masetty <sharat04@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: ebtables issue in compat mode
Date: Thu, 1 May 2014 12:02:29 +0200 [thread overview]
Message-ID: <20140501100229.GS31953@breakpoint.cc> (raw)
In-Reply-To: <CAJzFV37HK7J2W5uz8-zFZ-n80yYKvu8KmxWu8Dx2rzbzzLeZDw@mail.gmail.com>
Sharat Masetty <sharat04@gmail.com> wrote:
> I am seeing a problem when running ebtables in 32bit userspace and 64
> bit kernel space mode.
>
> The command I am trying to run is
> ebtables -t broute -A BROUTING -p IPv4 -j DROP
>
> Here is the log message I am seeing in userspace
>
[..]
> I noticed that setsockopt() is failing . The message is also printed
> in kernel – Standard target size too big . This occurs because there
> is a mismatch in the size of the structures ebt_standard_target which
> is 48 bytes in kernel and 40 bytes in userspace.
>
> Can someone help us fix this issue?
Please provide more information.
Works fine for me on x86_64 with 32 bit binary:
# ~/bin32/ebtables -t broute -A BROUTING -p IPv4 -j DROP
# echo $?
0
ebtables -L shows
Bridge chain: BROUTING, entries: 1, policy: ACCEPT
-p IPv4 -j DROP
as expected. Linux 3.13.11 x86_64.
Are you using an old kernel without ebt compat support?
--
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
next prev parent reply other threads:[~2014-05-01 10:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 5:18 ebtables issue in compat mode Sharat Masetty
2014-05-01 10:02 ` Florian Westphal [this message]
2014-05-01 16:09 ` Sharat Masetty
2014-05-01 21:50 ` Sharat Masetty
2014-05-02 22:31 ` Florian Westphal
2014-05-02 22:35 ` Jan Engelhardt
2014-05-02 22:37 ` Florian Westphal
2014-05-03 1:06 ` Sharat Masetty
2014-05-04 21:05 ` Bart De Schuymer
2014-05-03 1:23 ` Jan Engelhardt
2014-05-04 21:04 ` Bart De Schuymer
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=20140501100229.GS31953@breakpoint.cc \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=sharat04@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).