@stephenw10 Nice!! i look later tonight Regards

@ck42 No, not PPPOE. Was just intending to show the relative single-thread performance of a low-end desktop processor vs an embedded one, since that directly affects PPPOE performance. The Geekbench browser will let you compare scores of different processors if you don't already have one to test.

@rcoleman-netgate Thank you but i see that there are still problems, it happens to me too.

@pete Yes it works very well now.

Ah, good result then! Yeah you almost certainly don't need all those rules. Also those are rulesets and you probably don't have all the rules in them loaded because that would be a lot of rules! Steve

@stephenw10 Bingo! I rebooted just to see, and you are correct, it now shows AES-NI as available but inactive. Thanks..

@p-dang That's good news. I didn't see it in their release notes. I happened to come across what I read here on the "can I use my own hardware" https://www.netgate.com/support/frequently-asked-questions-pfsense-plus

I'm on 2100. I'll try to reboot it again. It was pulsing before the upgrade. cheers, M. Edit: it needs one more boot after the upgrade. I have a pulsar again! thanks

Per forum user @w0w, you can download a newer Realtek driver package from freebsd.org per the commands below. I've gone ahead and done this "newer" driver version for my current 2.5.2 install, and it worked well...it is a "test" for me prior to upgrading to 2.6.0 to make sure the drivers worked under load. You still have to edit the /boot.loader.conf.local file after installation, and it will say so on install of the package. (well, it will say to edit /boot/loader.conf, but you may want to do the /boot/loader.conf.local so these settings will persist on doing a future upgrade, per the instructions from @stephenw10 ) fetch -v https://pkg.freebsd.org/FreeBSD:12:amd64/latest/All/realtek-re-kmod-196.04.txz pkg install -f -y realtek-re-kmod-196.04.txz

Ok, that's fair. You won't see 1Gbps OpenVPN through the 7100. Not yet at least. Steve

@stephenw10 So, moved back to the Intel card and I am seeing the results I expect to see now. So, the major issue was that I had a hard gateway defined for the LAN interface, which started asymmetric routing issues. While supported, the bce based card was the second issue. I'm seeing ~230/~110 on a 250/125 circuit, which matches the old firewall almost perfectly, so I think I can put this one to bed. Now, to get BGP and all the other stuff moved to the new firewall, probably gonna setup HA between the old and new and use that to make the switch between the firewalls. Thanks everyone for the input, it got me in the right direction and hopefully it will help others who come across it.

Update on this for anyone with the same issue. What I though was a memory IC wasn't. It's bricked, I don't think there is any way to fix it.

They are 1G, you can see from the PCI device ID: https://pci-ids.ucw.cz/read/PC/8086/15e4 Steve

Interesting. You get different public IPs in different subnets? You can't load-balance like that between WANs that use the same gateway for example. Steve

@stephenw10 thanks for that detail.

Ah, nice find!

@setarcos there’s no need to downgrade the firmware you can use the latest one if you want. Infact I used a newer one 8.4 I think (My card originally shipped with 7.2). It will still work fine with the inbuilt driver. I did however compile the latest driver from Intel’s site, though not necessary.

@stephenw10 that makes perfect sense. Thanks.. The card is an I350-t4-blk (blk for bulk) for those interested

@pete said in NTP / PPS GPS_ntpd - Time Error - PPS Jitter Exceeded: @bingo600 So does that mean the default option should be "unticked"? The kernel PPS is more "picky" , and the NTP PPS ought to be good enoguh for timekeeping. Not getting any PPS Jitter Exceeded log entries on the SureGPS and U-Blox GPS with PPS. I did purchase two more U-Blox modules with old firmware. One of them flashed fine to current firmware and the other said it did not recognize the flash memory. Identifying receiver updater version at 115200 baud. Firmware loader version 5.01 detected. Suitable Multi-ROM image found Check pass: u-blox8 Multi-ROM image -> u-blox8 ROM2.01-receiver No valid FW header found in Flash: 0x00000000. Identifying Flash Flash: ManID=0x68, DevID=0x4013 Flash device not supported Done in 6.4 sec. Statistics: Erases sent: 0 Writes sent: 0 Erase timeouts: 0 Write timeouts: 0 and the other one worked: $GNTXT,01,01,02,ANTSTATUS=OK*25 18:00:44 $GNTXT,01,01,02,u-blox AG - www.u-blox.com*4E 18:00:44 $GNTXT,01,01,02,HW UBX-M8030 00080000*60 18:00:44 $GNTXT,01,01,02,EXT CORE 3.01 (107900)*33 18:00:44 $GNTXT,01,01,02,ROM BASE 2.01 (75331)*19 18:00:44 $GNTXT,01,01,02,FWVER=SPG 3.01*46 18:00:44 $GNTXT,01,01,02,PROTVER=18.00*11 18:00:44 $GNTXT,01,01,02,FIS=0xEF4015 (84524)*67 18:00:44 $GNTXT,01,01,02,GPS;GLO;GAL;BDS*77 18:00:44 $GNTXT,01,01,02,SBAS;IMES;QZSS*49 18:00:44 $GNTXT,01,01,02,GNSS OTP=GPS;GLO*37 18:00:44 $GNTXT,01,01,02,LLC=FFFFFFFF-FFFFFFED-FFFFFFFF-FFFFFFFF-FFFFFF69*23 18:00:44 $GNTXT,01,01,02,ANTSUPERV=AC SD PDoS SR*3E 18:00:44 $GNTXT,01,01,02,ANTSTATUS=OK*25 18:00:44 $GNTXT,01,01,02,PF=3FF*4B Buying those can be a "lottery" I like the "Older" LEA-5T , as it's designed for timing (The T at the end), and at a price i can afford (will pay) https://www.ebay.com/itm/254603722675 LEA-6T or 8T are nicer but a lot pricier , and the 5T is good enough for me. Beware , the Antenna plug is SMB M (you'd want a SMB F to SMA F adapter) https://www.ebay.com/itm/202466110634 And the connector plug is 2mm , but easy enough to solder on. If you don't have any 2mm plugs & ribbon cable. You can "Sneak" 2.54mm Dupont wires into the plug , but it's a tight fit. /Bingo

@stephenw10 Thanks Steve, I was planing to use one for wired subnet and the other for wireless subnet and the onboard for external since it’s 1G the onboard is capable of 2.5G. Joe