NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
XR500 - VLAN tagging making wifi devices unable to communicate?
Hi,
I'm in Australia and just joined NBN FTTC, which required a new router that supported VLAN tagging - got XR500. My ISP iinet requires VLAN tagging for their service, via VLAN ID 2. Internet kicked in and everything appears fine on day 1; all devices can access internet.
A few days later I realise I cannot connect my nvidia SHIELD to my NAS (Synology DS1819+). They used to connect fine with my old Netgear DGND3700. NAS is wired whilst SHIELD is wifi because I don't have ethernet cabling in my lounge room.
I assumed it was an issue with the SHIELD and fiddled with a million settings on both the NAS and SHIELD, before a second wifi device tipped me off today. A second wifi device (Surface Go tablet) also cannot access the NAS.
Googling this issue raised a whole number of topics about VLAN tagging issues impacting the network. If I turn VLAN tagging off, my internet cuts out, but when it is enabled, it appears my wifi-connected devices can't talk to each other (can see each other but not negotiate).
By default, XR500 has VLAN tag group "internet" for all wired ports and all wireless ports. If I attempt to create another VLAN tag group, it permits LAN ports 1-4 or either/both wifi bands, but not the WAN port where the internet comes in.
This is super annoying because one of the primary functions of my network is to provide NAS service to all household devices and most of them are on wifi.
Any suggestions how I might change the configuration to keep my VLAN tagging for internet purposes, but allow the wifi devices to talk to the NAS?
Thank you
59 Replies
Replies have been turned off for this discussion
Oh, to add, I believe I can purchase a separate switch to handle the VLAN tagging and potentially alleviate the issues within my XR500 router, but I don't want to have to purchase more hardware, considering the XR500 is new enough and VLAN tagging isn't so uncommon for fibre ISPs.
- If you edit the standard rule and change the ID to 2 does that work at all? Are you able as a test to wire the shield to the router and see if it can connect to the NAS then just to rule out other issues.
Thanks for replying.
Yes I edited the standard rule, i.e. only have 1 rule in place.
I am not able to test the shield just now via ethernet as it's in another room and I need a TV to view the output - don't have any cables long enough. I could potentially try tomorrow by bringing the shield to my study and getting the output to my monitor.
However I was able to replicate the issue on a separate device - my laptop. If I plug the laptop into ethernet it can access the NAS. If I remove the laptop from ethernet and enable wifi, it cannot access the NAS.
So rather than pull out all the SHIELD cables and fuss about, I seriously suspect it's an issue with all wifi devices, not specific to the SHIELD, as illustrated with the laptop test.
- Thanks for that, that's what I wanted to know. For WiFi are you using Smart Connect? If so disable that and connect to the WiFi networks individually. If that doesn't work there are some options in Advanced WiFi settings - beamforming, MU-MIMO & HT160, I'd recommend disabling the later and playing around with those options to see if you can get it to work. Some devices don't like these options. If all else fails, make a guest wifi network and connect the affected devices to it and see if it works that way.
I know this is 4 years later, but the fix for me was the following
Under Vlan/Bridge Settings which is under advanced.
Go to By VLAN tag group and create a new group called "LAN" in the vlan ID box call it vlan 1 and select up to 3 Wired and 2 wireless (keeping one Wired port free)
After doing this click apply
Next and this is the most important step under where you see this new group. Make sure where it says "Enable" , Untick it!
For some reason what this does it keeps your one wired and one WAN as the one single vlan ID you require for internet.
And then it sets the rest of your wireless and wired as vlan 0, making communication work again across the different ways of communication (wired, wireless, 2.4/5ghz)
I'm also on the beta version XR500 V2.3.2.134-dumaos33-rc14
Thank you originaltechno !
I have been struggling with this since I moved to a full fibre ISP 2 months ago. I was about to go out and buy a new router.
