Business Community > Controllers > mDNS Inter-VLAN
< Controllers

mDNS Inter-VLAN

mDNS Inter-VLAN

mDNS Inter-VLAN
mDNS Inter-VLAN
Yesterday - last edited 18 hours ago
Model: ER707-M2   Omada Software Controller (Linux)   TL-SG3210XHP-M2  
Hardware Version:
Firmware Version: 5.15.8.2

Hello,

 

I'm trying to configure the mDNS for Inter-Vlan communication.

 

What i want to archive is:

- Streaming Music from Smartphone to TV

- Accessing Media from TV stored on NAS

- Accessing NAS Storage from Windows-Clients (Samba-Share etc.)

- Accessing Printer/Scanner from Windows-Clients

- Accessing HomeAssistant from Windows-Clients

 

But i cant get it to work.

 

The NAS should be accessed via "NAS.local", but with no success.

Its not possible to add  Bonjour Service with "NAS.local"

Networkshares cant connect

 

Switch ACL for mDNS are set.

 

VLAN1 (Management VLAN) -> NAS

VLAN10 (Windows-Clients)

 

There is a very small limit in Bonjour Service  15 Records (5 Custom records with 3 Values only each)

The number of custom Bonjour Service has reached the limit.

 

I've followed the Guide.

 

In the Guide is an error. There is "IP-Group ACL" written. But it should be an IP-PORT-Group ACL

 

What do i need to do to get it work? Currently i've put TV/NAS/Windows-Client in the same VLAN, which Works.

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:mDNS Inter-VLAN-Solution
18 hours ago - last edited 18 hours ago

Hi @pustekuchen 

Thanks for posting in our business forum.

pustekuchen wrote

Hey, thanks for the response.

 

Yes, i've checked with wireshark

 

This are the packages, i receive with my windows client when im in the management VLAN1 192.168.0.*

 

If i switch the port settings of my EAP655 (which my Windows client is connected to with ETH Port), to PVID VLAN10. I never see any of the mDNS packages from my NAS again.

Some other do (from a printer)

 

So mDNS Proxy doesnt work.

 

Okay, i retried it again. And it seems get a response to the query now from the Gateway. I can ping NAS.local with success. But not NAS (without .local). This works in VLAN1.

What could be the problem with Pinging "NAS" ?

 

 

 

 

nas.local is the mDNS.

If you cannot ping NAS.lan, that's your DNS issue with the DHCP server.

 

The Omada router natively does not support NAS.lan dynamic binding.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update! ☛Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
Recommended Solution
  1  
  1  
#5
Options
4 Reply
Re:mDNS Inter-VLAN
Yesterday

Hi @pustekuchen

Thanks for posting in our business forum.

If you have set up the IP-Port Switch ACL to allow mDNS(5353), which is the ACL I talk about in that guide.

If you set up the protocol properly with the help of Wireshark, that's the Bonjour Service you need to create instead of imagining a thing called "NAS.local" as the Bonjour Service. If you don't know how to use Wireshark or the specific service name, go to your vendor and ask them about their mDNS service and add it manually.

That's basically the whole you need to debug for the mDNS. Or it is not a mDNS problem.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update! ☛Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
  0  
  0  
#2
Options
Re:mDNS Inter-VLAN
22 hours ago - last edited 22 hours ago

Hey, thanks for the response.

 

Yes, i've checked with wireshark

 

This are the packages, i receive with my windows client when im in the management VLAN1 192.168.0.*

 

If i switch the port settings of my EAP655 (which my Windows client is connected to with ETH Port), to PVID VLAN10. I never see any of the mDNS packages from my NAS again.

Some other do (from a printer)

 

So mDNS Proxy doesnt work.

 

Okay, i retried it again. And it seems get a response to the query now from the Gateway. I can ping NAS.local with success. But not NAS (without .local). This works in VLAN1.

What could be the problem with Pinging "NAS" ?

 

 

  0  
  0  
#3
Options
Re:mDNS Inter-VLAN
22 hours ago

to successfully ping "NAS" i needed to add a rewrite rule to my dns server for "NAS.lan". I will try the other services as well like screensharing etc.

  0  
  0  
#4
Options
Re:mDNS Inter-VLAN-Solution
18 hours ago - last edited 18 hours ago

Hi @pustekuchen 

Thanks for posting in our business forum.

pustekuchen wrote

Hey, thanks for the response.

 

Yes, i've checked with wireshark

 

This are the packages, i receive with my windows client when im in the management VLAN1 192.168.0.*

 

If i switch the port settings of my EAP655 (which my Windows client is connected to with ETH Port), to PVID VLAN10. I never see any of the mDNS packages from my NAS again.

Some other do (from a printer)

 

So mDNS Proxy doesnt work.

 

Okay, i retried it again. And it seems get a response to the query now from the Gateway. I can ping NAS.local with success. But not NAS (without .local). This works in VLAN1.

What could be the problem with Pinging "NAS" ?

 

 

 

 

nas.local is the mDNS.

If you cannot ping NAS.lan, that's your DNS issue with the DHCP server.

 

The Omada router natively does not support NAS.lan dynamic binding.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update! ☛Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
Recommended Solution
  1  
  1  
#5
Options

Information

Helpful: 0

Views: 65

Replies: 4

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.