The sophos connect client cannot select a bridge or no IP interface as the service interface
When I was using SOPHOS Connect Client of XG firewall, I entered the configuration content and clicked application
My firewall is bridged behind the gateway and switch (port1 area wan; port2 area LAN; IP address is given to the bridge port after wan bridging)
However, I noticed that in the sophos Connect setting, only port2 port (area wan) can be selected as the VPN interface and bridge port cannot be selected, while port2 port has no IP state and shows NA. I suspect there is something wrong with this place
Therefore, I tried to do the experiment, and configured a static IP (area wan) for the connectionless port3 port, and then added the port3 port to the sophos Connect interface, and found that the configuration could be applied correctly.
When I changed the port3 to DHCP, because the interface was not connected to the cable ,DHCP not gIve the address , , so it showed NA at the interface of sophos connect. At this time, when I clicked the application configuration, the above error was repeated: sophos connect Client could not be updated
My firewall version is SFOS 17.5.1 mr-1. I guess whether this bug has been fixed in the subsequent version. Therefore, I found an XG firewall of SFOS 17.5.5 mr-5 for reappearance test, and the result is still the same as the above phenomenon
I think it may be because the interface option of sophos connect only filters the ports in wan area (excluding the bridge port), which leads to this problem. This makes the firewall unable to use the sophos connect VPN function in bridge mode. I hope the next version update can fix this bug