Condition Match
Quoted 18 lines · --- Harald Welte
Quoted 18 lines · allen
Quoted 14 lines
Quoted 14 lines · Stephane Ouellette
Quoted 4 lines
Quoted 4 lines
I developped last week a new extension to Netfilter in order to
enable or disable a set of rules using /proc files.Yeah, as others have said, the idea is definitely cool.
Quoted 8 lines
Quoted 7 lines
Though the idea is cool, I think we are solving a problem the wrong way. Why add complexity to the kernel for a problem which can be solved without any problem from userspace?
Where is the problem in having a couple of different rulesets (e.g. created with iptables-save) which are then loaded using an iptables-restore commandline or a script at the shell of the firewall?
Harald,
I have already tried the solution you propose on a production
environment and it proved difficult to deal with. Using the condition match, it is far faster to enable/disable rule sets than it is with a set of scripts. It is also less error-prone on a management point of view as the firewall rules never change.
I would suggest that the condition match makes it to P-O-M, and let the users try it.
Regards,
Stephane Ouellette.
Quoted 1 line · Stephane Ouellette
--- Harald Welte <[email protected]> wrote:
( snip )
Quoted 6 lines
Quoted 3 lines
Quoted 3 lines
Where is the problem in having a couple of different rulesets (e.g. created with iptables-save) which are then loaded using an iptables-restore commandline or a script at the shell of the firewall?
Harald,
Quoted 8 lines
I have already tried the solution you propose on a production
environment and it proved difficult to deal with. Using the condition match, it is far faster to enable/disable rule sets than it is with a set of scripts. It is also less error-prone on a management point of view as the firewall rules never change.I would suggest that the condition match makes it to P-O-M, and let the users try it.
Yeah.
After thinking more about it, yeah. It IS cool.
Note:
1. Already many things are adjusted via /proc mechanism that are similar in that they are related to networking parameters that need to be modified on the fly.
2. Making a modification to netfilter rules by dumping and loading new rules is not cool and is prone to error "during the switch".
This method is only straightforward, but actually more complex in operation. ( The administrator has to think more )
3. The other thing would be a libipq thing, and there can be only one. And it is in userspace and it can die.
I think the /proc concept in this case is better than the load/modify/delete/add kind of concept.
I'm having a hard time thinking of a better "thing" than /proc.
It seems like the next best alternative is yet again some "new thing" that doesn't exist yet.
What new thing would be better than /proc ?
Who would "buy" something new ? so to speak...
For what it is worth, I second the motion here.
-AEF