ROS and disabled subnet settings

Does any anybody know if ROS still uses an IP subnet settings even after it’s been disabled ?

A quick example of this is where you have say 192.168.0.2/30 disabled=yes but when you try to add 192.168.0.2/30 disabled=no, ROS complains that the address is already being used?

A disabled entry is still there for purposes of duplicate detection but it is not in active use.

I haven’t tested it myself, but ChangeLog says this behavior has been changed in the 6.36rc (unstable version currently in public testing):

What’s new in 6.36rc36 (2016-Jul-06 09:51):

*) address - allow multiple equal ip addresses to be added if neither or only one is enabled;

This makes no sense ? Duplicate detection should only be for active entries and not disabled entries, I mean when does a entry become effective - Active or Disabled?

That is the way it should be, but i fear until this ROS version that when testing different IP subnets, ROS was also using disabled IP subnets and disabled routing network interfaces, etc… along with active ones, which I suspect was causing routing inconsistencies even after rebooting?

I’m sure disabled interfaces (in 6.35) cause no routing issues, I have used those.
Could be that they briefly flipped on/off at boot, I have not closely observed that.
Never tried to have the same entry both disabled and enabled, I see no purpose for that.

I was only using that both disabled and enabled as a example and yes it would serve no purpose?
My topic question was leading into a practical operational example of where I was disabling /30 ip and network routing entries and checking /29 setting, in this scenario I would ask is ROS still go to consider the disabled /30 entries ?

It is becoming too unclear to me.
Can you please describe clearly what is your issue with a clear example, not morphed into some theoretical case?

I have no issue now but was trying to establish if simply disabling items like,
IP address’s /30
OSPF network /30
MPLS LDP Interface
While trying to setup a /29 assignment, was causing ROS to be confused as to which setting are to used ?
in my case routing would not fully re-establish with the disabled /30’s and active /29’s even after rebooting, the solution to delete disabled entries, this when using ROS Version 6.35, I was wondering if other users has experienced similar.