I've setup an ERX for a customer with local authentication and it seemed to work.
Later today I got a message from the customer that they have tried to access their office from their home and the results was not that good. My customer is using a Mac with Mac OS Sierra which is the main reason to get L2TP instead of PPTP that they used via their Win SBS.
1: It seems like the socket gets broken in some way after a while resulting in the following screenshot when they are using MS Remote Desktop:
I logged in the the ERX some times via SSH and were going to ping 8.8.8.8 to see how long the socket was OK.
I got results similar to the following more than one time:
ssh <username>@<customer erx> Welcome to EdgeOS By logging in, accessing, or using the Ubiquiti product, you acknowledge that you have read and understood the Ubiquiti License Agreement (available in the Web UI at, by default, http://192.168.1.1) and agree to be bound by its terms. <username>@192.168.0.1's password: Linux <customer ERX> 3.10.14-UBNT #1 SMP Fri Jul 29 16:53:39 PDT 2016 mips Welcome to EdgeOS Last login: Thu Oct 13 19:24:22 2016 from 192.168.0.180<username>@<customer ERX>:~$ pinBad packet length 619497416. ssh_dispatch_run_fatal: Connection to 192.168.0.1 port 22: Connection corrupted
I then tried to log on to the GUI using Chrome via the LAN address while connected via L2TP using port 10443 since the customer used 443 to their server on the LAN.
What can cause this and how can it be fixed?
This is the first ER* configured with L2TP that I've deployed at a customer so I really wan't to get it working as it should. I can live with the GUI, that can be solved in other ways, but the L2TP Must work.