Hi all, in what board should I report a bug in the iOS mobile Mikrotik app?

If here is OK, here's what I encounter.

I get access to a router from my up-to-date iOS device with the latest version of the Mikrotik app, while using a Wireguard VPN. So far, so good.

I then want to add another peer, and upon entering the "Allowed address" and saving it, the field shows a "0.0.0.0" address.
Since I have a working peer set up that also shows "0.0.0.0" in that field in the app, perhaps that is normal behaviour. Strange, but normal.

Then lastly I press the (save) check mark and I get a notification "no allowed-address set", and the peer will not be created.

If this is a limitation of the mobile app, I can accept that - but then WHY would the option be available?

Can someone duplicate this error? Does it do the same on Android?

Thanks in advance for your time.

Can someone duplicate this error? Does it do the same on Android?

Not wrong. I get same 0.0.0.0 and also that it still won't save the peer on iOS to RouterOS 7.17beta4.

It seems the field does not know it's a ip-prefix type, since it should default should be 0.0.0.0/0, not just plain "0.0.0.0". So, I think, when it tries to save it, RouterOS rejects it since the field is not a prefix. But net result same "no allowed-address" error.

But I'd recommend you file this at help.mikrotik.com as a BUG - Mikrotik does not always review every forum post and/or may miss the clear bug here.

I got my answer, pretty quick, via email from support@mikrotik.com. Thanks for the quick response!

"Hello,

Thank you for contacting MikroTik Support.

This setting from app does not work at the moment, please use winbox for configuration. This will be fixed in the future.

Best regards,

Oskars K."