Using ROS 6.45.5 on CCR1009

If the admin changes the name of a filter, this does not propagate through to any peers using the filter. What happens is the peer simply starts acting as if there were no filter.

Of course, this is an undesirable situation.

My suggested behaviour would be for either-
1. Name changes to propagate through
2. Any peer without a valid filter, when one is specified, to shutdown automatically.

Can confirm this behavior. I would go a bit further and ask for the out filter to be required when configuring a new peer.

Can confirm this behavior. I would go a bit further and ask for the out filter to be required when configuring a new peer.

Nice suggestion.

MichaelHallager, does this behavior occur in a 6.44.5?