ElkRP conflicts and disabled rule

[dtreyes]

I just noticed that whenver I disable a rule from ELKRP, I get conflict the next time I connect to the system through ELKRP. Is this by design ??? What is the best practice to temporarily disable elk rules. Thanks

 

[electron]

I think when you disable a rule, it removes it from the Elk M1, and just keeps it in ElkRP. When enabling it again, it sends it back to the M1. At least that's what I am thinking based on my own experience.

 

[dtreyes]

I think when you disable a rule, it removes it from the Elk M1, and just keeps it in ElkRP. When enabling it again, it sends it back to the M1. At least that's what I am thinking based on my own experience.

Since I have M1XEP and connect to M1 from diff machines on the network, does that mean I need to sync the database to all those machines that I am using.

 

[electron]

That's a good question. I guess it would be better if Spanky answers this question, in case I am wrong. However, I strongly urge to store the database on a network share, so it doesn't matter what machine you are using (or you will run into issues with comments not matching, etc.).

 

[nov0798]

Yes, if you are using different machines with the RP on it, then you need to update the machine when you log back in. The RP checks for differences in the M1's programming compared to what the RP database has in it. You can disable that feature, but why? Once you make changes on one machine using RP, you then send it to the control and save it on the local database. When you connect with a different machine, the database on the machine is different than that compared in the M1. This is all covered in the RP users manual.