Verified VCDS User
- Aug 14, 2015
- Reaction score
- VCDS Serial number
Thanks for the info, I continue to work on the router and which firmware actually started the problem. I've tried every option I can think of, including running open security but the new versions will not allow ping but the hex-net does get an ip address via dhcp, it shows in my network client list with the correct ip, subnet, dns, default router and wifi network. All of my older 2.4 ghz devices, like my 5 year old nest thermostats, some ring camera's my nest doorbell, etc work on this release and none of them have an issues, just the hex-net. The router is a fairly expensive gaming router, I've open tcp port 10002 and udp 777 with upnp enabled (which should mean I don't need to forward ports but I did it anyway). My fallback on this is just just use in USB mode which works. If it turns out that more people start to report this over time let me know if a fix can be found on the hex-net side. Thanks again.The HN2- interfaces do have a newer wifi module, but it does not support 5GHz and it doesn't universally support all of the wide channel implementations. In generally I would not expect the wifi performance to be very different. However, if the problem here is indeed related to WPA2 changes, there is a remote chance the newer wifi module would handle this differently. Since you are the first person reporting this, I don't know if you would see any practical improvement with an HN2, but my guess would be that it's a long shot, and you would probably be better off finding a different wifi router if that is indeed the problem.
The HN2- interfaces support DoIP for diagnostics on certain newer platforms, but this is currently not required for any diagnostics procedure that we are aware of. You would get the same coverage from your current interface via UDS over CAN.