From: "/dev/rob0" <rob0@gmx.co.uk>
To: netfilter@vger.kernel.org
Subject: Re: ULOG The kernel doesn't support a certain ebtables extension, consider recompiling your kernel or insmod the extension.
Date: Mon, 31 Aug 2009 15:34:19 -0500 [thread overview]
Message-ID: <200908311534.19700.rob0@gmx.co.uk> (raw)
In-Reply-To: <4A9C2F4C.9050405@branndal.se>
On Monday 31 August 2009 15:15:08 Thomas Berg wrote:
> /sbin/ebtables --modprobe /sbin/modprobe -A FORWARD --in-interface
> eth1.4 --protocol IPv4 --ip-protocol udp --ip-destination-port 67
> -j DROP --ulog
> ULOG The kernel doesn't support a certain ebtables extension,
> consider recompiling your kernel or insmod the extension.
>
> lsmod
> ebt_ip 1752 29
> ebt_log 3268 32
> ebtable_broute 1740 0
> ebtable_nat 2000 0
> ebtable_filter 2028 1
> ebtables 14108 3 ebtable_broute,ebtable_nat,ebtable_filter
> ipt_ULOG 6684 1
> x_tables 14108 4 ebt_ip,ebt_log,ebtables,ipt_ULOG
> bridge 39968 1 ebtable_broute
> 8021q 17932 0
> garp 6996 1 8021q
> stp 2112 2 bridge,garp
> I can se the modules below
> /lib/ebtables
Those are ebtables(8) user-space modules, not kernel.
> Isnt ebtables supposed to auto load its needed modules?
I have this:
/lib/modules/$(uname -r)/kernel/net/bridge/netfilter/ebt_ulog.ko
Do you?
If this is your custom kernel, you overlooked it. If it is a Debian
kernel, file a Debian bug.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
next prev parent reply other threads:[~2009-08-31 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 20:15 ULOG The kernel doesn't support a certain ebtables extension, consider recompiling your kernel or insmod the extension Thomas Berg
2009-08-31 20:34 ` /dev/rob0 [this message]
2009-09-01 7:47 ` Thomas Berg
2009-09-01 11:43 ` Patrick McHardy
2009-09-01 12:17 ` Thomas Berg
2009-09-01 12:35 ` Patrick McHardy
2009-09-01 13:20 ` Thomas Berg
2009-09-01 13:21 ` Patrick McHardy
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=200908311534.19700.rob0@gmx.co.uk \
--to=rob0@gmx.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox