Elk RP and disabled rules, always reports conflict

[michelkenny]

I have my Elk RP check for conflicts upon connecting and disconnecting. When I mark some rules as disabled, Elk RP will always report a conflict with my rules when I connect and disconnect (presumably because the disabled rules are not sent to the Elk, and Elk RP thinks they are missing). Is this a new bug in Elk RP or has it always been like that?

 

[wuench]

I have my Elk RP check for conflicts upon connecting and disconnecting. When I mark some rules as disabled, Elk RP will always report a conflict with my rules when I connect and disconnect (presumably because the disabled rules are not sent to the Elk, and Elk RP thinks they are missing). Is this a new bug in Elk RP or has it always been like that?

It's worked that way for me too as long as I can remember...

 

[ddennerline]

I gave up on disabling rules because of synchronization idiosyncrasies. I ‘believe’ ElkM1G does not have a disable rule field, so it becomes difficult to synchronize rules between two devices.

Instead, I frequently export/save rule reports. If I ever need to re-enabled rule, I just reenter the rules back into ElkRP (bit of pain). I wish ElkRP would provide a method to copy-n-past raw rules into editor (without using the wizard-type UI). This would make it easier to version rule files. I know this would increase rule verification costs.

 

[electron]

I have my Elk RP check for conflicts upon connecting and disconnecting. When I mark some rules as disabled, Elk RP will always report a conflict with my rules when I connect and disconnect (presumably because the disabled rules are not sent to the Elk, and Elk RP thinks they are missing). Is this a new bug in Elk RP or has it always been like that?

I have been having this problem for years, now I am wondering if it is because of a disabled rule, will have to check my rules database again.