IP is up on port that's down

I figured out strange behavior of MT ip engine on ROS 6.43.13:

I take MT router, reset it to the clear setup (no fw, no IPs, no bridges).

Then I set up one (single) IP on one (single) Ethernet port, and try to ping it from within the router. Ping is on as expected.

Then I disable the port - and the ping keep going on, even that the port is down, and thus the subnet is not available. Moreover, I see the route to the subnet via the port in question - even when no such a port is up!

I feel very fuzzy on this, so please advice if this is the expected behavior? I really need to have the subnet on the device only if the port is up.

I kind of understand where you are coming from but that’s not necessarily how it works.
By disabling the interface you are disabling the physical access on that side of the interface. Think of the IP sitting between the CPU and the interface you’re assigning it to.

This is kind of concept approach i agree, but how can i have ip disabled as i have port down? What i need is to down it as the link is down and back up as the link goes up again.

I do understand if the ip is on the bridge bit it is on object that phisically or logically disabled, this way it can not stay up (

This was working… we are used to use loopback as a bridge to avoid the IP to get down, but now doesn’t make any sense, since the IP is always answering requests even with the interface down.
Please, correct this Mikrotik.