Skip to contentSkip to conversation

ip6tables filter breakage.

DISCUSSION Dave Jones 4 participants 4 messages Aug 6, 2014 – Aug 7, 2014

Subsystems (3)
lore
Share & tools
lore

Dave Jones

author
#0 lore raw

After updating to Linus' current tree with todays net/ merge, I noticed that ip6tables doesn't work any more..

# ip6tables -F
ip6tables v1.4.19.1: can't initialize ip6tables table `filter': No
chain/target/match by that name
Perhaps ip6tables or your kernel needs to be upgraded

My config has CONFIG_IP6_NF_FILTER=m
I also note that ip6table_filter.ko doesn't get auto-loaded now. But even after modprobing it, I get the same message.

Is there some additional option I now need to enable ?

I was a little surprised by how CONFIG_NF_TABLES is mandatory for iptables to keep working, even if you don't have nft userspace. (The only relevant thing in the Kconfig was related to x_tables,
which I wasn't using).

Perhaps either some select's, or additional help text ?

Dave

maintainer
#1 lore raw

From: Dave Jones <[email protected]>
Date: Wed, 6 Aug 2014 15:52:22 -0400

CC:'ing netfilter-devel, Dave please do this in the future for netfilter reports, thanks.

Quoted 28 lines

After updating to Linus' current tree with todays net/ merge, I noticed that ip6tables doesn't work any more..

# ip6tables -F
ip6tables v1.4.19.1: can't initialize ip6tables table `filter': No
chain/target/match by that name
Perhaps ip6tables or your kernel needs to be upgraded

My config has CONFIG_IP6_NF_FILTER=m
I also note that ip6table_filter.ko doesn't get auto-loaded now. But even after modprobing it, I get the same message.

Is there some additional option I now need to enable ?

I was a little surprised by how CONFIG_NF_TABLES is mandatory for iptables to keep working, even if you don't have nft userspace. (The only relevant thing in the Kconfig was related to x_tables,
which I wasn't using).

Perhaps either some select's, or additional help text ?

Dave

--
To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#2 lore raw
Quoted 27 lines · David Miller

From: Dave Jones <[email protected]>
Date: Wed, 6 Aug 2014 15:52:22 -0400

CC:'ing netfilter-devel, Dave please do this in the future for netfilter reports, thanks.

Quoted 21 lines

After updating to Linus' current tree with todays net/ merge, I noticed that ip6tables doesn't work any more..

# ip6tables -F
ip6tables v1.4.19.1: can't initialize ip6tables table `filter': No
chain/target/match by that name
Perhaps ip6tables or your kernel needs to be upgraded

My config has CONFIG_IP6_NF_FILTER=m
I also note that ip6table_filter.ko doesn't get auto-loaded now. But even after modprobing it, I get the same message.

Is there some additional option I now need to enable ?

I was a little surprised by how CONFIG_NF_TABLES is mandatory for iptables to keep working, even if you don't have nft userspace. (The only relevant thing in the Kconfig was related to x_tables,
which I wasn't using).

Perhaps either some select's, or additional help text ?

Cc'ing Tom:

cb1ce2e ipv6: Implement automatic flow label generation on transmit has allocated socket option 64 which is already reserved by ip6tables.

I'm going to send a patch to fix this.

#3 lore raw

Thanks for catch an fix!

Quoted 35 lines · Pablo Neira Ayuso
Quoted 27 lines · David Miller

From: Dave Jones <[email protected]>
Date: Wed, 6 Aug 2014 15:52:22 -0400

CC:'ing netfilter-devel, Dave please do this in the future for netfilter reports, thanks.

Quoted 21 lines

After updating to Linus' current tree with todays net/ merge, I noticed that ip6tables doesn't work any more..

# ip6tables -F
ip6tables v1.4.19.1: can't initialize ip6tables table `filter': No
chain/target/match by that name
Perhaps ip6tables or your kernel needs to be upgraded

My config has CONFIG_IP6_NF_FILTER=m
I also note that ip6table_filter.ko doesn't get auto-loaded now. But even after modprobing it, I get the same message.

Is there some additional option I now need to enable ?

I was a little surprised by how CONFIG_NF_TABLES is mandatory for iptables to keep working, even if you don't have nft userspace. (The only relevant thing in the Kconfig was related to x_tables,
which I wasn't using).

Perhaps either some select's, or additional help text ?

Cc'ing Tom:

cb1ce2e ipv6: Implement automatic flow label generation on transmit has allocated socket option 64 which is already reserved by ip6tables.

I'm going to send a patch to fix this.