<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Best Practice for Ruckus Unleashed Bonjour Gateway in Unleashed</title>
    <link>https://community.ruckuswireless.com/t5/Unleashed/Best-Practice-for-Ruckus-Unleashed-Bonjour-Gateway/m-p/111105#M7145</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I’m setting up the Bonjour Gateway feature on Ruckus Unleashed and want to make sure the VLAN configuration is correct so I don’t cause duplicate printers, loops, or multicast flooding.&lt;/P&gt;&lt;P&gt;My setup:&lt;/P&gt;&lt;P&gt;Dedicated Unleashed AP acting as the Bonjour Gateway&lt;/P&gt;&lt;P&gt;AP is using its default untagged management, which corresponds to VLAN 5 on the switch&lt;/P&gt;&lt;P&gt;Printers also live on VLAN 5 (AirPrint-enabled HP LaserJet units)&lt;/P&gt;&lt;P&gt;Wireless clients (iPhones/iPads) are on VLAN 15&lt;/P&gt;&lt;P&gt;Goal: Allow users on VLAN 15 to discover printers on VLAN 5 using AirPrint&lt;/P&gt;&lt;P&gt;Current Bonjour Gateway rule:&lt;BR /&gt;AirPrint: From VLAN 5 → To VLAN 15&lt;/P&gt;&lt;P&gt;Questions:&lt;BR /&gt;&lt;span class="lia-unicode-emoji" title=":keycap_1:"&gt;1️⃣&lt;/span&gt;Should I also configure the reverse direction?&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;AirPrint: From VLAN 15 → To VLAN 5&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Or would that create a Bonjour/mDNS loop, causing duplicate printers and excess multicast traffic?&lt;BR /&gt;My understanding is that AirPrint only needs to flow from the printer VLAN to the client VLAN, not in both directions — but I’d like confirmation from others with Unleashed experience.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":keycap_2:"&gt;2️⃣&lt;/span&gt;Should the Unleashed Bonjour rule use VLAN 1 or VLAN 5?&lt;/P&gt;&lt;P&gt;Even though the AP is managed on VLAN 5 (untagged), I’ve seen documentation and forum posts saying you sometimes need to select VLAN 1 inside the Unleashed UI because Unleashed internally treats the untagged/native VLAN as “1” unless otherwise overridden.&lt;/P&gt;&lt;P&gt;So which is the correct “From VLAN” value in this situation?&lt;/P&gt;&lt;P&gt;Printers physically on VLAN 5&lt;/P&gt;&lt;P&gt;AP management/native VLAN is also VLAN 5&lt;/P&gt;&lt;P&gt;Switch trunk native VLAN = 5&lt;/P&gt;&lt;P&gt;Should the Bonjour rule be:&lt;/P&gt;&lt;P&gt;From VLAN 5 → To VLAN 15&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;or&lt;/P&gt;&lt;P&gt;From VLAN 1 → To VLAN 15&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;depending on Unleashed's internal VLAN handling?&lt;/P&gt;&lt;P&gt;I want to be sure I’m not accidentally choosing the wrong VLAN in the GUI, especially since Bonjour behavior is sensitive to VLAN mismatches.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Wed, 12 Nov 2025 23:20:46 GMT</pubDate>
    <dc:creator>matthewlampe</dc:creator>
    <dc:date>2025-11-12T23:20:46Z</dc:date>
    <item>
      <title>Best Practice for Ruckus Unleashed Bonjour Gateway</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/Best-Practice-for-Ruckus-Unleashed-Bonjour-Gateway/m-p/111105#M7145</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I’m setting up the Bonjour Gateway feature on Ruckus Unleashed and want to make sure the VLAN configuration is correct so I don’t cause duplicate printers, loops, or multicast flooding.&lt;/P&gt;&lt;P&gt;My setup:&lt;/P&gt;&lt;P&gt;Dedicated Unleashed AP acting as the Bonjour Gateway&lt;/P&gt;&lt;P&gt;AP is using its default untagged management, which corresponds to VLAN 5 on the switch&lt;/P&gt;&lt;P&gt;Printers also live on VLAN 5 (AirPrint-enabled HP LaserJet units)&lt;/P&gt;&lt;P&gt;Wireless clients (iPhones/iPads) are on VLAN 15&lt;/P&gt;&lt;P&gt;Goal: Allow users on VLAN 15 to discover printers on VLAN 5 using AirPrint&lt;/P&gt;&lt;P&gt;Current Bonjour Gateway rule:&lt;BR /&gt;AirPrint: From VLAN 5 → To VLAN 15&lt;/P&gt;&lt;P&gt;Questions:&lt;BR /&gt;&lt;span class="lia-unicode-emoji" title=":keycap_1:"&gt;1️⃣&lt;/span&gt;Should I also configure the reverse direction?&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;AirPrint: From VLAN 15 → To VLAN 5&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Or would that create a Bonjour/mDNS loop, causing duplicate printers and excess multicast traffic?&lt;BR /&gt;My understanding is that AirPrint only needs to flow from the printer VLAN to the client VLAN, not in both directions — but I’d like confirmation from others with Unleashed experience.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":keycap_2:"&gt;2️⃣&lt;/span&gt;Should the Unleashed Bonjour rule use VLAN 1 or VLAN 5?&lt;/P&gt;&lt;P&gt;Even though the AP is managed on VLAN 5 (untagged), I’ve seen documentation and forum posts saying you sometimes need to select VLAN 1 inside the Unleashed UI because Unleashed internally treats the untagged/native VLAN as “1” unless otherwise overridden.&lt;/P&gt;&lt;P&gt;So which is the correct “From VLAN” value in this situation?&lt;/P&gt;&lt;P&gt;Printers physically on VLAN 5&lt;/P&gt;&lt;P&gt;AP management/native VLAN is also VLAN 5&lt;/P&gt;&lt;P&gt;Switch trunk native VLAN = 5&lt;/P&gt;&lt;P&gt;Should the Bonjour rule be:&lt;/P&gt;&lt;P&gt;From VLAN 5 → To VLAN 15&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;or&lt;/P&gt;&lt;P&gt;From VLAN 1 → To VLAN 15&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;depending on Unleashed's internal VLAN handling?&lt;/P&gt;&lt;P&gt;I want to be sure I’m not accidentally choosing the wrong VLAN in the GUI, especially since Bonjour behavior is sensitive to VLAN mismatches.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Wed, 12 Nov 2025 23:20:46 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/Best-Practice-for-Ruckus-Unleashed-Bonjour-Gateway/m-p/111105#M7145</guid>
      <dc:creator>matthewlampe</dc:creator>
      <dc:date>2025-11-12T23:20:46Z</dc:date>
    </item>
  </channel>
</rss>

