Re: 2.6.20-rc4: regression: iptables failed to load rules

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Linus Torvalds
Date: Tuesday, January 9, 2007 - 10:33 am

On Tue, 9 Jan 2007, Tomasz Kvarsin wrote:

I bet you enabled the new transport-agnostic netfilter, and didn't enable 
some of the actual rules needed for your iptables setup (they have new 
config names).

I do think that the netfilter team has been very irritating in changing 
the config names, even if it "is logical". 

Somebody should stop the madness, and tell people what config options they 
need for a regular iptables setup like this. Rather than say "just compile 
everything". There's about a million different filters, and they all 
depend on one infrastructure or another.

And then the networking people should F*NG STOP that config name changing 
madness! The config names should match the _usage_, not some 
implementation detail. And failing that, leave the config options named 
something illogical, as long as people don't have to change their config 
file all the time and answer millions of questions that they don't care 
about!

David, please crack some heads.

		Linus
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
2.6.20-rc4: regression: iptables failed to load rules, Tomasz Kvarsin, (Tue Jan 9, 12:29 am)
Re: 2.6.20-rc4: regression: iptables failed to load rules, Linus Torvalds, (Tue Jan 9, 10:33 am)
Re: 2.6.20-rc4: regression: iptables failed to load rules, Patrick McHardy, (Wed Jan 10, 12:56 am)
Re: 2.6.20-rc4: regression: iptables failed to load rules, Linus Torvalds, (Wed Jan 10, 9:15 am)
Re: 2.6.20-rc4: regression: iptables failed to load rules, Bill Davidsen, (Wed Jan 10, 3:10 pm)