AFAIK pfsense doesn’t support this natively but there is a script that you can run using the cron package that works great for me. https://forum.netgate.com/topic/137707/auto-update-check-checks-for-updates-to-base-system-packages-and-sends-email-alerts/3

For reference: https://redmine.pfsense.org/issues/15618

@mkap218 said in Selectively blocking mDNS/Avahi: It seems like I can't use firewall rules to block mDNS from reaching Avahi since there's no way to filter out individual destinations, right? Yes, you can use a firewall rule to block inbound mDNS packets to the firewall, which would prevent Avahi on the firewall from seeing them. That would allow you to say that mDNS for host X on VLAN A is not seen on either VLAN B or C. What you cannot do is to say that host X on VLAN A can be seen by hosts on VLAN B, but not by hosts on VLAN C. By extension, you cannot filter out "_printer._tcp.local" for host X on VLAN A from the advertisements for VLAN B but include it for the advertisements for VLAN C.

SOLVED It was partly my fault. When importing the .XML file it configures the Interfaces per default of my other main FW Hardware. That HW uses different assignment identification than the Netgate, therefore I have mismatched the Interface IDs. Expl.: Current HW Interface assignment Port1 WAN = PPPoE0 Port2 LAN = igb1 Port3 DMZ = igb0 Port4 ANP = igb2 Netgate Interface assignment Port1 WAN = PPPoE0 Port2 LAN = igc2 Port3 opt1 = igc3 Port4 opt2 = igc0

For future ref. phpmailer is included in the mailreport package

@stephenw10 When you say, "It would be much easier if they can just route the /27 to you via the current WAN IP in the /29..." are you saying that the DC changes the gateway address to be the same for both the /27 and /29 here?

@JonathanLee , @waldo15a Ever since the updates to UPnP a few releases back I have always kept my Outbound NAT to Automatic. If I'm not mistaken, the issue with static ports is being handled correctly by UPnP since the updates. And in my ACL entries, I only allow for a few necessary ports 3074-3076 and 28960-28964 required by most (all) games. [image: 1721807732664-567c140c-bd6c-49d4-b816-10d354ce597c-image.png]

@hspindel Search the forums https://forum.netgate.com/topic/38499/set-gateway-and-dns-in-shell

@xman111 said in Internet going down: I was hoping for an easier way Well, it's a way. Other might exist. pfSense uses, as a WAN, an ordinary NIC, the same as your LAN, and other interfaces. These stay 'up' as long as power is good. No reason an interface would be taken down. That said, pfSense can take it down for a moment, as there is a process called dpinger that constantly pings a remote host, normally your upstream gateway,n or, as many people do : they chose '8.8.8.8'. if the pings start to drop, pfSense detects a 'bad' connection, an can reset the WAN. The moden, as it sees (feels ?) his LAN going down, can re initiate the upstream connection.

Thanks For Sharing Information.

@Gertjan one PPPoE connection for both IPv4 and IPv6. This is the configuration page: [image: 1721666225067-38d93822-7c9c-4eec-868d-9508acf4566a-image.png]

@Gertjan thanks, really helpful. Still I don't know why Netgate have not fixed this. Enabling DoT should just be that and not affect anything else.

Try checking the NAT type in each game on your Xbox, like in DayZ or Fallout. Sometimes the game shows a different NAT type than the Xbox settings. If it's showing strict or moderate NAT, that could be the problem.

@sheprador said in Is there a rule to tell pfSense: Allow traffic to the Internet from this interface?: There is the possibility in pfSense to create a single rule in which I say: "everything that comes from the WiFiGuest Vlan can go to the Internet". (maybe a couple of rules if I have 2 WANs) Yes ! It's the default rule you've found on the LAN interface when you installed pfSense. Here are mine : [image: 1721650863262-345324ba-6d5c-40cd-bb67-3ce1021d496c-image.png] Forget about the first rule, it's a NAT NUT rule, useful if you have an UPS. The second and third rule could be combined into one, but I've split them in 2 so I can see direct "how much IPv4 and how much IPv4". As soon as the IPv4 counters stays at "0" for a while, I can remove and disable IPv4 everywhere ^^

@SteveITS Many thanks for helping. Best regards

@stephenw10 Thanks very much for that. I did the upgrade and have not had the issue since. I did try looking for instructions on how to do this, but Google was not very helpful with the terms that I used. Either way, thanks again for the help.

sorry, my mistake. i had another drive (empty but normally mounted) that was the real problem, not zfs. i removed it from fstab and the system boot completed. again sorry for the false alarm...