we are having some issues with the combination of IPv6/dualstack on our WLANs (which we had for quite some time) and the use of the VLAN Select-feature of our WISMs (Code: 126.96.36.199).
Due to the nature of VLAN Select, the clients can hear the multicasts from both VLANs, so they can hear the IPv6-RAs from both IPv6-routers. The clients then calculate an IPv6-Address for both routers (of which, only one is reachable - the one in the same VLAN as the client) and then some weird stuff happens, depending on the IPv6-Stack of the client-OS.
It seems that Linux-Clients have some trouble with this, leaving both routers on REACH or STALE, because the client receives RAs all the time. So even if there is no possibility for the client to reach the router in the other VLAN, it never marks it as UNREACH. So the client loses connectivitiy, if it chooses the wrong default gateway, depending on coincidence. First reports indicate, that Android phones (so a Linux-IPv6-Stack as well) suffer from the same flaw.
This does not affect IPv4, because in IPv4 the client does DHCP - so the client initiates the process for getting an address, versus the router sending RAs. So in a pure IPv4-Network, there is no chance of that becoming a problem.
So, my question: Does anybody run dualstack with VLAN Select? How to resolve this issues? The "multicast VLAN" feature with VLAN select is the exact opposite of what should happen...
The interface groups feature allows an organization to have a single WLAN with multiple VLANs configured on the controller in order to permit load balancing of wireless clients across these VLANs. This feature is commonly used to keep IPv4 subnet sizes small while enabling a WLAN to scale to thousands of users across multiple VLANs in the group. In order to support IPv6 clients with interface groups, no additional configuration is required as the system automatically sends the correct RA to the correct clients via L2 wireless unicast. By unicasting the RA, clients on the same WLAN, but a different VLAN, do not receive the incorrect RA.
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...
This is the start of a display filter cross reference between Wireshark and OmniPeek.
The 1st installment is a table of advanced filters. More filters will be added as time allows.
It is a living doc, so check back for changes every so often
Please feel ...
I have created a Powershell script to automatically add a Wireless Guest User on Cisco WLCs. (tested on 2500 Series)
The script should be completely self explanatory.
Powershell SNMP Module (Install-Module -Name SNMP)
SNMP Write Access to...