Intel NUC BOXD34010WYK2 - Wont find any NIC



  • Installed pfSense on a BOXD34010WYK2, it wont find any NICs.

    How can I solve? Theres a builtin Gigabit network card, and then I added a "Startech USB 3.0 Gigabit Network Adapter" to get NAT functionality.

    USB vid/pid of the USB thingie is:
    VID: 0B95
    PID: 1790
    and identifies itself with the string "AX88179", MAC: 00:24:9B:0A:2A:EA
    Owner: "Action Star Enterprise Co., Ltd." (looks okay)

    The builtin (PCI motherboard integrated) network card is:
    VEN: 8086
    DEV: 1559
    Identifies itself with the string "Intel Corporation Device 1559" and has MAC: EC:A8:6B:FC:81:E1
    Owner: "ELITEGROUP COMPUTER SYSTEMS CO., LTD." (bizarre?)

    Any toughts on this? The MAC on the Intel gigabit card returns "ELITEGROUP COMPUTER SYSTEMS CO., LTD." when searching for the owner Company of MAC…. bizarre?



  • Pfsense doesn't support Intel i210/217 NICs or USB 3.0 ports.



  • any plans on supporting it? Is it possible to manually add support? (adding a module or something like that?)



  • @sebastiannielsen:

    any plans on supporting it? Is it possible to manually add support? (adding a module or something like that?)

    Sort of (will break traffic shaping), and no.  Your best bet is to wait for 2.2 which will be based on FreeBSD 10 instead of 8.3.

    Also, not to be mean about it, but in the future you should try searching before you buy hardware for a project (pfSense or otherwise).  The lack of fully-functional drivers for i210/217 (and i354) as well as the lack of USB 3.0 support have been covered here dozens of times.  I've personally given a blanket recommendation of just staying away from Haswell-based systems at least 6 or 7 times.  You could have saved yourself some time and money (assuming you can't return the gear or repurpose it for something else).

    If you aren't able to return the hardware, your best bet would be to install the free version of vSphere on it and run pfSense inside a VM.  You'll take a performance hit vs. running on bare metal but I'm guessing you don't have enough bandwidth for that to actually matter, most people don't.



  • Notes:

    • i354 / i210 currently working, but then, I'm special.  ;D

    • Haswell is cool.  Rangeley is cool(er).  :-X

    • 2.2 is near alpha (most of what we think is left are GUI issues)  8)

    • USB 3.0?  Why?  :P



  • goozopancho: USB 3.0 support is good for adding network cards, when the hardware aren't able to accept more fixed network cards.

    Jason Litka: I did search but did only find threads about the old (gen 1) NUC and assumed there would be support for the second generation too.
    What Im doing is searching for something similiar that will have roughtly the same functions but still work.
    Im currently looking at IPFire and such other distro.

    Traffic shaping is not that important for me. But about 2.2, any rought estimate of release date?



  • @sebastiannielsen:

    goozopancho: USB 3.0 support is good for adding network cards, when the hardware aren't able to accept more fixed network cards.

    gag me.

    @sebastiannielsen:

    Traffic shaping is not that important for me. But about 2.2, any rought estimate of release date?

    I'm guessing "April".  (We seem to be able to ship a release about 2x/year.)


  • Netgate Administrator

    Try disabling USB3 support in the bios, force it to use a legacy mode. USB NICs are not great though, notoriously problematic. Some people have no issues though. I don't think the AX88179 is supported by the axe(4) driver yet though.

    @Gonzopancho: Any chance we could get the updated igb.ko module, with broken AltQ support, hosted publicly somewhere? It seems like there are many people here who would happily sacrifice altq for working NICs.

    Steve



  • I have the i5 version of this working using VLAN's and virtual box vm of pfSense under Ubuntu.  I knew going into it I was going to have to do some tricky stuff to get it working.  But it's been up for two weeks solid and when the next pfSense release comes out it will be a monster on native hardware with AES-NI.  I may just keep it in the VM tho, because it's already much much faster than I need it to be.



  • @rkuo:

    I have the i5 version of this working using VLAN's and virtual box vm of pfSense under Ubuntu.  I knew going into it I was going to have to do some tricky stuff to get it working.  But it's been up for two weeks solid and when the next pfSense release comes out it will be a monster on native hardware with AES-NI.  I may just keep it in the VM tho, because it's already much much faster than I need it to be.

    Next pfsense will have native hardware with AES support ?

    Can you please shed some details on this, I always seen the CPU handling the AES instructions (50-70%) reduction in cpu load

    so are you suggesting pfsense will also now internally support AES instructions and reduce the cpu workload even more ?



  • AES-NI support is already available it just doesn't work all that well at this point.  I would expect that a move from FreeBSD 8.3 to 10 would result in some improvement there.



  • @Jason:

    AES-NI support is already available it just doesn't work all that well at this point.  I would expect that a move from FreeBSD 8.3 to 10 would result in some improvement there.

    Not really.  If it gets fixed in 10, we'll likely back port it to 8.3.

    one of the big problems is that the guy doing AES-NI for FreeBSD has never tried it with IPsec (or OpenVPN).



  • @gonzopancho:

    @Jason:

    AES-NI support is already available it just doesn't work all that well at this point.  I would expect that a move from FreeBSD 8.3 to 10 would result in some improvement there.

    Not really.  If it gets fixed in 10, we'll likely back port it to 8.3.

    one of the big problems is that the guy doing AES-NI for FreeBSD has never tried it with IPsec (or OpenVPN).

    Seriously?  How the hell do you write code for something and not test it?  I would have sent him a damn server…



  • Even if it is supported or half not working may as well get an AES NI enabled CPU which could cut the usage itself for you.

    Still that does figure in regards to current AES support.

    Does anyone know when 2.2 will release? hopefully it supports all these latest realtek and nics as well as improved or fixed AES support.



  • @Jason:

    @gonzopancho:

    one of the big problems is that the guy doing AES-NI for FreeBSD has never tried it with IPsec (or OpenVPN).

    Seriously?  How the hell do you write code for something and not test it?  I would have sent him a damn server…

    Because he's more focused on storage.

    Hell, I just sent him an Avila board the other day.  It's not like we're not talking.



  • @Fevan:

    Even if it is supported or half not working may as well get an AES NI enabled CPU which could cut the usage itself for you.

    Still that does figure in regards to current AES support.

    Does anyone know when 2.2 will release? hopefully it supports all these latest realtek and nics as well as improved or fixed AES support.

    Realtek is always gonna suck.  It might suck less in 10 (2.2).  The AES-NI support isn't going to get any better unless we MFC a change back from -HEAD (assuming that happens).


Log in to reply