Is it actually losing link? What do you see logged when that happens?

@dugeem It would be interesting to see how much PPPoE performance has improved with the new if_pppoe driver included in 2.8 CE and Plus 25.07. Previously with Netgraph/mpd5 it was limited to ~ 400 Mbps on the APU2.

Given that it's already in Intel's branch I'd expect it relatively soon. It's not like igc for example where there was no driver. There is work on going to include it and it looks like it's imminent: https://reviews.freebsd.org/D50067

Cloning the SSD should work, yes. But I would also just install clean and restore the config.

@stephenw10 No Sir, i have not tested it yet. Just finished building my M570, will test it on the M370 in the near future.

No, just ordered from Amazon.

@johnytb said in Gtek 2.5G (Intel I225 Controller) PCI-E x1 Network Card not recognized by the pfsense: can you explain to me what exactly is this interface that you show here ? That's pfSense most important interface The one that works when even all your NICs don't work. Its called : the console, which could be a serial connection, or, if you have VGA/HDMI build in, it could be that and a (USB) keyboard. Or : If the LAN NIC is working, you 'ssh' into your pfSense using a SSH client like putty or classic 'ssh'. Keep in mind : what happens when you have a disk drive issue ? => pfSense can't boot. => Network interfaces will all by down ... You the the console (serial or VG/HDMI/Keyboard) access. For command line commands I use the ... command line = console (or SSH) access.

For anyone interested in the exciting conclusions... it worked fine in the 16x slot for 2 weeks and is still in there now I put an I340-T4 in the 1x slot at the same time and left that running and that has been perfectly fine as well It seems to be an incompatibility between the 1x slot and the I350 specifically but i'm not sure why. In either case, the issue seems to be resolved It may be something specific to AM5 and the I350 in the 1x, or just the I350 and the 1x alone but if anyone else for some reason tries the same, at least you know what symptoms manifest and what the cause was Thanks again for those that helped and commented

Probably just that then. But you should see the set options and capabilities for those NICs like: [2.8.0-RELEASE][admin@t70.stevew.lan]/root: ifconfig -vm igb0 igb0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500 description: WAN options=4e100bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWFILTER,RXCSUM_IPV6,TXCSUM_IPV6,HWSTATS,MEXTPG> capabilities=4f53fbb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_UCAST,WOL_MCAST,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,NETMAP,RXCSUM_IPV6,TXCSUM_IPV6,HWSTATS,MEXTPG> So there you can see the NIC is both checksum offload and TSO capable but only checksum is enabled.

@stephenw10 I want to use 10GBIT DAC inside my rack and also directly attach to my ISPs Fiber. It'd be the perfect successor for the SG6100 with the SFP+ Addon installed.

Hmm, interesting. Hard to see how that driver could ever have made in difference when passed through like that. If you don't pass it through you could use the modified driver in Proxmox and then present it to pfSense as a virtual NIC until we get the patched driver in pfSense. Except you're saying the modified driver no longer loads in Proxmox....

@stephenw10 ok i sure will do thanks

So initially it booted and then failed after 48hrs and now doesn't boot at all? Do you have the actual boot logs showing the errors?

@jwt that is great news, thank you!

@bttech56 Hey, this was the only single tim IDs changed. Though I did move from LTE to optical cable, with terminal-only unit, so at the moment it is via ethernet port. Now I have about 3 months without reboot. No root cause identified.

@planedrop yep its an older thread, i arrived here through googling the issue i was having and this was one of the top results. whilst it is a virtualised environment, the commonality between them exists and my setup is largely indistinguishable from a non-virtualised setup. i'm using dedicated cores, binding IRQs to those cores, isolating them, using hardware passthrough. theres a variety of other threads who have had similar experiences with SR-IOV too. just to add this was with the default MTU of 1500 and rx / tx descriptors of 4k on the linux side improving this on the freebsd side (by placing into the loader.conf.local) #enable iflib overrides for ixv interfaces dev.ixv.0.iflib.override_qs_enable="1" dev.ixv.1.iflib.override_qs_enable="1" # Set 4K descriptors dev.ixv.0.iflib.override_nrxds="4096" dev.ixv.0.iflib.override_ntxds="4096" dev.ixv.1.iflib.override_nrxds="4096" dev.ixv.1.iflib.override_ntxds="4096" # Enable iflib overrides for ix interface dev.ix.0.iflib.override_qs_enable="1" # Set 4K descriptors for ix interface dev.ix.0.iflib.override_nrxds="4096" dev.ix.0.iflib.override_ntxds="4096" seems to have helped out with regard to rx_no_dma_resources issues, you can generally check if you are having those same issues by looking at sysctl dev.ix | grep -E "(r_drops|r_stalls|r_restarts|no_desc_avail|credits|override_n[rt]xds)"

@jra9511 where does it fail in the process.. What error does it present? I just created a new account and didn't have any issues. [image: 1750773199015-creation.jpg]

I think I figured it out my mistake to over commit CPU in a VM . Now seens to not get stuck at 100%