[Known Issue] [8.4.0 - 8.5.3] Bonjour Forwarding between VLANs not working

Ref.: #35199

Details:
We have received several tickets reporting that Bonjour Forwarding is not working when the user enables the feature between two VLAN interfaces in the Peplink router.

The issue will be noticed after a short period of time, once the feature is activated. The client devices (eg. Apple iPhone, iPad, etc) on the Client Network-VLAN are unable to receive Apple Bonjour traffic (mDNS) from the advertised device(s), eg. AirPlay, AirPrint, etc, on the Service Network-VLAN.

Conceptual Topology:
| VLAN 10 (Service Network) |<==Bonjour Forwarding==>| VLAN 20 (Client Network) |

We have prepared a special firmware (8.5.3s101) to mitigate the issue. The fix will be included in the next GA release.

Affected firmware version:
8.4.0 - 8.5.3 GA

Affected models:
All device models that support Bonjour Forwarding.

Fixed in firmware version:
8.5.3s101

Download Link Product Hardware Revision
Download B One Series HW1/HW1-2
MAX BR1 Pro CAT-20 HW7
MAX BR1 Pro 5G HW1
MAX BR2 Pro HW4
MAX Dome Pro LR HW1
MAX HD1 Dome Pro HW1-2
MAX Transit Duo Pro HW1
Download Balance 5000 EC HW1
Balance 2500 EC HW1
Balance 1350 EC HW1
Balance 310 5G HW1-2
Balance 310 Fiber 5G HW1-2
Balance 310X HW1-4
Balance 380X HW1
Balance 580X HW1
Balance Two HW1
EPX HW1
MAX HD2 MBX HW1-4
MAX HD4 MBX HW1-4
MAX MBX Mini HW1
PDX HW1-2
SDX HW1-3
SDX Pro HW1-2
Download Balance 20X HW1-3
MAX BR1 IP55 HW4
UBR Plus HW1
Download Balance 210 HW4-5
Balance 30 LTE HW3
Balance 30 Pro HW1
Balance 310 HW4
Balance One HW1-3
Balance One Core HW1
MAX 700 HW3-4
MAX BR1 ENT HW1-2
MAX HD1 Dome HW1
MAX HD2 HW5-6
MAX HD2 Dome HW1
MAX HD2 IP67 HW2-5
MAX HD2 Mini HW1-4
MAX HD2 with MediaFast HW1-4
MAX HD4 HW1-5
MAX HD4 IP67 HW1
MAX HD4 with MediaFast HW1-4
MAX Transit HW1-3
MAX Transit 5G HW2-3
MAX Transit Core HW1
MAX Transit Duo HW1-3
MAX Transit Duo Pro E HW1
MediaFast 200 HW1,3
SpeedFusion Engine Cam HW1
Download Balance 1350 HW2
Balance 2500 HW1
Balance 305 HW2
Balance 380 HW6
Balance 580 HW2-3
Balance 710 HW3
MediaFast 500 HW1-2
MediaFast 750 HW1

NOTE:
This special firmware included the fix in 8.5.3s024 to support iPhone Tethering for those supported models.

4 Likes

this version formware included 8.5.3s093 fix ?
If not, can include it ?

tks

@bruce.wh.kuok I have checked, the fixes in 8.5.3s093 are independent and not included in 8.5.3s101. However, both special firmware fixes will be added in the next GA firmware.

If you have an immediate situation that needs both fixes, do let us know, and we will see how to accommodate that.

1 Like

Thanks for your replied.
I was just curious, why special version not include previous fix.
:slight_smile:

How soon can we expect the next GA firmware?

@WeiMing do you think this fixes the issues with VLANs and Outbound Policy failing to route traffic properly?

See https://forum.peplink.com/t/outbound-policy-vlan-bug-in-8-5-and-8-4-1/

1 Like

@soylentgreen some of the described symptoms in the ticket matched with other occasions we have from a different user. You can try to load this special firmware, and report back to us if you still encounter the issue.

If required, we can re-open the ticket (PTS#25020175) and follow up with you on the case.

1 Like

I’m testing 8.5.3s101 on my Balance One, and it does not seem to fix the bug referenced here: Outbound Policy + VLAN bug in 8.5 and 8.4.1 - #16 by soylentgreen

Immediately after rebooting in 8.5.3s101, some devices IOT devices (on ethernet VLAN) are unable to get DNS service. Powercycling the devices doesn’t help.

What did help is Disabling DNS Proxy and DNS Caching, saving changes, then powercyling the devices. At that point I can turn DNS Proxy and Caching back on and all is normal, at least for a while…then days later something starts to malfunction again. [Edit: at least with 8.5.3 release version - I will report back in a few days to see if this special s101 build also has that problem]

I don’t know if this is two manifestations of the same bug, or two different bugs, but it sure would be nice to get this issue fixed (it seems to be some combination of: Ethernet VLAN, Outbound Policy, and DNS Proxy/Caching) but I’ve never been able to figure out the exact issue.