05-24-2012 03:37 PM
I've got a small network of 3 Aruba IAP-105s (firmware 188.8.131.52-184.108.40.206_33617), serving two SSIDs on two VLANs -- using the untagged VLAN for management traffic.
It seems that recently (possibly with a recent firmware upgrade) IPV6 router solicitation messages -- and it seems any IPv6 multicast traffic -- coming from wireless clients are not making it to the wired network. Clients on the wired network seem to do all right.
I've got mutlicast "optimization" and broadcast filtering disabled on these SSIDs -- but I've tested with "optimization" on and still don't see the expected traffic.
Are there any known limitations with the newer firmware versions, multicast, and IPv6 that I'm missing here? Swear this was working fine a couple of months ago!
05-25-2012 09:25 AM
This was certainly working when I was running the the 220.127.116.11-18.104.22.168 series code.
If its any help, I've got mostly OSX & FreeBSD on the network, and a NetGear GS724TP switch. I only became aware of this situation when I couldn't access any of my AirPlay devices that were wireless-connected -- Apple would like to use IPv6 multicast for discovery if the client has an active IPv6 stack. (the temporary solution has been to completely disable the ipv6 stack on the client to force it to use ipv4)
If you have a URL for the previous (22.214.171.124-126.96.36.199) firmware, I could try to downgrade the wireless firmware and verify the previous functionality.
05-25-2012 09:35 AM
Do you have an account on the Aruba support site? All images are posted there including Instant 2.0.
Drop me a note if you encounter any issues.
I am checking with my engineering team to see if there could be anything that could break this - but we may not have tested for this use case internally.
05-25-2012 12:44 PM
I did a quick test using IAP image version 188.8.131.52-184.108.40.206_33617 and did a packet capture. I see both ipv6 and ipv4 queries and responses with an iPad and apple tv.
So, this is working even with the latest Instant code.
05-27-2012 11:31 PM
It seems that downgrading to 220.127.116.11-18.104.22.168_32946 does actually fix this problem. Since I don't need any 22.214.171.124 features right now, this isn't a big deal.
To be more specific, the traffic that isn't making it onto the wireless network (or between wireless hosts) in 126.96.36.199 is the IPv6 multicast traffic (ethernet 33:33:xx:xx:xx:xx).
clock timezone Pacific-Time -08 00
syslog-level warn ap-debug
syslog-level warn network
syslog-level warn security
syslog-level warn system
syslog-level warn user
syslog-level warn user-debug
syslog-level warn wireless
mgmt-user admin XXX
wlan ssid-profile FreePublicWifi
wlan ssid-profile CostlyPublicWifi
wlan access-rule default_dev_rule
rule any any match any any any deny
wlan access-rule FreePublicWifi
rule any any match any any any permit
wlan access-rule CostlyPublicWifi
rule any any match any any any permit
05-29-2012 11:21 AM
Can you please send me a topology diagram with some idea of you IP addresses?
client -> IAP -> switch/router -> IAP -> client <something like this?>
and what is failing.
06-29-2012 07:26 PM
Thanks robertbanz for posting your note. I too was having issues with 188.8.131.52 when reattaching Windows 7 computers to my homegroup. Had to hardwire the laptops to rejoin the group. I was then able to print over WiFi.
I just down graded the Instant to 184.108.40.206 and was able to rejoin my homegroup successfully.
10-07-2012 11:31 PM
I can report that IPv6 still does not work in 220.127.116.11-18.104.22.168_35320.
Is IPv6 on Instant tested by Aruba before each software release? It is late 2012 and IPv6 should, IMHO, be considered a critical feature that can not be ignored for several versions. And I know that Aruba has been aware of this problem for several months now.
It would be great if we can get an offical response from Aruba on this.