I migrated my software UTM (9.351-3) to new hardware a couple of days ago. I maintained the same version and imported the exported config from the old hardware. The old hardware had 5 network interfaces but one was unused and not assigned to any purpose. The new hardware has 4 network interfaces. I moved around some of the interfaces to my preferred arbitrary network ports which I have come to expect anytime I have to do a config import. Everything worked except Dyndns which was trying to update the host entry with the non-routable IP that my ISP assigns to my External WAN interface. I had to change the dyndns update method from interface to web and then it updated the host correctly. But then I found I could not remote access into the UTM. Just times out. I could sporadically get connected to the user portal and SSL VPN when inside the network. I checked with the Management:User Portal:Network Settings and the interface was set to Any. I changed it to External (WAN) address. Also checked out the Remote Access:SSL:Settings interface address and it changed already to External (WAN) address. I stopped and started both User portal and SSL VPN Remote Access Profile. But I still cannot get connected to the 443 port and see the User Portal nor does SSL VPN get a response when connecting outside the network. The user portal now no longer works from inside the network (when I changed the interface address from any). Adding in Any to the Allowed networks did not help. Everything worked on the old hardware so I am not sure why Remote Access is not working on the new hardware. Any advice? Here is a snippet from the openvpn log on the UTM: 2016:05:20-08:47:07 myfirewall openvpn[4665]: MANAGEMENT: Client connected from /var/run/openvpn_mgmt 2016:05:20-08:47:07 myfirewall openvpn[4665]: MANAGEMENT: CMD 'status -1' 2016:05:20-08:47:17 myfirewall openvpn[4665]: MANAGEMENT: Client disconnected
↧