MDNS across wired and wireless: bridge or AVAHI

  • I'm standing up a "new" pfSense install at home. Hardware has onboard wireless, is a little short of resources (500 Ghz Geode, 256Mb RAM, 1GB CF). Two of the requirements are:

    • I want to have mDNS work between my LAN and wireless. This seems to imply that I bridge the two, or else run the Avahi package to reflect between the wired and wireless subnets.

    • I want to have separate RRD charts for the wired and wireless.

    Is it possible to get separate RRD charts for the separate physical interfaces if they are bridged, or does requirement #2 mean I can't bridge and thus need to solve requirement #1 with Avahi?

    Any other considerations when deciding to bridge or route?

  • Did you ever get any answers on these Avahi questions? I've got the same set of questions and am wondering if I should install Avahi on a new 2.2.4 install…

  • I am using avahi to route airplay between subnets on my network with 2.2.4.  It works great.

  • LAYER 8 Global Moderator

    What resources do you need..  My printer is airplay and I wanted my ipad to see it for example.. Easy solution was to just put the printer on same segment as the wireless via a wire.  My wired devices have no issues printing to printer on another segment.  So this was the simple solution to that problem.

    What other resources do you have that you need mdns to work?

  • I see, so Avahi is only needed to pass mDNS/Zeroconf/Bonjour traffic between separate broadcast domains right? e.g. between 2 VLANs, or between 2 separate network interfaces.  It is not needed if you only have a single LAN segment.

  • LAYER 8 Global Moderator

    exactly!  You can setup mDNS to work across segments but its a PITA ;)  avahi makes it easier.  But if you only have 1 segment, or your wifi and wired are on the same segment and your resources are wired n that segment your wireless devices on that segment can find them.

    I ran into this issue when I isolated my wireless for security reasons and still wanted to print ;)  Easy solution was to move my printer to that segment..