Hi,
I want to understand why I have for some clients multiple SSTP Server Binding:
Capture.JPG
and know how to prevent this from happening?
Any help? Thanks!!
Hi,
I want to understand why I have for some clients multiple SSTP Server Binding:
Capture.JPG
and know how to prevent this from happening?
Any help? Thanks!!
Try static binding instead of the dynamic.
Hi Jarda, I’m not using a any Pool but setting the IP in the ‘Remote Address’ field of each Secret.
Is not that static binding?
No. The “D” mark is for dynamic. Add static server binding like new interface…
Ok, I got it!
Can you help with the script to create the SSTP Server Binding? I didn’t find the syntax ![]()
Use winbox. Press + in interface window, select the sstp server binding and fill the values. No need to any script for that. Anyway I left the sstp and moved to l2tp some time ago. It is much faster.
Yes, I found how to do it with Winbox but I have to create 250 interfaces… the script will be very helpful ![]()
Make one. Do export to get the script and replicate it as many times as you need.
Good idea! Thanks!!
I created one SSTP Server Binding for each client but some of them are still generating dynamic interfaces as well… any idea why?
Capture.JPG
If there is not any matching problem just kill the dynamic ones and let it reconnect. Maybe do it several times, it should catch the static ones. Check you have the same timeouts on the both sides of the link.
This keeps happening all the time! ![]()
When the clients are re-connecting to the VPN server, sometimes are creating dynamic interfaces and sometimes not.

How can I prevent this from keep happening? Dynamic interfaces are a problem because I cannot access the client until I remove them all and leave only one interface for the client.
Any help??
What version do you use now? Maybe you can kill dynamic bindings by a script regularly. I have not seen this behaviour for long time now on my routers…
Dynamic server bindings are created when no static bindings exist. This is the case when the client is reconnecting before the server realizes the previous session has ended.
I created two bindings per user for this reason - works OK. Create three or more per user if you experience more reconnects within session timeouts.
Check the timeouts what was suggested by me year ago…
Shortening timeout (server side) will help minimizing the problem, but if the client is somehow forcedly disconnected (restart / interface went down) it will reconnect before server times out.
mati83, you could try setting ‘only-one’ to ‘yes’ in ppp profile.
This will probably deny the new connection as long as the old connection is active.
See: http://wiki.mikrotik.com/wiki/Manual:PPP_AAA#User_Profiles
I tried already decreasing the timeout and also creating multiple bindings but they didn’t solve the problem (in some cases I got more than 25 dynamic binding).
Finally nescafe2002’s suggestion about the ‘only-one’ setting solved it!!
- I totally missed that setting.
Thanks a lot!!