Mmm, it's a known issue. It's ugly but harmless. You shouldn't ever manually edit the loader.conf file normally but you can remove the duplicates. Any loader value you need to set or unset should always be put in loader.conf.local. Steve

@stephenw10 Finally got it working! On the fifth support call to KC I asked them to double check the login details with me, the password was one character wrong! I had manually typed this in to my router a year ago yet somehow the connection worked. I can only assume their modem management filled in the correct details. Thank you for your help Stephen. I'm mad it took me 5 days to get this sorted but relieved I don't have to change ISP to get it working.

@srytryagn said in Best non-Intel Quad port NICs ?: @nimrod Udate-a-bility-> If the firmware is not updated and vulnerable was thinking that it might not be a good idea to to use it for an edge device, i.e/ a very trusted firewal. Perhaps some Broadcomss or modern intel. Those are extremely rare cases that NIC needs a firmware update to fix a critical security issue. Im with @stephenw10 on this one. Stick with Intel. You will save yourself from unnecessary headaches. to your point -> do you mind expanding on that ? Is there a mitigation? Thought that was only an issue for " pro" amd and that intels had a way to shut off in bios.` There is no mitigation. Every Intel and AMD motherboard manufactured after 2006 has a embedded chip that runs modified closed source version of MinixOS that has low level DMA access. DMA access means. Full access to the contents of your RAM. Full access to your storage. Full access to your I/O devices. It can capture keystrokes, mouse movements, take screenshots...etc. It basically owns your system completely from the moment you turn it on. It boots first, so its completely irrelevant what operating system you use. Intel calls this "feature" Intel Management Engine, and AMD calls it PSP which is short for "Platform Security Processor". There were several attempts to remove ME/PSP but intel/AMD made it impossible. When your system is done with POST, CPU microcode checks for the presence of ME/PSP and makes a handshake through a custom encrypted protocol. If the handshake fails, a timer in CPU is triggered and system reboots after 30 minutes. Basically, if you somehow remove ME/PSP your system will be stuck in permanent reboot loop state until full ME/PSP functionality is restored. There are very limited number of motherboards and old laptops where ME can be fully or partially disabled. You can find more info about this here.

What do you see from Diag > DNS Lookup in pfSense? Are the clients using 1.1.1.1 dircetly for normal lookups? Steve

Just turn off IPv6 - does it work now? There you go you know where the problem is happening. But doing a directed query to 1.1.1.1 which wouldn't be IPv6 and getting a timeout just seems like bad connectivity, or slow connection, are you routing through a vpn? Are you on sat connection? You doing some odd redirection of dns traffic on pfsense? Do you have isp or other router in front of pfsense doing dns redirection?

It should be logged there if you have logging enabled on the pass rule(s) and any states have been opened. It may have left the logs already if you have a very busy WAN.

@bokolobs said in Anyrevo fanless appliance hitting >60 C, is this normal?: @nimrod I actually have an extra tube of Thermal Grizzly Kryonaut lying around. I might re-paste it if I feel adventurous. I would not do it. Although cheap, there is absolutely nothing wrong with your unit. All the issues you had so far were software issues. Just install pfBlockerNG, apply the patch and you are good to go. And thanks for the info regarding mini pc brands. This is my first unit like this. I'm used to assembling my own PCs, but I got lazy and just purchased this. It is also very difficult to get 4-port Intel NICs right now where I live. I still have a Beelink GK55 mini pc which I used as an Untangle box for almost a year, but it only had 2 Realtek ethernet ports and is no longer suitable for our network needs. I'll probably use this Anyrevo one until it breaks or gives me trouble. Or maybe I'll just build a low powered, mini-atx one with better specs if I can get my hands on Intel NICs. If you guys have recommendations, that would be awesome. Anyevo is a cheap appliance, but make no mistake. The board inside still has a Intel CPU and Intel NICs. Anyevo and other cheap Chinese brands, get lower prices by using lower quality metals for their case. Packaging is cheap. They have bad machining (rough metal), poor paint and printing on the case. They also ship their units with cheap AC adapters, cheap no name RAM and SSDs. There are no bios updates, software support, or any support for that matter. Warranty is also questionable. If you, for example, get higher quality power supply and better SSD, that unit will serve you for many many years with zero issues.

It looks like it's something in multicast routing though which is probably why more people are not hitting it. I don't see either IGMPproxy or pimd shown in your console output but do you have either configured? It could be same root cause as this: https://redmine.pfsense.org/issues/12079 It's very difficult to reproduce that issue unfortunately. Steve

Are you running that as TCP or UDP? It's hard to say from their website but it looks like it's UDP by default. That hardware should pass that without any difficulty at all. It could probably pass >5Gbps. I'd be amazed if this is not a restriction in the WAN some where. If you connect a client to the WAN directly do you see the expected 1Gbps with no loss? Does pfSense show packet loss in the WAN monitoring? Steve

@stephenw10 You sir are amazing! Thanks a bunch!!

@stephenw10 Ok, thanks!

@jimp I came across a post talking about this option. My configuration already had it disabled.

https://redmine.pfsense.org/issues/13388

There was a similar thread to this a few months back. User kept getting warnings from Hetzner about unregistered MAC addresses. It was a configuration issue though IIRC. As long as LAN side clients are sending all their traffic through pfSense anything on the WAN side cannot see the LAN side MACs. Since it's all virtual though Hetzner may be looking on the LAN side? Steve

@jarhead I have solved my Problems! I deleted everthing and started again several times! I have documented everything I did. Since it is a Word Document I've uploaded it to Dropbox, in case anyone is interrested here DropBox . Essentially I discovered that when I set up pfSense it connected to the DHCP Server in my ISP's Modem and gave it an IP Address on my WAN. I could not see why this needed changing so I left it alone and did not try to give it a static IP Address. I also think that when I had been asked during the pfSense installation process, when I was asked whether I wanted to enable a HTTP connection for WebConfigurator, I had answered "n", thinking that the alterantive would be HTTPS. This time I answered "y", and low and belhold I can now get into the WebConfigurator! Anyway, everything is now going and I no-longer have problems.

Check the logs. Unbound probably shows why it cannot start.

Of course FreeBSD supports multiple devices. pfSense is a firewall/router and was never intended to support multiple storage devices other than as a drive mirror. That's not to say it can't be done. If you search the forum there are multiple threads with users describing their own solutions for making it work. However all of them operate outside the default pfSense config such that if you need to reinstall and restore for example you need to be sure you can restore any custom scripting you added. It's far simpler to just install and boot from the larger drive directly. Steve

You could set the values very high since the other WAN is 100% down. So, for example, 1000ms latency and 80% packet loss. Really though you should tune the values to your connection. That's difficult to do if the cell is in very high use but you just want to avoid false alarms whilst still alerting if it goes down entirely. Steve

@stephenw10 Don't worry about it. It was Firefox with an adblocker but I hadn't seen that behaviour before with any other pfSense field. I'm not touching the pppoe config now that it's working.