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

Intel I219-LM network interface card not detected

Hi,

I see this has been asked before and based on the favourable answer given by @cryptochrome, almost two years ago - to the day, I went ahead and bought a SuperMicro X11SSV-LVDS motherboard, confident that I would not have any NIC issues, however UTM 9.509-3 is not detecting the I219-LM NIC. 

The motherboard comes with two onboard nics: "Intel Ethernet Controller I210-AT and Intel Ethernet Connection I219-LM Phy with AMT". 

I am assuming the "-LM Phy with AMT" is not causing the problem.

@cryptochrome mentions the supported kernel version as 3.19.x, however, I notice UTM 9.509-3 is running 3.12.74-0:


    # uname -r

  3.12.74-0.283050698.g2cded84.rb2-smp64


 

or


    # cat /proc/version
   Linux version 3.12.74-0.283050698.g2cded84.rb2-smp64 (abuild@axgbuild) (gcc version 4.3.4 [gcc-4_3-branch revision 152973] (SUSE Linux) ) #1 SMP Mon Feb 5 12:05:55 UTC 2018


 

Has there been a regression in the kernel version? However, two posts further down, @williamWarren states it is supported in kernel 3.12.x

I've built the appliance in a small ITX case and there is no room for a PCI card and I don't really want to buy another, larger case to fit a PCI NIC.

 

I've seen another post that states both NICs have to be the same. Is this true?

 

All said and done, is there anything I can do to get the I219 NIC to work without buying more hardware?

 

Many thanks

 

W.



This thread was automatically locked due to age.
Parents
  • Hi Adrian and welcome to the UTM Community!

    I don't know if there's a newer one, but the Hardware Compatibility list pdf from 2016 does not list the I219.

    According to a post in the Unofficial HCL, it still wasn't supported a year ago.

    The two cards don't need to be identical, but you do need to reload from ISO after you add a different device as the only drivers loaded are the ones for the devices found at the time of installation.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • Thank you  for your reply. I wonder how  got it working. I'm cross with myself that I didn't dig deeper.

    I did see a post eluding to the fact that Sophos consider the L219 NIC a consumer product. Interesting, considering I've seen SuperMicro Xeon boards with the same NIC.

    So where do I go from here. Is it possible to load in the drivers? I've seen various posts, some say it's possible, some say not, some advise against it as this is a security appliance and has to be compiled in with the compile tools that Sophos have. Either way, I haven't found a noob step-by-step on how one might add ones own drivers.

    Is there any scope in trying to pay Sophos to add these drivers. If they haven't added it since 2016, I don't see they're going to do it now, unless they have an incentive.

    I suppose I can use my build for something else and go for something else like the Fortinet 60E which will mitigate issues with vendor / hardware support.

     

    Thanks again.

     

    W.

  • I don't recall hearing of anyone adding an unsupported driver, so I think it's either add a NIC or shift to a different tool.  You might check out the XG.  It's a different approach than the UTM, but is probably a great tool if you're starting from scratch.  That said, I don't know if it supports the I219.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • Thanks  

    As far as I can tell, it's the same issue with XG. The I219 is considered consumer grade.

    I have had a thought though, what stops me installing XG or UTM on top of a hypervisor such as ESX?  I have installed UTM on ESX before, so I know UTM supports ESX drivers and I know I can get the I219 driver to work with ESXi 6.5

    The reason for the small ITX form factor is so that it can be physically located next to my router and I believe this would solve the problem.

    Thanks

     

    W. 

  • Great idea, Adrian!  I guess these little boxes can handle ESXi - that's an obvious answer.  I don't work with anything other than Sophos, HP and VMs on big boxes, so I hadn't thought of that.

    Install on Suse Enterprise 11 64-bit with VMXNET3 adaptors.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • Great idea, Adrian!  I guess these little boxes can handle ESXi - that's an obvious answer.  I don't work with anything other than Sophos, HP and VMs on big boxes, so I hadn't thought of that.

    Install on Suse Enterprise 11 64-bit with VMXNET3 adaptors.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
No Data