Hi all, Currently, our L2TP/PPTP servers authentication is purely based on username and password for each user (Secrets). Our problem is that these users have a basic understanding, and they frequently configure their VPN connection on their personal computers as well. The objective is to restrict t...

You could only advertise the same /24 if the two locations are connected by some other means (ex. layer 2 circuit between them), or at least some kind of tunnel over IPs that are not part of that /24. Otherwise you could have packets returned to datacenter B that are meant for datacenter A and the ...

Hi all, Currently, we're an AS with a /24 prefix. We're advertising these IPs through 2 peers. The problem is that we'll need to move our datacenter, physically, to the new company address. What is the best solution to this case? We bought another CCR just in case we need to keep it powered on in th...

By passing with Radius the Prefix, in more than one customer? Because I did test it an got duplicated pool error, as I stated above in red. How did you make it? Ah... understoodI I've tested with only one "user". I'll test again later. In case of accounting, I got it ( using the Pool defi...

The "Delegated-IPv6-Prefix" is now working on 6.48.1! Prefixes are being delegated to the clients, apparently.

But, the accounting packet (Router -> RADIUS) doesn't contains "Delegated-IPv6-Prefix" attribute. Do anyone managed to have this working?

Anyone tested on 6.45.x ? Hi Pietro, glad to see you. I just tested on 6.45.6. For PPPoE, sending "Delegated-IPv6-Prefix" attribute did not work. I found that enabling "dhcp" option in RADIUS Client resulted on RouterOS sending "Delegated-IPv6-Prefix" to RADIUS Server,...