Community discussions

MikroTik App
 
odroid
just joined
Topic Author
Posts: 10
Joined: Thu Sep 15, 2022 8:46 am

No accessibility to Samba Synology server

Mon Sep 26, 2022 9:28 am

Hi there,
When I was creating a wifi guest with Bridge_Guest and a DHCP server. I cannot connect to my synology servers (Samba WORKGROUP) from my computers or Kodi (Internet works and I can access my other routers from Safari or Android Application: 192.168.0.1 etc...)

Guest Wi-Fi Setup

Address: 40.0.0.1/24
Network 40.0.0.0
Bridge_Guest interface

DHCP Server: Bridge_Server

Firewall / Filter Rules nothing
Nat: scrnat/40.0.0.0/24 masquerade

Do you have an idea ?

Thank you all
 
odroid
just joined
Topic Author
Posts: 10
Joined: Thu Sep 15, 2022 8:46 am

Re: Pas d'accessibilité au serveur Samba Synology

Tue Sep 27, 2022 10:09 am

I just succeeded, it may be a security flaw !!!

I created :
Wifi guest with VLAN
Address: 50.0.0.1/24
DHCP Server 50.0.0.2-50.0.0.20
Vlan20
Bridge_Vlan20
NAT ( Internet ok )

I connect to guest wifi, I get an ip address 50.0.0.20
On Kodi (Amazon Fire TV 4K), I want to add a video source that is on my Synology Server ( 192.168.0.90 ), it does not work (zeroconf, SMB)

You will tell me it's normal because I'm doing it from the VLAN and the network is separated.

So there is a possibility and I can't understand why it works?

From Amazon Fire TV 4K: Connect to another wifi which is on the same network as the Synology server.

Add the video source that is on the Synology server from Kodi.
Once done, cut the wifi and reconnect to the wifi Vlan and everything works.
I can browse my video source which is in my Synology

Do you have any explanations?
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11434
Joined: Thu Mar 03, 2016 10:23 pm

Re: Pas d'accessibilité au serveur Samba Synology

Tue Sep 27, 2022 10:54 am

Do you have any explanations?
The problem with such services is that very often they rely on broadcast auto-discovery. Which works very well inside single L3 network (i.e. where server and clients are in same IP subnet), but doesn't work between different L3 networks unless router is configured to aide auto-discovery. After client discovers server, it often uses unicast connections for further communication which works flawlessly over router (unless router runs firewall which blocks that traffic, but that's a completely different issue).

Who is online

Users browsing this forum: No registered users and 55 guests