Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 5 subscribers
  • Views 1134 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Remote Access SSL VPN

Pawel Kazinski

Hello All,

I have recently added a new NIC to my UTM 9.705-3 and found that if I disable it (bring down the interface) my remote access ssl vpn no longer connects. I did not change anything on the vpn configuration and it works fine when all interfaces are UP. What is strange is that the new interface is not defined in the VPN configuration. Is this per design that all interfaces must be UP or is this a bug.

Your help would be greatly appreciated.

Thank you



This thread was automatically locked due to age.
Parents
  • 0

    hello H_Patel,

    The interface that I bring down is a LAN interface (eth3). To give you some background, I originally only had 1 SSL VPN rule that would connect to ETH1 and ETH2 and that worked great. I then added a third interface ETH3 and configured another SSL VPN that connected ONLY to ETH3. I usually use ETH3 only for testing purposes and have it down. Once I noticed this weird behaviour I removed the remote SSL VPN that connected to ETH3 and only have the original remote SSL VPN.

Reply
  • 0

    hello H_Patel,

    The interface that I bring down is a LAN interface (eth3). To give you some background, I originally only had 1 SSL VPN rule that would connect to ETH1 and ETH2 and that worked great. I then added a third interface ETH3 and configured another SSL VPN that connected ONLY to ETH3. I usually use ETH3 only for testing purposes and have it down. Once I noticed this weird behaviour I removed the remote SSL VPN that connected to ETH3 and only have the original remote SSL VPN.

Children
No Data
Unfiltered HTML