Nice! Yeah we've seen ASPM cause all sorts of issues.

I found this post and this is exactly what I want to do. https://serverfault.com/questions/1034535/pfsense-dns-port-forwarding Instead of setting NAT reflection to Enable (Pure NAT) I tried setting Enable (NAT + Proxy) and I'm able to see result when I dig with my domain x.x.com. Unfortunately, I'm still unable to connect to DoT from my Android phone.

@stephenw10 Thank you @viragomann 's solution worked directly connecting to the firewall hardware console using video cable, keyboard and mouse. Thank you again!

Ordering the Rackmount version shortly and I'll test restoring one component at a time to see if the interrupts persist, or at what point they may increase.

@stephenw10 unless they work for the ISP of the Feds.. Anyhow.. My fasting recipe 1/8 cup honey 1 banana 1/2 pint fresh blue berries 1/2 pint fresh red grapes with seeds 1 skinned Golden delicious apple no seeds 1/2 pint great value frozen fruit blend. 1/2 pint great value frozen tropical blend top off with Eureka spring water,, blend into a smoothie.. and get your crown on.. :)

Yes by default the server set in general settings don't do anything. pfSense resolves directly (Unbound in resolving mode) and clients are passed the local interfaces address to query against that. Do you see blocked traffic in the firewall logs? Your rule probably isn't matching as you intended it to.

@JonathanLee - nope ... 2.7.2 CE from Dec of last year.

Hmm, as you say the llinfo arp messages have obscured anything that might give us a clue. Really not much to go on there. The backtrace shows a general memory error but that could be hardware or software. Is that the first time it has happened? Did it happen after upgrading to 23.09.1?

Yup use a static mapping: https://docs.netgate.com/pfsense/en/latest/services/dhcp/ipv4.html#static-mappings

@mtis This issue might also be caused by the ISP requiring DHCP renew requests to be QOS marked or VLAN Priority tagged. I have a french ISP that requires all DHCP frames to Priority 6 vlan tagged - otherwise they just don’t reply to the frames. Do you have any chance of doing a packet capture of the ISP’s CPE doing DHCP discover and renew? Then you could see what they might be doing (if not just requiring renews to be broadcasted).

That's not a wireless problem. It sounds like you have misconfiguration in the VLANs somewhere. Probably in the switch. Steve

Sorry typo'd that; it shouldn't be under TNSR! Also IIMB is already present in 23.09. You can just enable it.

Great. Yes there are a bunch of improvements there coming in 24.03.

Edit the entry then you will see that.

@stephenw10 Thanks for those suggestions. I will give it a shot.

@stephenw10 @Gertjan around 24 hours after switching off all of the power saving modes, and everything is chugging along perfectly with zero errors or logs on the console. I thought I had configured something wrong and would have to do a fresh reinstall and reconfig. Thank you so much!

@MakOwner I concur with @stephenw10 's recommendation to set up an IP-alias VIP (under Firewall/Virtual IPs) for each additional public IP address. I got my multi-address configuration set up in an hour or two using that approach, despite being a complete newbie with pfSense. Once the VIPs are in place you can either use 1:1 NAT to map one of those addresses to an internal server, or use individual port forward rules. If you do 1:1 NAT you'll still want firewall rules to block all server ports you don't want exposed, so it ends up about the same number of firewall rules either way --- which way you do it depends on how you'd rather think about the setup.

Probably because internal users are trying to use an FQDN to access it that resolves to the pfSense public IP address. See: https://docs.netgate.com/pfsense/en/latest/recipes/port-forwards-from-local-networks.html Steve

Branch naming issue. The beta should be available to anyone who wants to test but should only show on the System > Updates screen when you navigate to it. Steve