01-06-2015 02:50 PM
Currently I have a rather simple setup with a server, a printer, and several clients on a LAN. I also have several users that connect using the USG's Remote Access VPN feature via PPTP. VPN clients can connect to devices on the LAN fine by IP. Connecting to, or pinging, the host name is not working at all. nslookup resolves the correct IP.
I am comfortable making CLI changes and exporting them to the controller...
Here's what I have in my config.gateway.json to try to get this going. The eth1 IP is 10.10.1.1:
05-12-2015 12:36 PM
I am having similar issue.
I just got a couple at work to test. So far not overly impressed but I can see potential if Ubiquity gets their act together and supports more CLI features in GUI.
I setup remote PPTP VPN.
Was trying to use the router IP for DNS and could not get it to resolve DNS when connecting via PPTP.
I am testing using my iPhone btw.
Try taking out the 10.10.1.1 and just using Google's 18.104.22.168
I found out that I cannot use Router as DNS in this case.
I don't understand why this is though since a PC on the local LAN uses the router as a DNS server. I can even connect to the USG webpage from my iPhone using its IP so it is not as if it is being blocked.
I have not yet tested using another DHCP server (eg. a domain controller) on the network but I don't see why that wouldn't work.
I am not using Radius but rather local authentication with modified .json file. The files/instructions posted elsewhere don't work correctly (error in json) and some other firewall settings have to be added in order to get to work, but that's another post I will do shortly after I do some testing.