If you can connect the phone directly to the Mikrotik's Ethernet port, you can use the script configured at the dhcp-client attached to the WAN interface to switch the port down and up again each time the address changes (or with each assignment regardless whether it differs from the previous one o...

It's hard to me to suggest a fix for your problem without understanding what is going on behind the scenes. If I suggest you some action, it would be only a weak guess. I think it's better to you to discover what's happening (running the tests I proposed is a good start). You can also put the packag...

Hi anav, This is not actually a response for your problem, but it can help you. First, the most important part of the manual (OBi Device Admin Guide) that you should read is (from pg. 95): NAT Traversal Considerations If the device sits behind a NAT (typically the case), it can discover the mapped e...

Where did I state I have one WANIP> I have two WANS and one voip modem on a single private IP behind the router which is static. Hi anav, When you have two WANs and a VoIP modem using a single private IP behind the router, is the same case discussed in this post. In your case, your modem works as t...

I think the solution given by boen_robot (completely stop using 'print terse' and 'print default' and so use 'print as-value' to create a custom but parseable output). I also like the idea to print an API compatible output (since there are libraries that can parse API outputs for us).

Just adding other outputs that will be wrongly parsed when using print terse : /interface bridge add name="teste mtu=1500" That produces: 2 R name=teste mtu=1500 mtu=auto actual-mtu=1420 l2mtu=1522 arp=enabled arp-timeout=auto mac-address=00:0C:42:74:99:F3 protocol-mode=rstp fast-forward=y...

Hi, As I know, there are four good ways of processing complex print outputs from Mikrotik: using the Mikrotik API, or using the 'print detailed', 'print terse' and 'print as-value' commands. I use Fabric (http://www.fabfile.org/) to manage Mikrotik hosts. It uses SSH as backend: so, I rely on 'print...

Hi mrz, Thanks for your attention! In short (after our discussions), I think you have two ways of implementing this: 1) Delete assigned ssh-keys when user is removed -> My first proposal Or: 2) Associate ssh-keys to user via internal IDs (instead of via usernames - strings), so keys will become inva...

I do NOT want to share any key between users. I only replied to the docmarius consideration. He wrote that the keys should be kept because someone could share a key between users: What if you want some key shared between multiple users? And I said the consideration doesn't make sense because there i...

Hi @docmarius, I'm answering your considerations bellow: 1) Since you added the keys in a separate step, how do you expect you the router to guess you want to remove them or not together with the user? I think both behaviors (keep or delete the keys) may make sense - there are arguments to both of t...

I did the same tests again and, in all tested Mikrotiks, old users regained access when recreated. It seems that users are linked to keys by name and not by internal ID (I agree if they were linked by internal IDs, there was no problem - but it seems that it is not the case). So, I run the following...

Hi @sindy, thanks for your explanation. You are right: the SIP problem is not a SIP problem, but an UDP NAT problem (a more general problem). It isn't even a bug: it's a UDP NAT limitation (a protocol limitation). I made some NAT tests and understood better how NAT works in MikroTik. I'm publishing ...

Hi @mrz, I have two considerations: 1) I made a test with a user in a production router (version 6.39.1). I removed the user, tried to login via SSH - it failed, re-added the user, and tried to login via SSH again: the old public keys were allowed at this point. debug1: Offering RSA public key: /Use...

Hi @mrz. Thanks for your response. But what do you think about the pros/cons arguments at the end of the post?

Issue: After removing user, its ssh-keys are not removed together. Description: Consider we have a user in MikroTik that have public SSH keys (RSA or DSA) already imported. If we remove this user, its public SSH keys are kept in the system. Maybe the expected behavior would be remove all public SSH...

Some new info: An employee from my company realized that may exist connection-type=sip2 entries (although "sip2" connections are not documented in MikroTik wiki - only "sip" connections are - https://wiki.mikrotik.com/wiki/Manual:IP/Firewall/Mangle or https://wiki.mikrotik.com/wi...

Issue: SIP client cannot re-register in the SIP server after switching ISP (different NAT). Description: In our setup we have two ISP providers, a SIP client with a private IP, and we're using NATs (a different NAT for each ISP provider) with SIG ALG translation, aka SIP nat helper. When changing t...

Hi, This is a very interesting question. As you already know, when setting a BGP peering, it's necessary to set a route ID in our BGP instance. The idea is the same used by the OSPF: We will use the same router ID in all of our interfaces. So, all of our neighbors will know that the route announceme...