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

VMware no Connection

Hey all,

since I have the slight feeling that utm will not be supported in the future I wanted to make the first steps with xg

I have installed it into a VMware on my Mac and I am not able to ping or webaccess the firewall.

Questions:

1. is it possible to access the Sophos via wan Interface by default?

2. i changed the lan ip of Sophos to a valid subnet ip (same as wan) but that did not work as well

Unfortunately I cannot tell my Mac to be in 172.16.16.0 in WiFi - he knows that this up cannot so anything within the 192.168. net

So I am a Bit löst and don’t know how I can get it work.

I have tried to deactivate my local Mac firewall and packet filter but that did not work.

I tried to set up a loopback interface, tried to add the 172.16.16.16 to the /etc/hosts but did not work either

Hope you have some good ideas to support me

Thanks a lot



This thread was automatically locked due to age.
Parents
  • Let me see if I understand what you are trying to do?

    You have installed vmware on your MAC Mini, mac book pro and then want to install the XG software on the VMWare?

    The setup seems very strange to me. There is no security provided by this configuration.

    The wifi is integrated into the MAC hardware and OS.

    Ian

  • Hey Ian,

    thanks for your instant help. As long as the utm runs there is no need to rush so I have installed the Sophos xg locally on my MacBook. So I only want to access the xg (vm) from my MacBook so to say from the same device

    Thanks

  • Hi Paul,

    sorry, I do not understand why you are running vmware on your MAC to run a security system that needs two interfaces? You would be better off with an old PC with two intel nics.

    Ian

Reply Children
  • Only to play around with the new gui before purchasing adequate hardware. My home is protected by utm hw appliance

    The vm has two virtual nics

  • Hi Paul,

    thank you for the explanation. You can't change the internal IP address until you have set the password in the GUI, then you can access the CLI and change the IP address and DHCP range.

    You could try the external interface for the initial setup?

    Ian

  • Ah ok. Thanks. Thought I could change it in the terminal window when I am logged in

    Unfortunately the external interface (same subnet) is not responding either. Good to know that it should work by default

    I have the feeling that request is send to the default gw and is not routed directly to localhost whiteout going through the network