2.5 Gbps Hardware
-
@iprowell said in 2.5 Gbps Hardware:
https://smile.amazon.com/QNAP-QXG-2G1T-I225-Single-4-Speed-Network/dp/B08FB83C1H/ref=sr_1_3?dchild=1&keywords=qnap+2.5+gbps&qid=1633245287&sr=8-3
That's the card i was referring to. There's also a 2 port and a 4 port (with fan) version of it. Search the forum and there's a fairly long thread about it, but the TL;DR is that the new Netgate 6100 device has 4 i225 ports so the support is lagging a bit behind in the FOSS version but it's coming. I'm planning to buy i225 and deal with it until 2.6. If i was starting fresh I'd just buy the 6100 tbh
-
As far as I know 2.5.2 is only missing a fix for the hardware checksum off-loading. You can just disable that in the GUI anyway.
Steve
-
@stephenw10 so the i225 should be supported out of the box in 2.5.2 and I just need to go in and disable hardware checksum off-loading? Is there a preferred i225 based card? I only need a single port for WAN as I have the x520 working on the LAN side.
-
What about AQC107 based NICs? That is tempting due to 10 Gbps/5 Gbps/2.5 Gbps/1 Gbps/100 Mbps support.
-
There is an Aquantia driver but it's not included in pfSense. You need to load the FreeBSD module but there is now a pkg for that. There have been mixed reports, for example:
https://forum.netgate.com/topic/166522/tx401-support.Steve
-
@stephenw10 thanks for the info. Those are the sort of results I am not very interested in dealing with. I ended up buying a QNAP i225 based card. It went into the system last night, was recognized by 2.5.2, linked up to my modem at 2.5 Gbps, and everything seems to be happy.
-
@iprowell said in 2.5 Gbps Hardware:
QNAP i225 based card. It went into the system last night, was recognized by 2.5.2, linked up to my modem at 2.5 Gbps, and everything seems to be happy.
Just double checking. I'm interested in building a PC with 2.5gb to WAN and LAN. Have a very nice older i5 with 3 pci-e slots that'd be a perfect PFSENSE router. Not doing anything fancy. Just want to build a basic home router with 2.5gb to match my ISP speed.
I have read the threads here, REDDIT, etc., on PFSense and 2.5gbe PCI-E NIC support. And of course have gotten myself confused.
Checking my understanding. As quoted the latest PFSENSE by default supports the Intel based 2.5? The i225 chipset?
-
The igc driver is included in 2.5.2, yes. Because of the release timing it missed a hardware checksum fix that is in 2.6 snapshots but you can just disable hardware checksum offloading.
I have not personally tested anything other than the i225 NIC we use in the 6100 but there are several reports of success such as the one above.
Steve
-
@stephenw10 said in 2.5 Gbps Hardware:
disable hardware checksum offloading.
I'm assuming that's an option I can set via LAN IP interface in the software?
Some reason not to use the .6 snapshot?
-
There's a global setting for it in Sys > Adv > Networking.
Current 2.6 snapshots are pretty stable, I'm aware of any major issues. I have several instances running here. But that is the dev branch, new snapshots may introduce issues. So if you choose to run 2.6 you should not upgrade to every new snapshot if stability is an issue.
Or course the more people who can run a 2.6 test box and report problems the better.
Steve
-
Thanks. While Iām not adverse to playing with new releases, use RMerlins Betaās on my AX86U, two family work from home so it has to be stable.
Itāll be end of week Iām going to have a chance to play.
-
@stephenw10 I checked and I already had hardware checksum offloading disabled. Should I disable that when 2.6 is released? I have the i225 for WAN and a x520-da2 for LAN in the system. Thanks for all the support!
-Ian
-
This post is deleted! -
@iprowell said in 2.5 Gbps Hardware:
Should I disable that when 2.6 is released?
I assume you mean enable it, if you already have it disabled?
Yes, you could enable it in 2.6 but there is almost advantage in doing so. I would leave it disabled.
Steve
-
Figured out bios options, etc., for the install to be recognized as a bootable drive. Worked. Install obviously installed.
Initial configuration did not work. I'm using version 2.6.0 which does not recognize the Intel I-225 NIC's are present. I tested everything with Windows 10 before blasting everything with the PFSENSE install. All worked, 2.5gb cards recognized, etc.
What am I missing? Is there some option I'm supposed to go to the manual screen and enter something to download and install the drivers for the 2.5gb cards?
-
Can you complete the install with other NICs?
If so do that and then at the command line run:
pciconf -lv.You should see the igc NIC listed there. If the driver failed to attach they will be shown as 'none' bit you will be able to see the PCI devices IDs your card is using.
The boot log may also contain errors if/when the driver tries to attach.
Steve
-
@stephenw10 Thanks for getting back to me Was at family dinner. I only have one non 2.5gb card. Wonāt it choke once again thinking it needs to config a WAN and LAN?
It isnāt expensive to pick up another 1gb PCI-e card if needed
Iām booting right now with every LAN port attached.
Not sure but that might have been it. Each LAN port needed something plugged into it.
Edit: Was able to get through configuration, am able to log in via web interface. The Intel 2.5Gbe cards nowhere to be found though. PCICONFIG -LV shows the cards and ānoneā.
-
Had to disable the check sum thing. Once disabled, booted, Intel cards found.
Also I have to keep the 1gb built in LAN active. Its assigned to āOpt 2ā. Might use it to a 1gb NAS directly instead of going through a switch.
I though 2.6 didnāt need that setting disabled?
I might go back to 2.5.2.
-
You only need one recognized NIC to complete the install, just WAN.
Setting checksum disabled would have no effect on the driver attaching to the NICs initially. It only does anything once they are up and linked. Something else is happening there.
Are you saying that if you remove the 1G NIC the others are then not detected again?What is the output of pciconf? What PCI IDs are the devices on that card?
Steve
-
Good morning.
I am using 2.6.0. Updated something this morning. 2.5.2 said the 2.5gb NIC's were 1gb.... went back to 2.6.0.
Yes, if I remove the 1gb NIC from the mix the 2.5gbe ones are no longer "attached" to a driver. It is the built in LAN port of the Dell 390 Minitower.
Consistent behavior is if I don't disable the checksum box, the 2.5gbe cards are not attached or become unattached if they were attached. I am not able to explain it. But that's what happens.
I have it working. So PCICONF is correct now showing attached. Folks using the network so I can't easily run PCICONF at the moment.
I have three 2.5gbe NIC's. One is for the WAN. One goes to the ASUS AX86U 2.5gbe port which is in AP mode. One goes to other home office and 2.5gbe clients. The other office, where' I'm sitting, connected directly to the PFSENSE router, not through the AP. The AP mostly for wireless. Although any 1 gb clients are hanging off its LAN ports.
I'm getting 1300+mbs via Fast.com on PC's in the "other" office. So the connection is more than 1gbs.
I had to bridge the NIC's. I could have created a separate DHCP pool, gateway, etc., I suppose. Was just as easy to bridge the NIC's. Once bridged the DHCP server/DNS stuff worked for all attached clients.
If I do a power down of the PC with PFSENSE, it loses the config for the 2.5gb NIC's and I have to add interfaces again.
I had a problem with the WAN working but I couldn't connect to the internet with any clients. I had to update a couple of firewall rules according to what I found in this forum. Did and was able to connect to WAN with all clients except its just IPV4. I can't get IPV6 going. Searching on that now.
At this moment I'm on, obviously, from the "other" office via 2.5gb. Two family members on in their office including VOIP.
For those two since they connect to company VPN speeds are throttled by their VPN. Me however everything is WAY faster, snappy. The PC based router faster than the Asus AX86U.
Sorry if I'm a bit scattered. I can not play during work hours for my family members. I got up quite early so I could try setting things up.
And of course I'm doing things the hard way.
