Actions
Bug #187
closed
m0n0wall config conversion trigger invalid
Start date:
11/28/2009
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:
Description
If the string "m0n0wall" is found anywhere in the configuration, including things like a rule description, it gets converted. Need better checking to not convert pfSense configs that happen to contain "m0n0wall" somewhere within them.
Updated by Scott Ullrich over 14 years ago
- Status changed from New to Feedback
The change is only triggered if <m0n0wall> is found. It then proceeds to convert all m0n0wall -> pfSense which is perfectly fine and will be difficult if not impossible to improve on this.
Updated by Chris Buechler over 14 years ago
- Status changed from Feedback to New
It's triggered now with "m0n0wall", not "<m0n0wall>". The latter would be fine.
Updated by Scott Ullrich over 14 years ago
- Status changed from New to Feedback
It now looks for <m0n0wall> as of r1d68379
Actions