@bigbird007 said in Pfsense performance:

wait for it to fail, see if I can work it out

Finding the issue is actually easy with the FreeRadius package - process.

First : stop the FreeRaduisx instance in the GUI, if it is running.
Then, use the console or better SSH access, and enter god-mode : option 8.

Type the magic command :

radiusd -X

A boatload of log line scroll over your screen.
After an initial startup phase, thing will calm down on your screen.
You can leave this screen open, and have break, day of, some sort of delay.
When the process dies, one of the last lines will probably printed in red. That is your issue.
The question was : what is the issue.
The answer will be : read the red line.

@mykl With the Kingston UV500 series, I had no problem (for NGFW)

perfect ☺

You see, it's already clear what's wrong...

You can do two things:

you experiment, but it can cost useless money, if it doesn't work and you buy one this (the compatibility of the I350 is legendary):
https://www.dell.com/en-au/work/shop/dell-intel-ethernet-i350-t-quad-port-1-gigabit-server-adapter-low-profile/apd/540-11333/networking

or

https://www.bargainhardware.co.uk/intel-i350-t4-quad-port-rj45-1gbps-low-profile-pcie-x4-nic

-or you go that way, which I have already experienced and you use a Broadcom T4 NIC (bce4), I know for sure it works:

https://www.bargainhardware.co.uk/broadcom-bcm5709-quad-port-rj45-1gbps-low-profile-pcie-x4-nic
(we use it without any problems)

I'm sure with such a strong CPU, the (bce4) driver has no disadvantages when running pfSense

@Harrye It really depends on what NIC you're using ... also, may I suggest to hide your Netgate ID as that's confidential info.

Will do, thanks!

Doesn't look like free is included, but you can try Diagnostics/System Activity.

Nearly all traffic is https these days. This implies that the 'router' - all routers - on the data path can not 'see' the traffic payload.
pfSense can not snip out parts and bits.
pfSense sees source and destination IP, ports, some packet flags, a packet size and number, and scrambled data. That's it.

You could have added your own initial advice ; re install Windows ^^

Btw : routers can get hacked, of course. Not because the hacker wants to see what the users on the routers LAN(s) are doing. They have other interests.

@Gertjan said in Ethernet devices being assigned WI-Fi Range IP addresses - How do I keep the subnets separate?:

Normally, when you are at home, and wired up (cable) you shut down ( there is a key on the keyboard for this ) the Wifi.

I have never done that. I just rely on the metric. Also, with Linux, unlike Windows, the WiFi address is still reachable via the Ethernet port. So, if I ping the WiFi address, while connected with Ethernet, the ping goes in via Ethernet. I have verified that with Wireshark.

Oke I noted it

fix: https://redmine.pfsense.org/issues/10625

Bump.

Got it ... it's dmesg | grep igb0

[2.5.0-DEVELOPMENT][admin@NollipfSense.nollipfsense.lan]/root: dmesg | grep igb0
igb0: <Intel(R) PRO/1000 PCI-Express Network Driver> mem 0xa1000000-0xa10fffff,0xa1104000-0xa1107fff at device 0.0 on pci7
igb0: Using 1024 TX descriptors and 1024 RX descriptors
igb0: Using 4 RX queues 4 TX queues
igb0: Using MSI-X interrupts with 5 vectors
igb0: Ethernet address: a0:36:9f:09:b0:3c
igb0: netmap queues/slots: TX 4/1024, RX 4/1024
igb0: link state changed to UP
igb0: promiscuous mode enabled
igb0: link state changed to DOWN
igb0: link state changed to UP
igb0: link state changed to DOWN
igb0: link state changed to UP
igb0: link state changed to DOWN
igb0: link state changed to UP
igb0: link state changed to DOWN
igb0: promiscuous mode disabled
igb0: link state changed to UP
igb0: <Intel(R) PRO/1000 PCI-Express Network Driver> mem 0xa1000000-0xa10fffff,0xa1104000-0xa1107fff at device 0.0 on pci7
igb0: Using 1024 TX descriptors and 1024 RX descriptors
igb0: Using 4 RX queues 4 TX queues
igb0: Using MSI-X interrupts with 5 vectors
igb0: Ethernet address: a0:36:9f:09:b0:3c
igb0: netmap queues/slots: TX 4/1024, RX 4/1024
igb0: link state changed to UP
igb0: promiscuous mode enabled
igb0: link state changed to DOWN
igb0: link state changed to UP
igb0: link state changed to DOWN
igb0: link state changed to UP
igb0: link state changed to DOWN
igb0: link state changed to UP
igb0: promiscuous mode disabled
igb0: promiscuous mode enabled
igb0: promiscuous mode disabled
igb0: link state changed to DOWN
igb0: link state changed to UP
igb0: <Intel(R) PRO/1000 PCI-Express Network Driver> mem 0xa1000000-0xa10fffff,0xa1104000-0xa1107fff at device 0.0 on pci7

@zsing82 said in Script not executing... command not found:

Debian boxes. BSD is a whole different animal

Actually, for the most part Linux and BSD are similar, in that they're both Unix variations. However, there are some differences, but nowhere near the difference between either and the Windows shell commands.

textdump.tar(1).0

might backup my config and reload it on a clean install. still crashing 😵

@fabiolanza I contacted the seller/company that confirmed the chipset was Intel made. I am waiting for them to list more so I can purchase.