Hello!
Only one user can connect to VPN at a time. Each user has a different location across the country (they are not in the same local network)
I’ve read that people have problems with multiple connections being behind the NAT. But this is not the case.
RB951G-2HnD 6.49.6
PPTP server
Each user has its own secret
‘Only one’ set to No
L2TP has the same problem
I can post the config if needed
Users:
With different IPs across the country
Windows 10
Problem:
Only one user can connect at a time
If one is already connected another gets the message
‘The connection was closed by the remote computer’
Am I missing something?
How to set up PPTP (or L2TP) server to accept simultaneous connections from different IPs?
If the clients are not behind the same public IP address it should just work. Use /export hide-sensitive for RoS v6 or just /export for RoS v7, copy the output, remove any other sensitive or personal information (such as serial number, static public IP addresses, credentials in scripts), and post in a code block (the icon above the text box when posting on the forum).
And just don’t use PPTP, the MSCHAPv2 authentication and MPPE (RC4) encryption have known longstanding insecurities.
Probably due to using using local-address=pool_router in the PPP profiles - as the pool only contains one address the pool is them empty for subsequent connections. Use local-address=192.168.1.1 instead.
Pools should not overlap, it would be wise to delete pool_router, pool_local and dhcp_pool1
Replacing pool_router to the exact IP address solved the problem. Thank you very much!
Noted your other suggestions too. I appreciate it.
I used pool_router as a kind of variable. Comes from a programming background. I don’t like “magic numbers” )
(Curious whether RouterOS allows the creation and using variables)
Pools are as the name suggests are a pool / list of addresses. When an item is allocated from the pool it cannot be used by anything else until released.
There are address lists and interface lists which can be used in place of hard-coded addresses or interfaces, but only in certain places such as firewall rules. There isn’t a generic variable object which can be used anywhere in RouterOS.
I would use a lightly different wording - you can use generic variables in scripts, and you can use scripts to add/remove/modify configuration items, but configuration items themselves cannot refer to generic variables.
In the specific case of /ppp secret items, you can let each of them to refer to another pool that contains just a single address, but it is in fact a two-stage reference - the /ppp secret item links several properties to a username, so there is little point in using an alias for just one of them.