cancel
Showing results for 
Search instead for 
Did you mean: 

zelenev's Posts

Traceroute times or ping times to network routers mean nothing. This has been the case for the past 15 years. Routers route traffic in hardware, however ICMP traffic for the router itself is processed... See more...
Traceroute times or ping times to network routers mean nothing. This has been the case for the past 15 years. Routers route traffic in hardware, however ICMP traffic for the router itself is processed by CPU, and is deprioritized, policed and shaped. It is slower to process than legitimate routed traffic (if it is not dropped at all).
You can, but only up to 63 characters. Once your passwords are 63 characters long (for WPA2), you can only add complexity by increasing the range of characters. Length is indeed more important, but WP... See more...
You can, but only up to 63 characters. Once your passwords are 63 characters long (for WPA2), you can only add complexity by increasing the range of characters. Length is indeed more important, but WPA2 has a limited password length. Working with devices like Nest thermostat that do not offer copy/paste or wireless provisioning of the password is a real challenge with 63-character passwords. Ideally, SSID name should also be uncommon. Here is a formula for password entropy, with L being length abd C being range of characters: log(C) / log(2) * L
@codesplice I disagree. Non-alphanumeric characters significantly increase brute force crack complexity and rainbow table size for cracking WPA2. Of course the ideal approach is using WPA3 across the ... See more...
@codesplice I disagree. Non-alphanumeric characters significantly increase brute force crack complexity and rainbow table size for cracking WPA2. Of course the ideal approach is using WPA3 across the board, but since a lot of legacy devices do not support WPA3, even when the access point supports WPA3, it is usually configured to run in WPA2/WPA3 compatibility mode. Password complexity is the only obstacle to quickly cracking WPA2. WPA2 is cracked. It's insecure. Password/SSID name complexity is the only thing that is keeping WPA2 from following the fate of WEP. Suggestion to downgrade security to be able to play games online cannot be taken seriously in this day of age. The overall 802.11 stack on Stadia controller seems broken and buggy. According to standards, unsupported protocol features should be ignored by incompatible clients, and yet, if you enable 802.11v on SSID, as recommended by many vendors included Apple, it completely prevents the Stadia Controller from joining SSID.
What would be the use case for 1Gbps PHY for CCU? It's not like CCU can consume or produce more than 100Mbps worth if traffic anyway. My guess is 100Mbps is more than enough for CCU needs, consumes le... See more...
What would be the use case for 1Gbps PHY for CCU? It's not like CCU can consume or produce more than 100Mbps worth if traffic anyway. My guess is 100Mbps is more than enough for CCU needs, consumes less power than Gigabit chipsets and is cheaper, so consumers can pay less without sacrificing any functionality.
I don't think there is a way now, but in my opinion, the right way to support it would be allowing USB-C Hubs and USB HID devices like mouse, keyboard, steering wheel, etc to be connected to Chromecas... See more...
I don't think there is a way now, but in my opinion, the right way to support it would be allowing USB-C Hubs and USB HID devices like mouse, keyboard, steering wheel, etc to be connected to Chromecast Controller. Another nice to have option would be support for USB-C Ethernet adapters, so that the controller can be used on wired Ethernet.
Just a follow up, in case someone missed my response in the other thread. I got Stadia Controller to connect to my SSID by disabling 802.11v on SSID - evidently Stadia Controller has some kind of com... See more...
Just a follow up, in case someone missed my response in the other thread. I got Stadia Controller to connect to my SSID by disabling 802.11v on SSID - evidently Stadia Controller has some kind of compatibility issues with this standard.
Unless your AP is using 802.11v and you can easily disable it, I don't think that you'll find a quick fix for your issue here.    To work around connectivity initially I've purchased a Meraki MR24 ... See more...
Unless your AP is using 802.11v and you can easily disable it, I don't think that you'll find a quick fix for your issue here.    To work around connectivity initially I've purchased a Meraki MR24 Access Point from eBay for about $15, and re-flashed it with OpenWRT open source firmware, following the instructions here https://openwrt.org/toh/meraki/mr24 The reflashed AP works well for Stadia Controller connectivity, since it does not have 802.11v enabled by default, but I've discontinued using this AP since I figured out how to get the Stadia Controller working with my main Access Points (instructions in my post above).
I got it figured out.   Stadia Controller is not compatible with IEEE 802.11v. Too bad, since it helps in environment with multiple APs, especially for battery-powered clients that may want to slee... See more...
I got it figured out.   Stadia Controller is not compatible with IEEE 802.11v. Too bad, since it helps in environment with multiple APs, especially for battery-powered clients that may want to sleep.   Once I've disabled 802.11v, on WLC, Stadia Controller connected right away. This explains why it works with OpenWRT - unlike Cisco, it does not have 802.11v enabled by default.
Yes, it does associate, but fails to authenticate.
I have the same problem. Controller would not connect to WiFi on Cisco Access Points protected with WPA2/WPA3. I have dozens of enterprise, consumer and IoT devices, including Google and Nest product... See more...
I have the same problem. Controller would not connect to WiFi on Cisco Access Points protected with WPA2/WPA3. I have dozens of enterprise, consumer and IoT devices, including Google and Nest products that connect to Cisco APs just fine. Controller does connect to an OpenWRT AP with WPA3 and same password, so there is definitely some kind of a bug with controller firmware.   Is there a way to enable WiFi association/authentication logs on controller? The controller must be running a buggy WPA Supplicant or buggy 802.11 driver.
I could not get Stadia controller to work with my Cisco Wireless Access Points. I have tried 3600 (with and without AC module) in standalone and lightweight mode as well as 1850 series in both Mobili... See more...
I could not get Stadia controller to work with my Cisco Wireless Access Points. I have tried 3600 (with and without AC module) in standalone and lightweight mode as well as 1850 series in both Mobility Express and CAPWAP mode and could not get Stadia controller to register to SSIDs with Enhanced open, WPA2-PSK or WPA3- SAE . Open SSIDs with no password or encryption do work. I've tried it on both 8.8 and 8.10 Cisco controller/AP firmware.  Is there anyone who does have Stadia controller working with Cisco Enterprise APs with WPA2-PSK, WPA3-SAE or their combination? I've had to spin up an OpenWRT router with WPA3-SAE SSID on hostapd 2.9 and it did work, but I really want to use my existing redundant Cisco AP infrastructure.  Doing a packet capture to analyze  the differences in WPA RSN IEs is on my to-do list, but I am wondering if anyone has this issue and got it resolved?