In the end I went with Dell Wyse 5070 Extended. I also put Dell 09YD6K 4-Port 1 Gbps Ethernet NIC inside. That is Intel i350-T4 card. I had problems with this card cause when I put it inside, dell was not posting anymore. It signaled memory problem. So if anyone has similar problem with i350 card, solution is to block pins B5 and B6 with electric tape. After that it posted and everything works ok. Solution was found here: Modding a Dell Perc 6 / Dell H310 / Dell H710 (other LSI 1078 or 9223-8i based) SAS Raidcontroller. In comments on that blog post, someone mentioned i350 NIC.

Mmm, well I would definitely try booting verbose to check the ACPI errors if you're seeing this as I said previously. There's a good chance the BIOS is passing some values to FreeBSD that Windows never sees because most manufacturers don't care about anything else. Steve

Ah, yes. Well it might work. Unfortunately we have no way test so I cannot be sure. There have been a few threads about it here but I don't think anyone have actually tested it yet. Steve

@cybermancer Hy cybermancer i'm in this case to. Could you explain your operating mode for the script?

@stephenw10 said in iwifw() module loading show ERROR in dmesg, if it needed on server ?: It's already not loading them. You can see they are not listed in your kldstat output. Adding those lines to loader.conf won't change anything. They are loader variables you have to add them there, adding them as sysctls does nothing. You are only seeing those lines at all because you're booting verbose. Thank You Steve (and all others here!) for patience and help with this case. Have a nice day!

The i350 NIC has better potential throughput since it presents 4 queues per NIC and the i211 only 2. However the difference is marginal. I would expect either to be able to move traffic at Gigabit line rate given a sufficient CPU. Steve

@stephenw10 Thanks, i will check there.

@jimp said in How to set different certain screen resolution on FreeBSD and pfSense boot for VGA and COM Console output ?: The monitor size doesn't matter. It's a matter of being able to drive the video card appropriately, which in many cases isn't possible. Some VESA modes may work but mostly you have to worry about dumb things like video drivers consuming memory and kernel resources better spent on firewall tasks. Thank You again one time for suggestion. From this point of view where better to place the settings for screen resolution (/boot/loader.conf, /boot/loader.conf.local, Advanced / System Tunables) to not losing settings after pfSense system update?

There's no way to change that behaviour as far as I know. I have looked into it a few times in the past and nothing I have tried had any effect. There is no ACPI power button on the XTM8 so you would still need to power cycle it to boot again anyway. Unless you added one. Steve

You should only have that one line in loader.conf.local because that will take preference over loader.conf. So if you change anything in pfSense that requires updating loader.conf it will not work if you have all the old settings in the .local file. For LCDproc I use: [image: 1635345253933-screenshot-from-2021-10-27-15-33-12.png] [image: 1635345261784-screenshot-from-2021-10-27-15-33-35.png] The screensize and port settings are hard coded into the SDEC driver so it doesn't actually matter what you set there. Obviously the choice of screens to display is up to you but those work well for me. Steve

@c_c said in Supported and working external Gigabit NIC: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210488 Ah, interesting, Do you see the very high error rate when flow control is not enabled?

@rmeskill Thank you for the responce. I have Done the same now.. and i hope the huawei model i bought today will work better :)

It's x86-64. VK-T40E was our internal name for APU(1) sold through the pfSense store. The CPU is an AMD G-T40E. It's this: https://www.pcengines.ch/apu1d4.htm I would certainly expect it to run OpenBSD if that's what you need. What's the actual error you see? Does it still boot pfSense correctly? Try the memstick serial image: https://nyifiles.netgate.com/mirror/downloads/pfSense-CE-memstick-serial-2.5.2-RELEASE-amd64.img.gz Steve

It looks like there may have been several hardware versions of that. If it's an x86 device then...probably. Is this something you have already? Steve

Quick update: I was able to rescue the config file by forcing read/write operations. I'm going to try RMAing the bad SSD and reinstalling pfsense on a new drive with the old config.

Because it only monitors the link between the pfSense WAN and the gateway. Which means if the ISP has an outage beyond that you don't log that. But also the gateway IP might not respond to ping at all. Or might be configured to drop pings when it's loaded, which could be what you're seeing. If you test pinging to something external from a client behind pfSense when the gateway is showing a loss that would confirm it. Steve

Indeed, that SoC does not have any thermal sensors we can read.

@stephenw10 I started a new post since this is so old. https://forum.netgate.com/topic/167257/realtek-network-card-packet-loss I will try this but I already performed the steps above in this post. It says all packages are up to date. Thanks

@stephenw10 Thank you. I'm having issues with dropped packets and will try the drivers from Realtek now that I know what I currently have.