Zotac ZBOX CI323 nano

cristi_gh

@cinnamon:

hi
sorry haven't checked the forums in a while
for the guy who asked for it

http://s000.tinyupload.com/?file_id=67950169242632494971

that's the compiled version i use on my pfSense 2.3.2

compiled on FreeBSD 10.3

This seems to have worked. I'll attach it here in case the link goes down.
Also I'd love v1.93. As I understand the one I attached is v1.92

if_re.ko.txt

pf3000

This is v1.93 that I tried briefly on 2.4 beta (freebsd 11) before finding out that I couldn't receive IPv6 from the WAN.

if_re.zip

morgejgmail

@cinnamon:

Hey sorry, just got my main desktop up and running. I had some trouble after draining my watercooling loop, had to go out and buy a new block. then my pumps reservour cracked. etc.. lol

1. Install Kernel FreeBSD 10.3 with kernel sources.
1. Get kernel driver 1.91 from realtek site. You don't need the patch for driver, only if you're using FreeBSD 11+
2. Modify /usr/src/sys/amd64/conf/GENERIC and delete line "device re" - so if_re no longer be included in kernel itself - module will be build anyway.
3. Edit /boot/loader.conf adding line if_re_load="YES", so external module will be loaded.
4. Go to /usr/src and run "make buildkernel KERNCONF=GENERIC && make installkernel KERNCONF=GENERIC"
5. Reboot with new kernel. System should boot with open-source driver as module. kldstat will show if_re in list of modules.
6. Put Realtek's if_re.c and if_rereg.h into /usr/src/sys/dev/re
7. Build driver (cd /usr/src/sys/modules/re && make clean && make)
8. Backup /boot/kernel/if_re.ko, then cp /usr/src/sys/modules/re/if_re.ko /boot/kernel/if_re.ko && chmod 0555 /boot/kernel/if_re.ko && chown root:wheel /boot/kernel/if_re.ko
9. Reboot

Now i wasn't sure how to upload files to internet using lynx or fetch so i installed xorg server and kde on vm FreeBSD. This took a while and i had some issues with timeouts etc.
Basicly i uploaded new compiled if_re.ko to some small file hosting sites, used a tinyurl to shorten it with direct link

SSH into pfSense and used fetch to download it into /boot/kernel/
chmod 0555 /boot/kernel/if_re.ko && chown root:wheel /boot/kernel/if_re.ko

edit /boot/loader.conf in pfSense. Can do through web browser or through ssh client with vi
add line if_re_load="YES"

That should be it. Reboot and your 1.92 should be loaded. If you want to unload it just put # infront of if_re_load="YES" in /boot/loader.conf
If you're having issues compiling or uploading to web/usb stick i will be happy to upload it for you or send you somehow a already compiled one

I downloaded the compiled module from a few posts down the thread and installed with these instructions.

In my limited testing, this HAS fixed my issues with the CI323 nic's when downloading large files across my FIOS 300/300 service.

THANK YOU!

ermax

1.93 works fine on 2.4-RC. I have IPv6 working on mine too. Throughput still isn't consistent. It maxes out my 100/100 fiber but it seems to randomly hang on speed tests here and there.

I posted directions on compiling and installing along with all the loader options that are needed in this post here:
https://forum.pfsense.org/index.php?topic=103841.msg739039#msg739039

TheNarc

I run a CI323 nano and just updated to 2.4.0-RELEASE. As part of that, I grabbed Realtek's latest driver (v1.94 released September 15, 2017) from here: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=5&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

I then grabbed a ready-to-run FreeBSD 11.1 VM image here: https://download.freebsd.org/ftp/releases/VM-IMAGES/11.1-RELEASE/amd64/Latest/FreeBSD-11.1-RELEASE-amd64.vmdk.xz and fired it up in Virtualbox. The compilation went right through with no patching or modifications required. All I had to do then was put the compiled if_re.ko module in /boot/kernel/ and add the line if_re_load="YES" to /boot/loader.conf.local and everything seems to be happy, at least as evidenced by if_re.ko being listed in the output from kldstat and no stability issues so far.

I've added the compiled module in case anyone else wants it. The SHA512 of the if_re.ko file (not the ZIP file) is:
00f0278b396844e2735d10b57780ccf31a085d9a52e9e192fb758a904172fa4a9c27da297f6722f69906d9d62f4168ea3babfc8a27849f37a667bc0323c1841b

if_re.ko.zip

Areomayo

@TheNarc:

I run a CI323 nano and just updated to 2.4.0-RELEASE. As part of that, I grabbed Realtek's latest driver (v1.94 released September 15, 2017) from here: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=5&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

I then grabbed a ready-to-run FreeBSD 11.1 VM image here: https://download.freebsd.org/ftp/releases/VM-IMAGES/11.1-RELEASE/amd64/Latest/FreeBSD-11.1-RELEASE-amd64.vmdk.xz and fired it up in Virtualbox. The compilation went right through with no patching or modifications required. All I had to do then was put the compiled if_re.ko module in /boot/kernel/ and add the line if_re_load="YES" to /boot/loader.conf.local and everything seems to be happy, at least as evidenced by if_re.ko being listed in the output from kldstat and no stability issues so far.

I've added the compiled module in case anyone else wants it. The SHA512 of the if_re.ko file (not the ZIP file) is:
00f0278b396844e2735d10b57780ccf31a085d9a52e9e192fb758a904172fa4a9c27da297f6722f69906d9d62f4168ea3babfc8a27849f37a667bc0323c1841b

I can confirm this works, thank you, guess i better start learning how to compile these realtek drivers since my old if_re.ko for the previous version of pfsense 2.3 didnt work anymore for pfsense 2.4 :-\

krackpot

Has everyone done the upgrade from 2.3.x to 2.4? Or is it better to start from scratch and enable ZFS?

TheNarc

I ran the upgrade, which completed fine. However, I also run the pfBlockerNG package and there have been reports that it will cause lockups unless you update to ZFS. I haven't had this happen (yet) on my system so I haven't read up on it too much, but here's the thread in case you're interested: https://forum.pfsense.org/index.php?topic=137103.0

messerchmidt

is 2.4 working on this box properly?

TheNarc

It seems to be working fine for me, at least using Realtek's v1.94 driver. Of course, since 2.4.0 has been out for less than a week it's impossible to say whether it's completely stable yet.

messerchmidt

someone needs to make a youtube video of how-to do this…lol

ok i think i got it. seems to be ok

anyone else having success?

blueduckdock

Thanks to TheNarc- got the module and loaded it up.
So far, so good but it's only been a day so..

Edit- so…given that the normal FreeBSD drivers for Realtek NICs are not up to par, is there any reason we can't load up a kernel module in pfSense by default (question to the devs)? Is there some kind of issue loading up realtek drivers in the module due to copyright, openness, etc.? Figured you could just grab one of the latest, have beta testers test it, then keep it for the length of the FreeBSD base (ie. same driver/kernel module all the way through FreeBSD11, then upgrade the driver when it goes to 12, etc.)

silviu

Is this still ok to use on 2.4.1 ? Should be since we are still FreeBSD 11. Or do I need to recompile?

blueduckdock

@silviu:

Is this still ok to use on 2.4.1 ? Should be since we are still FreeBSD 11. Or do I need to recompile?

No issues here with that 1.94 module linked above.

1.94 seems to help Zotac CI327 too in terms of gaining stability and network performance when running pfsense 2.4.1.

So thanks to all those who figured out and provided the solution and especially for the binary.

I wonder if it would also benefit 2.3.x (FreeBSD 10.3).
Anyone has used it with 2.3.x ?

DvdW

Thanks to (among others) Ermax, Cinnamon, TheNarc and a little Google this noob was able to almost max out my 400/40 line on the C1327 nano with 2.4.1-RELEASE. Next stop: learn to speak FreeBSD… :o

MuadDib81

Hi!

I have also the ZBOX CI323 nano and the wireless is not working with pfsense 2.4.1. I added the two lines to /boot/loader.conf:


...
legal.intel_iwi.license_ack=1
legal.intel_ipw.license_ack=1

The output from pciconf -lv:


...
none2@pci0:4:0:0:       class=0x028000 card=0x80708086 chip=0x08b38086 rev=0x83 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = 'Wireless 3160'
    class      = network

I assume the missing subclass (Wireless) is responsible for not showing up in the wireless section. Is there any possibility to make it working though?

My CI327's wifi card was not supported by FreeBSD 10.3 or 11.1, but in an old laptop I found a wifi card that agreed with FreeBSD, so I swapped them.
The laptop (running linux) figured out the proper driver in a heartbeat so the new card didn't go to waste. On the pfsense box, the legacy wifi card supports G only, but better than nothing.
You might want to try something similar or even buy a suitable wifi card for your pfsense box. Wifi troubleshooting is way too painful especially on a FreeBSD system.

bgbird03

@TheNarc:

I run a CI323 nano and just updated to 2.4.0-RELEASE. As part of that, I grabbed Realtek's latest driver (v1.94 released September 15, 2017) from here: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=5&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

I then grabbed a ready-to-run FreeBSD 11.1 VM image here: https://download.freebsd.org/ftp/releases/VM-IMAGES/11.1-RELEASE/amd64/Latest/FreeBSD-11.1-RELEASE-amd64.vmdk.xz and fired it up in Virtualbox. The compilation went right through with no patching or modifications required. All I had to do then was put the compiled if_re.ko module in /boot/kernel/ and add the line if_re_load="YES" to /boot/loader.conf.local and everything seems to be happy, at least as evidenced by if_re.ko being listed in the output from kldstat and no stability issues so far.

I've added the compiled module in case anyone else wants it. The SHA512 of the if_re.ko file (not the ZIP file) is:
00f0278b396844e2735d10b57780ccf31a085d9a52e9e192fb758a904172fa4a9c27da297f6722f69906d9d62f4168ea3babfc8a27849f37a667bc0323c1841b

My apologies for this very amateur hour question, but how do I do this with my Zotac box? I've got version 2.4.1 running great, but obviously I'm getting the "re0:watchdog timeout" with the drivers that came with the box. Updating the drivers seems to be the best chance (the interface dies every few hours…). I tried uploading the files from both the GUI and the command prompt during loading and can't figure it out.

The very, very gracious if_re.ko file that you provided is unzipped and on a USB drive, but I can't figure out how to move that to the /boot/kernel folder; I've been trying the "mount /dev/da0s1a /mnt" command from the 'execute shell command' in the GUI but...no joy. I can add the text line in /boot/loader.conf.local no problem using the Diagnostics/Edit File in the GUI.

Thanks for your help! Hopefully this will fix this Realtek issue once and for all for me.

EDIT: well regrettably wasn't able to get anyone here to help me out with the issue, but another forum suggested using WinSCP to get the file over to the box; that worked perfectly and was very intuitive (for even me) to use. So if anybody is as clueless as I am, that tool is a great way/GUI to connect to your pfSense box and move files around between Windows & Unix/FreeBSD/pfSense.

bgbird03

@MuadDib81:

Hi!

I have also the ZBOX CI323 nano and the wireless is not working with pfsense 2.4.1. I added the two lines to /boot/loader.conf:
...
legal.intel_iwi.license_ack=1
legal.intel_ipw.license_ack=1
The output from pciconf -lv:
...
none2@pci0:4:0:0:       class=0x028000 card=0x80708086 chip=0x08b38086 rev=0x83 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = 'Wireless 3160'
    class      = network
I assume the missing subclass (Wireless) is responsible for not showing up in the wireless section. Is there any possibility to make it working though?

I just ended up purchasing a cheap ($20) wireless D-Link access point for my home as a "workaround". It is great. I have the WAN as re0 and LAN as re1 going to the wireless device configured with a static IP. The pfSense does the routing/DHCP…and the D-Link is just an access point. You might want to consider a solution like that rather than using an internal NIC. Its tough to find anybody on this forum that supports using internal NICs as your home WAP.