Hi everyone
I’m fighting with a network issue, where my synology nas doesn’t accept any connection from outside it’s subnet.
So, here’s my setup:
-
Unifi Infrastructure with three separated subnets:
- default:
xxx.xxx.2.0/24- no vlan - pool with all “safe” devices (notebooks, mobiles, servers etc.) - IoT:
xxx.xxx.83.0/24- vlan 83 - here are all the IoT devices, including nvidia shield, multiple chromecast music devices etc.) - guest:
xxx.xxx.20.0/20- vlan 20 - quarantined guest wlan - dns server are locally hosted at
xxx.xxx.2.42 and 43
- default:
-
my I got a new NAS and i designated my old DS214play (running DSM 7.1.1-42962 Update 6) as a Mediaserver that gets to live in the IoT net:
- changed the ip from
xxx.xxx.2.50toxxx.xxx.83.50 - updated the gateway and subnet
- added the vlan tag 83 on the network port
- updated the firewall to allow all necessary ports from and to the default network (so I can stream plex to my notebooks etc.)
- changed the ip from
-
The Firewall on the NAS is not activated
Issue:
- My NAS doesn’t accept any outside connections after moving it to the IoT subnet, neither from my default network nor the internet.
What I tried:
- allowed full access between LAN and IoT subnet for the NAS.
- tried it with another port -> same issue
- connected another device to this port (and setup the same firewall rules) -> this one works fine.
- checked the
unifi firewall logs--> requests get sent from the nas and answers from the other device - checked
logs of other devices (DNS, NetCat etc.)--> they receive the requests outside of the subnet, and return their anser but the NAS seems to block/ignore any incoming packages.
What I didn’t try:
- setting the VLAN id under
"Network Interface" > "LAN" > "Enable VLAN(802.1Q)"since, as far as I understand, the Unifi VLAN implementation terminates the VLAN tag at the port of the switch (and all other devices work without specifying it locally) - fully reset the NAS
I’m completely stuck how to solve the issue, so I have moved the NAS back to the default net, but some use cases are not working properly that way, so I’d really like to move it to the IoT subnet. Does anybody have (has?) any hints or knows of some obscure settings which need to be updated? I’d be really grateful for any pointers.
You must log in or register to comment.
Others have given you a good idea, but since you appear to be using Unifi for switch and firewall, o can give you a clear answer: Don’t set vlan on the Synology. Set it as the “Native” VLAN on the switch port going to the Synology.
Synology can be vlan aware, but you don’t need it. Let the switch do the talking.
On the Synology I recommend putting it on DHCP while you test. Once it starts getting an IP in the right subnet, you can then switch it to static. Just make sure your gateway is right, putting it wrong will cause the device to not be able to reach outside its own subnet.
I’ll try that one thanks
So if I understand this right you will need to change the network on the port attached to the synology in your UniFi configuration or set the vlan tag in the synology OS, I would do the former. It sounds like you just added a second network/vlan to the existing interface which means you actually created a trunk and are getting the old network untagged and the new network with vlan tags which the synology is dropping. Synology OS also doesn’t really support trunked ports through the UI (even though it does support a port that only uses a vlan tag) so it’s much easier to just leave them untagged.
So if I understand this right you will need to change the network on the port attached to the synology in your UniFi configuration or set the vlan tag in the synology OS, I would do the former.
doesn’t the switch terminate any VLAN tagging at the port? so if I add the VLAN to the DSM configuration it doesn’t receive any tagged packages and refuses them?
It sounds like you just added a second network/vlan to the existing interface which means you actually created a trunk and are getting the old network untagged and the new network with vlan tags which the synology is dropping.
with all the other devices in the IoT subnet it works with setting the VLAN on the port of the switch. If I check back on the unifi site, I found this:
'Applying a VLAN to a Switch Port Native VLAN The Native VLAN is the VLAN assigned to "untagged" traffic passing through a switch port. Devices physically connected to a switch port will be placed on this Native VLAN. Tagged Networks and Trunk Ports Ports can be configured to allow traffic from other networks. Allowing specific networks/VLANs is referred to as “tagging” them on the switch port. You can see all ports’ VLAN tags in the VLAN Viewer, found in the Ports tab. Ports that have been tagged to allow traffic from multiple VLANs are referred to as “trunk” ports. By default, all ports on UniFi Switches are trunked to allow all VLANs. 'if I understand that in combination with your comment correctly: I set the native VLAN to
83so everything tagged with83is correctly forwarded to the NAS and accepted there, stuff tagged with1are non native, the tag stays on and the NAS doesn’t accept it?But that would make the Synology NAS quite hard to use in any corporate setting with multiple VLANs which need to interconnect and why does it work the other way around? while being in the default net
1it does accept stuff from VLAN83Synology OS also doesn’t really support trunked ports through the UI (even though it does support a port that only uses a vlan tag) so it’s much easier to just leave them untagged.
which would mean, I can’t put it in the IoT net?
Did you change the native VLAN to IoT or just added the tag and left the native VLAN on the switch port set to default? You should be able to change the native VLAN and leave tagged VLANs as “allow all”.
My only other thought is how did you isolate the IoT network and are you able to access other devices from default to IoT?
I changed the native vlan to ‘83’ and allowed all others
The isoöation is done with firewall rules blocking access from the IoT net to default, with some exceptions (dns, media nas (currently), etc.)
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters DHCP Dynamic Host Configuration Protocol, automates assignment of IPs when connecting to a network IP Internet Protocol IoT Internet of Things for device controllers NAS Network-Attached Storage Unifi Ubiquiti WiFi hardware brand
5 acronyms in this thread; the most compressed thread commented on today has 6 acronyms.
[Thread #768 for this sub, first seen 28th May 2024, 08:15] [FAQ] [Full list] [Contact] [Source code]
Something like this happened to me. Change the static IP (configure your NAS to get its IP from DHCP) and fix the IP on the UniFi UI.
Worth a try, will try it when Im back home
Surely you want to enable 802.1q? Like, that is vlan aware switching and routing. Or is that on the nas?
Edit:
Some troubleshooting:Connect a laptop into the same subnet as your Nas (so same vlan and IP range/subnet) and connect to the nas. This either eliminates the NAS or the router from the equation
I’m a bit hesitant to activate the tag in the DSM, as it states that it then needs a tagged counterpart to be reachable, and since all the other devices in this subnet aren’t tagged anymore (as the switch untags the vlan at the port)
Connect a laptop into the same subnet as your Nas (so same vlan and IP range/subnet) and connect to the nas. This either eliminates the NAS or the router from the equation
did that, the NAS is easily reachable from within the subnet it’s only a problem from another subnet
