General • Strange issue with srd/dst address type 'local'

Hi all,

I'm doing some tests with my home router installation and it seems that I can't get dst-address-type=local match to work. I just add first rule in input chain like this:
Then I just do ping 192.168.1.254 and counter does not increase. Address 192.168.1.254 is assigned to eth5. When I watch traffic with torch, I can see that ICMP packets arrives with dst address of 192.168.1.254.

When I remove dst-address-type=local from the rule, then counter starts increasing. Intrestingly, if I invert dst-address-type=local rule, counter still does not increase. I do not really understand what is wrong. It should be all straightforward here, but for some strange reason it does not work as expected.

By the way, I'm running RouterOS version 7.14. WOuld appreciate if anyone has good ideas on how to troubleshoot this.

EDIT:
Small update. When I add above mentioned rule with dst-address-type=local from the beginning, then it works, counters are increasing. Then I change the rule, so that it starts blocking packets, something like adding src-address-type=local, which obviously will not match packets. Then I change everything back as it was originally dst-address-type=local and rule does not work anymore (or at least counters are not increasing). Then I need to remove and re-create rule and it works again. It also works, as mentioned above, if I remove dst-address-type=local.

EDIT2:
I have another RouterOS machine running version 6.49.10, and this behavior described above does not exist. This router works as expected. Could this be some kind of bug? Anyone can test it on 7.14?

Regards,

Statistics: Posted by alphalt — Sat Mar 02, 2024 1:01 pm

---