From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@lists.netfilter.org
Subject: Re: What happened to ipt_physdev.c ?
Date: Sat, 25 Nov 2006 13:56:36 +0100 [thread overview]
Message-ID: <45683D84.6030202@plouf.fr.eu.org> (raw)
In-Reply-To: <1164206481.456461916ec06@mail.third-rock.net>
Hello,
Paul Reilly a écrit :
> In recent kernels, 2.6.16.x there is no longer any
>
> net/ipv4/netfilter/ipt_physdev.c
Yes, since 2.6.16 it was replaced by net/netfilter/xt_physdev.c.
> and no option in kernel config to enable CONFIG_NETFILTER_XT_MATCH_PHYSDEV
Yes there is. I just checked in vanilla 2.6.16 and 2.6.16.20.
> So I have no physdev in /proc/net/ip_tables_matches
> and my rules which include a -m physdev fail with:
>
> iptables: No chain/target/match by that name
>
> Has PHYSDEV been moved somewhere else?
Since 2.6.16 the corresponding module is named xt_physdev.ko and depends
on x_tables and bridge.
> How do I enable it?
Symbol: NETFILTER_XT_MATCH_PHYSDEV [=m]
Prompt: "physdev" match support
Defined at net/netfilter/Kconfig:282
Depends on: NET && NETFILTER && NETFILTER_XTABLES && BRIDGE_NETFILTER
Location:
-> Networking
-> Networking support (NET [=y])
-> Networking options
-> Network packet filtering (replaces ipchains) (NETFILTER [=y])
-> Core Netfilter Configuration
-> Netfilter Xtables support (required for ip_tables)
(NETFILTER_XTABLES [=m])
CONFIG_NETFILTER_XT_MATCH_PHYSDEV is located in the "Core Netfilter
Configuration" submenu and depends on CONFIG_NETFILTER_XTABLES
(Netfilter Xtables support) and CONFIG_BRIDGE_NETFILTER (Bridged IP/ARP
packets filtering) which depends on CONFIG_BRIDGE (802.1d Ethernet
Bridging).
next prev parent reply other threads:[~2006-11-25 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 14:41 What happened to ipt_physdev.c ? Paul Reilly
2006-11-22 17:04 ` Andy Furniss
2006-11-22 17:24 ` Robert P. J. Day
2006-11-25 12:56 ` Pascal Hambourg [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-22 23:55 Paul Reilly
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=45683D84.6030202@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--cc=netfilter@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.