Is there a way to get the plus installer?
-
@yuryk No... not that i am aware of.
-
@yuryk As it stands now there are no images available for 23.01. However, there seems to be some initial support for i226 in CE 2.6.
See this post.. https://forum.netgate.com/post/1075823
Might be best to give the whole thread a read.. there are some other workable suggestions there as well.
-
I tried both, 2.6 and 2.7 - no dice.
-
@yuryk You could use the CE 2.7.0 DEV snapshot which supports i226, but there's a catch if you want to upgrade to Plus; when selecting the Upgrade branch, it wants to migrate to 22.01 which has no i226 support. So I assume you will have no more network connection once its installed. If it would offer 22.05 instead of 22.01 there's a chance it will work with an i226 (its reported to work on the N5105 fanless system I have). So I have not discovered a path to upgrade to Plus with an Intel 226 NIC.
I have an old 100Mb USB NIC I could possibly use but I tried it and while it seems to be recognized by pfSense I couldn't figure out how to successfully get it to replace the current WAN interface. I haven't setup all of my vlans and rules yet, so maybe I'll try resetting to defaults and go through the process from scratch with the USB NIC as WAN, but then I'd be back to trying to switch from the USB NIC to i226 interface.
I'm a pfSense noob so maybe someone will offer a bright idea. Might just have to stay on 2.7.0 DEV until there's a new option for upgrading. -
@yuryk 2.7.0 development didn't work with your i226 NIC? What system do you have? 2.7.0 works with my Topton Model-A N5105 with 4x i226 NICs.
-
I have Topton 12th Gen Firewall Router Elkhart Lake Celeron J6413 J6412 6x Intel i226-V 2500Mbps Nics Fanless Mini Router PC OPNsense Proxmox
https://a.aliexpress.com/_mqpqbTCIn fact, yesterday my old ProtectCli went hard down during an upgrade, so I tried CE 2.7 latest build on the new box, but the installer hangs after detecting the NICs.
I had to do an emergency swap to opnsense to get things working. Now will try to rebuild protectcli box and then will make another run on installing CE 2.7. The nics are in fact 226-V which should be supported.
-
@yuryk you can try running pciconf -l in a shell to see the NIC device IDs. Mine are 0x125C.
-
igc0@pci0:1:0:0: class=0x020000 rev=0x04 hdr=0x00 vendor=0x8086 device=0x125c subvendor=0x8086 subdevice=0x0000 igc1@pci0:2:0:0: class=0x020000 rev=0x04 hdr=0x00 vendor=0x8086 device=0x125c subvendor=0x8086 subdevice=0x0000 igc2@pci0:3:0:0: class=0x020000 rev=0x04 hdr=0x00 vendor=0x8086 device=0x125c subvendor=0x8086 subdevice=0x0000 igc3@pci0:4:0:0: class=0x020000 rev=0x04 hdr=0x00 vendor=0x8086 device=0x125c subvendor=0x8086 subdevice=0x0000 igc4@pci0:5:0:0: class=0x020000 rev=0x04 hdr=0x00 vendor=0x8086 device=0x125c subvendor=0x8086 subdevice=0x0000 igc5@pci0:6:0:0: class=0x020000 rev=0x04 hdr=0x00 vendor=0x8086 device=0x125c subvendor=0x8086 subdevice=0x0000
Seems that I have 0x125c as well.
-
@yuryk Dang, it all looks correct!
-
What error do you see when you try to use that?
0x125c should be supported as you say:
https://github.com/pfsense/FreeBSD-src/blob/devel-main/sys/dev/igc/igc_hw.h#L29It could be the hardware revision or perhaps the PHY the driver is objecting to.
The igc driver in 2.7 is identical to that in 23.01 from what I can see.
Steve