version x86, v6.43.7
lab 1
step 1 add 192.168.10.1/24 at one interface ( ping 192.168.10.1 ok)
step 2 delete 192.168.10.1/24
step 3 add 192.168.10.0/32 at the same interface (ping 192.168.10.0 fail fix it only reboot routeros )
lab 2
step 1 add 192.168.10.0/32 at one interface ( ping 192.168.10.0 ok)
WHY?
Hard to say without understanding whole network setting. Most important info is:
Anyway, first thing which I consider suspicious is using the 192.168.10.0 address in environment where you previously used 192.168.10.1**/24**. netmask /24 equals to 255.255.255.0 and simply means that 192.168.10.0 is network address, 192.168.10.255 is broadcast address (these two should be never used for particular host) and only 192.168.10.1-192.168.10.254 are available for hosts.
If you assigned the 192.168.10.0 to device in network where other devices are on 192.168.10.x/24, then I am not surprised it behaves funky.
no other setting, and only ping from himself,
I know about the available address, so step 2: remove 192.168.10.1/24 , step 3 : assigned the 192.168.10.0/32 to the device
[admin@mikrotik] > /ip address add address=192.168.10.1/24 interface=bridge2
[admin@mikrotik] > ping 192.168.10.1
SEQ HOST SIZE TTL TIME STATUS
0 192.168.10.1 56 64 0ms
1 192.168.10.1 56 64 0ms
2 192.168.10.1 56 64 0ms
sent=3 received=3 packet-loss=0% min-rtt=0ms avg-rtt=0ms max-rtt=0ms
[admin@mikrotik] > /ip address remove [/ip address find interface=bridge2]
[admin@mikrotik] > /ip address add address=192.168.10.0/32 interface=bridge2
[admin@mikrotik] > ping 192.168.10.0
SEQ HOST SIZE TTL TIME STATUS
0 192.168.10.0 56 64 0ms
1 192.168.10.0 56 64 0ms
2 192.168.10.0 56 64 0ms
sent=3 received=3 packet-loss=0% min-rtt=0ms avg-rtt=0ms max-rtt=0ms
I tried to replicate your issue but it did not occur. There might be something in your config interfering with it.
As I said earlier - without more info it is hard to guess.
If you share your whole config with ****
/export hide-sensitive file=yourConfig.txt
, then someone might find the issue.
Please, do NOT share screenshots of config unless the issue is related to winbox itself. Image is always hard to read because it contain just limited amount of info. Text config can be easily inspected and contains all details.
somehow I was in same issue. After recreating DHCP server from the screech solved this.
there is a record about this issue
official support said: " this is a known problem. That after changing netmaks connected routes are not updated properly. Removing and readding correct address from the beginning will fix the problem, or disabling enabling ip address after netmask change."
tested the second method, it don’t work.