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 disables eth0

I installed Sophos UTM 9.5 Home on a PC. During setup I set eth1 as LAN. After the installation finished I browsed to the web interface and found out that for some reason eth0 which is connected to WAN was down.

 

For some reason Sophos disabled eth0. To confirm this I simply unplugged the ethernet cable from eth0, and plugged it on my ubiquity router and it had activity. Plugged it back to the PC on eth0, and it was dead.

 

So I formatted the PC again and tried the 32bit version of Sophos UTM and had the same result. So this time I formatted the PC again and installed pfsense. Both LAN & WAN was just fine. 

 

So this is definitely an issue with Sophos.

 

Anyone faced this issue before? Any workarounds? 

Thanks



This thread was automatically locked due to age.
Parents
  • UTM interfaces are virtual objects that are bound to a Linux interface.  Here are some things to check.

    • Ensure that you have two UTM interfaces, bound to different Linux interfaces, and enabled (slider switch in the on position.)   
    • If you do not have two UTM interfaces, you need to create one and connect it to the unused Linux interface.   
    • If one UTM interface is bound to two Linux interfaces, you have a bridge configuration instead of two interfaces.  Undoing this problem will require adding additional Linux interfaces or rebuilding.  
    • If a UTM interface is bound to an inappropriate Linux interface (e.g. NUL), you will need to delete and recreate it.

    I have been confused by the web interface for initial system build.   Basically, it asks for the interface parameters for each of four interfaces, but it appears to the untrained eye like it is simply asking you for the same information because you made a data entry error.   Also, it asks for network information on four interfaces even if you do not have four interfaces.  The shell interface is much easier for this step.  If you were confused by this point, you may have the same IP configuration on both of your UTM interfaces, and the solution is to fix one of them.   

    Also check that "default gateway" is checked on one of the interfaces, but it sounds like you have not gotten to the point that this would matter yet.

Reply
  • UTM interfaces are virtual objects that are bound to a Linux interface.  Here are some things to check.

    • Ensure that you have two UTM interfaces, bound to different Linux interfaces, and enabled (slider switch in the on position.)   
    • If you do not have two UTM interfaces, you need to create one and connect it to the unused Linux interface.   
    • If one UTM interface is bound to two Linux interfaces, you have a bridge configuration instead of two interfaces.  Undoing this problem will require adding additional Linux interfaces or rebuilding.  
    • If a UTM interface is bound to an inappropriate Linux interface (e.g. NUL), you will need to delete and recreate it.

    I have been confused by the web interface for initial system build.   Basically, it asks for the interface parameters for each of four interfaces, but it appears to the untrained eye like it is simply asking you for the same information because you made a data entry error.   Also, it asks for network information on four interfaces even if you do not have four interfaces.  The shell interface is much easier for this step.  If you were confused by this point, you may have the same IP configuration on both of your UTM interfaces, and the solution is to fix one of them.   

    Also check that "default gateway" is checked on one of the interfaces, but it sounds like you have not gotten to the point that this would matter yet.

Children
No Data