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

My experience reinstalling Sophos OS with current build ISO

Yesterday I decided to reinstall my Sophos OS (Upgraded from beta with beta license)
due to the license being tied to the Installation it was necessary to instal the home use license.

First I installed Sopohs OS from the ISO. Then I tried to reach the webadmin Interface on 172.16.16.16/24.
The Interface was pingable but it was not possible to reach any services. (User Portal, Webadmin etc)

So I reinstalled again. Same thing after that.
Login to the console was also not possible, because I had to accept the EULA to get in there.

I think the activation process is not really intuitive and straight forward.
I also don't know how to activate Sophos OS if you don't already have some router and need PPPoE to get a Connection to the Internet.

The activation process in Sophos UTM was much easier.

After reinstalling a few times I decided to Switch back to my UTM 9 (other SSD).
I couldn't manage to access the freshly installed current build and activate it.

One time I was able to get to the webadmin. After relocating the Sophos XG I wasn't able to get in anymore.
It seems that some ports aren't opened under certain circumstances, not knowing which they are.

After seeing the beta and the activationprocess of the new Sophos XG, I really wanted to like it. But finally I think it has to improve much in some areas to be a replacement for Sophos UTM.

I know that some technical areas, like the Webfilter are outdated in Sophos UTM (32-bit) but currently I wouldn't switch important customers to Sophos XG.

I will try again in Version 2.

I hope it has improved by that time. Currently I think that it has been released too fast and it's still beta.

What do you think about it?



This thread was automatically locked due to age.
Parents
  • Strange thing is, that it worked in beta and it worked with the current build one time.
    I would suspect that the Management IP would even be pingable if the NIC is not supported.

    And it worked with current build (with upgrade from beta to actual build) without an issue.
    So i would suspect that some ports aren't opened, because the IP is pingable but I can't access the webadmin for initial setup.
Reply
  • Strange thing is, that it worked in beta and it worked with the current build one time.
    I would suspect that the Management IP would even be pingable if the NIC is not supported.

    And it worked with current build (with upgrade from beta to actual build) without an issue.
    So i would suspect that some ports aren't opened, because the IP is pingable but I can't access the webadmin for initial setup.
Children
No Data