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

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 10 replies
  • Subscribers 39 subscribers
  • Views 2658 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

No connection intel x520-DA2 (82599ES) on sophos home

Oliver Zoisl

Hello I struggle a little bit atm. I had sophos home virtualized on something intel N with 4x2.5G running proxmox. The thing had no legacy BIOS (sadly) so this was my only option.

Then I got a SG230 cheap and I installed a intel 10G nic (x520-DA2, 82599ES). Sophos recognized it without any problem. I loaded the old config and adapted everything. I configured a LAG with both ports and a bridge with the original LAN port.

Time to plug everything in and.. nothing.. the link LEDs are blinking on the nic and the unifi aggregation switch, but in the sophos UI it shows no cable connected. I've removed the LAG and bridge to try singe port but it's not working.

I also tried with a RJ45 module in the SFP+ port.. at first sight it's also not working but I had no time to further test it. 

Anyone an idea?



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

    Well I've no idea what's going on but it somehow worked fine for a bit after a restart and suddenly stopped working. It also showed ist perfectly fine in the UI.

    [ 8.095743] ixgbevf: Copyright (c) 2009 - 2015 Intel Corporation.
    [ 8.869057] ixgbe_nm 0000:01:00.0 Port9: renamed from eth8
    [ 8.893026] ixgbe_nm 0000:01:00.1 Port10: renamed from eth9
    [ 32.785811] ixgbe_nm 0000:01:00.1: registered PHC device on Port10
    [ 32.914235] ixgbe_nm 0000:01:00.0: registered PHC device on Port9
    [ 32.964007] ixgbe_nm 0000:01:00.1 Port10: detected SFP+: 4
    [ 33.088010] ixgbe_nm 0000:01:00.0 Port9: detected SFP+: 3
    [ 33.112037] ixgbe_nm 0000:01:00.1 Port10: NIC Link is Up 10 Gbps, Flow Control: RX/TX
    [ 33.232020] ixgbe_nm 0000:01:00.0 Port9: NIC Link is Up 10 Gbps, Flow Control: RX/TX
    [ 358.034890] ixgbe_nm 0000:01:00.0: Adapter removed
    [ 359.918958] ixgbe_nm 0000:01:00.1: Adapter removed
    [ 360.032057] ixgbe_nm 0000:01:00.0 Port9: MNG_VETO bit detected.
    [ 360.032130] ixgbe_nm 0000:01:00.0 Port9: speed changed to 0 for port Port9
    [ 361.920042] ixgbe_nm 0000:01:00.1 Port10: MNG_VETO bit detected.
    [ 361.920120] ixgbe_nm 0000:01:00.1 Port10: speed changed to 0 for port Port10

Reply
  • 0

    Well I've no idea what's going on but it somehow worked fine for a bit after a restart and suddenly stopped working. It also showed ist perfectly fine in the UI.

    [ 8.095743] ixgbevf: Copyright (c) 2009 - 2015 Intel Corporation.
    [ 8.869057] ixgbe_nm 0000:01:00.0 Port9: renamed from eth8
    [ 8.893026] ixgbe_nm 0000:01:00.1 Port10: renamed from eth9
    [ 32.785811] ixgbe_nm 0000:01:00.1: registered PHC device on Port10
    [ 32.914235] ixgbe_nm 0000:01:00.0: registered PHC device on Port9
    [ 32.964007] ixgbe_nm 0000:01:00.1 Port10: detected SFP+: 4
    [ 33.088010] ixgbe_nm 0000:01:00.0 Port9: detected SFP+: 3
    [ 33.112037] ixgbe_nm 0000:01:00.1 Port10: NIC Link is Up 10 Gbps, Flow Control: RX/TX
    [ 33.232020] ixgbe_nm 0000:01:00.0 Port9: NIC Link is Up 10 Gbps, Flow Control: RX/TX
    [ 358.034890] ixgbe_nm 0000:01:00.0: Adapter removed
    [ 359.918958] ixgbe_nm 0000:01:00.1: Adapter removed
    [ 360.032057] ixgbe_nm 0000:01:00.0 Port9: MNG_VETO bit detected.
    [ 360.032130] ixgbe_nm 0000:01:00.0 Port9: speed changed to 0 for port Port9
    [ 361.920042] ixgbe_nm 0000:01:00.1 Port10: MNG_VETO bit detected.
    [ 361.920120] ixgbe_nm 0000:01:00.1 Port10: speed changed to 0 for port Port10

Children
No Data
Unfiltered HTML