Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Thomas Berg <thomas.berg@branndal.se>
To: Patrick McHardy <kaber@trash.net>
Cc: /dev/rob0 <rob0@gmx.co.uk>, 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: Tue, 01 Sep 2009 14:17:35 +0200	[thread overview]
Message-ID: <4A9D10DF.1050307@branndal.se> (raw)
In-Reply-To: <4A9D08FF.7070705@trash.net>

Hi

trying this

rmmod ipt_ulog

modprobe ebt_ulog

ebtables 14108 3 ebtable_broute,ebtable_nat,ebtable_filter
x_tables 14108 5 ebt_ulog,ebt_nflog,ebt_ip,ebt_log,ebtables


module is then loaded, great but still the same error when trying to add 
a ebtables rule with ulog.

br0:~# /sbin/ebtables --modprobe /sbin/modprobe -A FORWARD 
--in-interface eth1.4 --protocol IPv4 --ip-protocol udp 
--ip-destination-port 67 -j DROP --ulog
The kernel doesn't support a certain ebtables extension, consider 
recompiling your kernel or insmod the extension.

unloading ebt_ulog and then trying to add a rule with ulog ends up with 
ebt_ulog loaded but still getting the same error message

The kernel doesn't support a certain ebtables extension, consider 
recompiling your kernel or insmod the extension.

So ebtables is loading ebt_ulog if ipt_ulog is unloaded but still there 
is this error message that the kernel need to be recompiled or try to 
load module.

I´ll have to check out nfnetlink_log and se if I can use that instead, 
is it forwaring the whole packet to userspace?

Best regards,
Thomas

Patrick McHardy skrev:
> Thomas Berg wrote:
>   
>>>> 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
>>>>     
>>>>         
>> br0:/lib/modules/2.6.26-1-686/kernel/net/bridge/netfilter# modprobe
>> ebt_ulog
>> FATAL: Error inserting ebt_ulog
>> (/lib/modules/2.6.30-1-686/kernel/net/bridge/netfilter/ebt_ulog.ko):
>> Cannot allocate memory
>>     
>
> ebt_ulog and ipt_ULOG can't be used simultaneously since they both use
> the same netlink unit. I don't think we can fix it at this point since
> both are obsolete and this would break existing setups. You can use
> nfnetlink_log and xt_NFLOG/ebt_NFLOG as a replacement.
>   


  reply	other threads:[~2009-09-01 12:17 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
2009-09-01  7:47   ` Thomas Berg
2009-09-01 11:43     ` Patrick McHardy
2009-09-01 12:17       ` Thomas Berg [this message]
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=4A9D10DF.1050307@branndal.se \
    --to=thomas.berg@branndal.se \
    --cc=kaber@trash.net \
    --cc=netfilter@vger.kernel.org \
    --cc=rob0@gmx.co.uk \
    /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