PfBlockerNG blocking Xbox One X internet access

[protik]

Hi

I have got the PfBlockerNG-devel up and running recently however have noticed that it is blocking the Xbox console from connecting to the net. Is there anyway for me to tell PfBlockerNG to allow outbound traffic for Xbox?
I have tried whitelisting relevant domains (https://www.reddit.com/r/pihole/comments/gmhyyc/is_microsoft_requiring_even_more_domains_to_be/) under DNSBL however that hasn't resolved it. Xbox only seems to be able to connect to the internet when I deselect LAN from the Outbound Firewall Rules under IP settings tab in PfBlockerNG. The Xbox in connected to managed switch which is connected to one of the pfSense interfaces.

Thanks!

[stephenw10]

Yes, you can add a firewall rule to pass that traffic from the xbox as long as you have the rule ordering set correctly.

You can probably also whitelist it in pfBlocker.

Steve

[cesarmsj]

This post is deleted!

[brians]

@stephenw10
I tried this but the pfB*** rule keeps moving above whenever it is updated.

There is a rule order but does not provide what I want.
I want to lock my own rule so it is above the pfblocker always.

Any suggestions?

[stephenw10]

Yes. Set the auto rule ordering correctly in pfBlocker. Have it add rules on the standard interfaces amd add your pass rule as floating for example.
Or configure pfBlocker to create aliases only and use them in your own rules. Then you can order them however you want.

Steve

[brians]

I found it easier to just assign google DNS via DHCP server for my Xbox Series X.

The only thing additional thing I had to change was modify my Redirect DNS NAT firewall rule to use a source alias for IPs. This alias contains IP for every host in my subnet (gets auto generated when adding a network eg. 192.168.10.0/24.) and I deleted the ones I didn't want enforced - my Xbox.

Of note is that it won't let me enter an alias until I click Save and it errors prompting me to enter a value which then I can.

[stephenw10]

Ah, so a DNS issue then? That would be unrelated to the auto firewall rule ordering you were seeing.

Steve