Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 8 subscribers
  • Views 842 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

I can only connect to my Sophos UTM device when it has a single interface

exwhywhyzee

I had an issue with my VMWare host, which required me to reset it.  I had to recreate all the interfaces.  Every other server seems to work just fine, except for the Sophos UTM VM.

I was not able to connect to ping the LAN interface, let along connect to Webadmin.  I can access the console, so not all hope is lost.  

Randomly, I removed both interfaces, and then added just the LAN interface.  When I did this, I was able to access Webadmin, and ping anything.  I then added the WAN interface, which preceded to break connectivity again.

I get host is unreachable and destination is unreachable errors when I've tried to use traceroute or ping.  Any any all help will be greatly appreciated.  I rather not reinstall the system, which seems to be what happens whenever something happened with my previous Sophos UTM VMs.



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

    You could try reverting back to where you were able to access webadmin - lose one of the nics.

    Once confirmed you can access utm, review the .vmx file, noting mac address and pci positions of the working nic. Add in your 2nd nic (wan), save, then review the file again. Make edits so the original nic has the same pci locations as it did before.  You're looking for entries that contain "ethernet".  Make a backup copy of the file before you start modifying.

    It is possible to reassign lan interface through console, but is a rather painful process.  There this file "/etc/udev/rules.d/70-persistent-net.rules" , but that only seems to reference real nics, not virtual ones.

    I gave up on vmware/esxi over a year ago. I got some new hardware which esxi 7 didn't support (rtl8125 nic). I was trying to really trim the system by getting rid of the quad port intel nic card and sas card. New board has dual nic (i211 and rtl8125) as well as 8 sata ports. I migrated to proxmox which supports all the hardware without issue (including sata passthrough).

    When I used esxi I did periodic vm images using veeam (NFR license). It was clunky (and bloated), but ultimately did what I needed it to do. For a home environment, other than training, esxi is quite bloated.  Proxmox works just as well. I suspect if esxi ever does support that nic, it's unlikely i'll switch back.

Reply
  • 0

    You could try reverting back to where you were able to access webadmin - lose one of the nics.

    Once confirmed you can access utm, review the .vmx file, noting mac address and pci positions of the working nic. Add in your 2nd nic (wan), save, then review the file again. Make edits so the original nic has the same pci locations as it did before.  You're looking for entries that contain "ethernet".  Make a backup copy of the file before you start modifying.

    It is possible to reassign lan interface through console, but is a rather painful process.  There this file "/etc/udev/rules.d/70-persistent-net.rules" , but that only seems to reference real nics, not virtual ones.

    I gave up on vmware/esxi over a year ago. I got some new hardware which esxi 7 didn't support (rtl8125 nic). I was trying to really trim the system by getting rid of the quad port intel nic card and sas card. New board has dual nic (i211 and rtl8125) as well as 8 sata ports. I migrated to proxmox which supports all the hardware without issue (including sata passthrough).

    When I used esxi I did periodic vm images using veeam (NFR license). It was clunky (and bloated), but ultimately did what I needed it to do. For a home environment, other than training, esxi is quite bloated.  Proxmox works just as well. I suspect if esxi ever does support that nic, it's unlikely i'll switch back.

Children
No Data
Unfiltered HTML