In my rather strange setup I am using the default VLAN for regular home traffic and have added several VLANs on top of that for Guest network and other kinds of traffic.
My network is guarded by a Dell Sonicwall NSA240 and the N66U is only configured as an access point. Basically, the NSA240 uses no VLAN for home traffic and has 5 VLAN configured for Guest, Test, Acceptance, etc… The N66U bridged WAN interface has been configured as a trunk port so I can host my Guest network on a virtual wireless interface and on port 1 for a vodafone femtocell. The other interfaces are untagged default VLAN.
Everything works like a charm but I have to set this up via the command prompt as the GUI tells me the WAN interface can either have untagged traffic or it can host tagged traffic but not a mix of the two. To fix this, I just tag the default VLAN on the WAN interface as well. Save… and use the command line to untag the WAN interface. After that, I have a nice working trunk with all my VLANs including the untagged default home traffic.
Is my setup that strange ? Or is it just something that can be added to the GUI ?
Another one; using the latest 121 firmware, the port status icons do not seem to work properly. Using an older firmware release I used the VLAN offset (96) to create my 100+ numbered VLANs. If I restore that backup, everything works fine and the port status icons are a 100% match with what is plugged in and active.
After I remove the offset (0) and manually enter the correct VIDs, the basic VLAN functionality continues to work as expected (still ssh into the router to untag WAN :-)) but the status icons suddenly show incorrect activity. port 3 is offline and port 2 is online (should be vice versa) and suddenly port 4 is active whereas that one is unplugged.
Now, I honestly fail to see the relation between a reconfigured VLAN from using offset to using manually entered VIDs but I am telling you, this is what makes my GUI port status lights going all dancing queen on me.
Many thanks !