![Opening port 5353 in the Windows XP Firewall to enable an XP PC to configure the Airport Express and use AirTunes Opening port 5353 in the Windows XP Firewall to enable an XP PC to configure the Airport Express and use AirTunes](https://ifelix.co.uk/tech/images103/1008.gif)
Opening port 5353 in the Windows XP Firewall to enable an XP PC to configure the Airport Express and use AirTunes
hb-service listening on port 5353 which conflicts with avahi daemon · Issue #3077 · homebridge/homebridge · GitHub
![Bug #8409: pfsense alias complains about well known name for non well known port - pfSense - pfSense bugtracker Bug #8409: pfsense alias complains about well known name for non well known port - pfSense - pfSense bugtracker](https://redmine.pfsense.org/attachments/download/2369/Screen%20Shot%202018-03-31%20at%2015.25.24.png)
Bug #8409: pfsense alias complains about well known name for non well known port - pfSense - pfSense bugtracker
![Opening port 5353 in the Windows XP Firewall to enable an XP PC to configure the Airport Express and use AirTunes Opening port 5353 in the Windows XP Firewall to enable an XP PC to configure the Airport Express and use AirTunes](https://ifelix.co.uk/tech/images103/1005.gif)
Opening port 5353 in the Windows XP Firewall to enable an XP PC to configure the Airport Express and use AirTunes
![I have these options checked on WAN. Should they be checked on LAN? Firewall logs are flooded with "Default Deny IPv6(1000000105)" with destination to "ff02::fb:5353" on my LAN interface. : r/PFSENSE I have these options checked on WAN. Should they be checked on LAN? Firewall logs are flooded with "Default Deny IPv6(1000000105)" with destination to "ff02::fb:5353" on my LAN interface. : r/PFSENSE](https://preview.redd.it/zhxfuxgz9fi71.png?auto=webp&s=8a8b5569c814c9237edcc0976cf10a7d9f72ed26)