Issue with container not working on new HEX Refresh (E50UG)

A faction convinced MikroTik to make that a feature in 7.16, even though it goes against all history of how ping works. Stopping the last server bound to eth0 on a classic Linux box doesn’t cause ping to stop, but now it does for veth on ROS. The stated logic for this is to allow ping to be used as a container’s health check, even though you could not do that on any other container platform for the same reason.

Alas, we are likely stuck with this wool-headed decision now, in the interest of avoiding flip-flopping.

(Change log entry: “container - clear VETH address on container exit and mark interface as running only when VETH is in use”. Imagine if /interface/bridge worked the same way. :man_facepalming:)