@phlmike said in Odd dns replies from ARIN and now another server: I only use pfBlockerNG A quick google for pfblocker and PTR seems to point to it doing them.. I don't use most of pfblocker functionality - I only use to mange some aliases via geoip and other lists for native aliases. Nor have I noticed any sort of blocks from dns root or gltd or in-appr servers.. But if I had to guess it prob related to that.. flagging @BBcan177 as he would be the guy to when and how pfblocker might do ptrs.. But even if was doing them the responses shouldn't be blocked unless issue with states or the answer coming in on on some interface pfsense doesn't expect the answer to come on

@bavcon22 Solution is to order another home Licence for pfsense+. It Would Be Nice if the licence will not be lost when the hardware changed.

@stephenw10 No issues found. :/

That ^. It sounds like you may be confusing the WAN and LAN addresses. The webgui will be accessible on both the WAN and LAN IP addresses from a client on the LAN side. All traffic inbound on the WAN side is blocked by default. Steve

Yeah These days, most devices get an IPv4 'because there is one' but if you look closely, they all use the other one : IPv6. Even when I'm posting here, on this forum, it's a solid IPv6 - no IPv4 in sight. So, I stuffed the dhcp6d full with 'static' global "DUID" based IPv6 assignments. Not that I'm trying to know these addresses, but that every device has a host name that I chose and remember.

Thank you @gertjan for the reply. I'm a newbie and I appreciate all the info and experience :) By the way, StarLink has arrived and configured for failover for students and guests. The current Internet (the expensive, guaranteed bandwidth) access is configured as the failover for the rest.

Does anyone have an IP list for HBO Max to whitelist in PfSense?

@udasboot Excellent, very happy your persistence with the ISP got a resolution. Enjoy the awesomeness that pfSense brings to your network quality and capabilities!

@pootle I don't recommend everyone do this because it is dangerous but you can shave the last 1/8" (3mm) off a shroud to get it to fit most things! Before [image: 1681835804913-img_2029-medium.jpeg] After [image: 1681835808526-img_2030-medium.jpeg]

Solved : false positive verified by Malwarebytes - This was due to a database that dynamically applies new patterns in the wild to proactively block emerging threats and was obviously an FP. This should be resolved in the next database update (give it about 30 minutes) [https://forums.malwarebytes.com/topic/296960-false-positive-pfsense-router-webgui/#comment-1563675](link url) It will not be that fast is my bet but It is now confirmed and can move on Hopefully this helps someone else as well And thank you guys very much !! and for humoring me along the way :)

It didn't happen in previous releases because php didn't change major versions. The same thing (or similar) did happen when we moved from php5 to php7 a few years ago. We mitigated numerous php issues in testing but with a major version change like that there were always going to be some we didn't find. Steve

Dashboard looks nice. Unfortunately (still) no telegraf on SG-3100, just found this ...

Nice! Yeah moving the server to a different VLAN so the route is always through pfSense in both direction is the 'correct' solution here.

Many thanks for the detailed options and pointing me in the right direction bmeeks! You have definitely given me some good areas to research further.

@jimp Yes, I have some of the recommended patches applied, including the one you mentioned, so a version of 22.9 is expected. I see that https://docs.netgate.com/pfsense/en/latest/releases/versions.html now documents 23.05 as config version 22.9. Thank you for your clarifications to resolve my concern. Regards.

@stephenw10 thank you kindly sir I was downvoted on the reddit for this same question I appreciate your time.

Typical filename looks like this: config-pfsense.mydomain.biz-20220222183909.xml, where pfsense.mydomain.biz is to replace with the pfSense name followed by FQDN. Regards

@stephenw10 Got it. Very much appreciate the info! Thank you!

@bmeeks said in Weird issue with SMTP: https://redmine.pfsense.org/issues/14031#note-15. Aha ! So, a non root instance couldn't overwrite with an empty queue file so it kept on sending the same queue content. Nice catch ! Thanks for the patch code

What gateway are you being passed by the ISP? No route error like that implies it might be outside the WAN subnet. There's a advanced gateway setting for allowing a gateway like that: 'use non-local gateway'. If that's what is happening.