Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

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

Sophos XG under ESXi

Going though this as a guide:

https://www.linkedin.com/pulse/configuring-sophos-xg-firewall-vmware-esxi-kelvin-charles?trk=pulse_spock-articles

I got Sophos to work, however i had gto had 3 vNins in VM, and at this stage i'm still wondering why i needed 3, and not 2

VMWare Fusion: 1 private assigned : 169,x,x for NFS datastore on QNAP

1. Bridged

1. Host Only

ESxi can connect on 169.x.x a ok. and after adding vSwitch1 and Port Group, I get internet access, while at the same time having QNAP nas as my datastore (NFS)

However, while this works in VM (servers/clients) it does not work in Sophos, which i find strange, because 169.x.x is a network itself, it just has no gateway..

ESXi connects on 169.x.x just fine, but sophos cannot... would have thought this would work:

Port1: 169.254.x.x

Port2: Bridged (WAN)

configured via console... but doesn't work. can someone shed some light as to why?



This thread was automatically locked due to age.
Parents
  • Hi,

    the 169 address range is not valid. The address range is used by devices when they cannot receive an IP address eg they have no network connection.

    ian

    XG115W - v20.0.2 MR-2 - Home

    XG on VM 8 - v21 GA

    If a post solves your question please use the 'Verify Answer' button.

Reply
  • Hi,

    the 169 address range is not valid. The address range is used by devices when they cannot receive an IP address eg they have no network connection.

    ian

    XG115W - v20.0.2 MR-2 - Home

    XG on VM 8 - v21 GA

    If a post solves your question please use the 'Verify Answer' button.

Children
No Data