Options > Test > Net can't find hex-net

   #21  

tmoe

Verified VCDS User
Verified
Joined
Aug 14, 2015
Messages
43
Reaction score
15
Location
USA
VCDS Serial number
C?ID=109772
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.
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.
 
   #22  

tmoe

Verified VCDS User
Verified
Joined
Aug 14, 2015
Messages
43
Reaction score
15
Location
USA
VCDS Serial number
C?ID=109772
Update: Both of my Asus routers with current firmware do not work with my original version hex-next but I found a workaround which was to enable my guest 2.4 ghz network which has a specific option to allow or not allow intranet access and if I enable intranet access (Shaun suggestion) and use WPA/WPA2 Personal security/authentication and the hex-net works! The intranet access option is not available for the standard networks. I did test quite a few versions of firmware and ability to work with hex-net, results below:

RT-AX86U - did not work with standard 2.4 ghz wifi
3.0.0.4.386.45934
3.0.0.4.386.45898
3.0.0.4.386.45375
3.0.0.4.386.44130

Merlin version - worked
RT-AX86U_386.3_2_cferom_pureubi

Stopped working with
RT-AX86U_386.4_alpha2-g23082e2452_cferom_pureubi
roll - up of all all Asus released firmware

RT-AX82U also tested

Does not work with
3.0.0.4.386.45934
3.0.0.4.386.45898
3.0.0.4.386.45375
3.0.0.4.386.43588
3.0.0.4.386.43129
 
   #23  

gawied

Developer
VCDS Distributor
Joined
Sep 3, 2014
Messages
46
Reaction score
117
Location
South Africa
Hi tmoe

We had the same issues with an Asus RT-AX55 router. Everything worked fine with the old firmware 3.0.0.4.386.9939 until we upgraded to 3.0.0.4.386.45934.

We eventually solved it by doing a factory reset - restoring to factory defaults. Seems like the configuration was not upgraded correctly between versions and it might have stuffed up some setting which resulted in this weird behaviour.

I know you got a working solution at the moment, but keep this in mind if you run into trouble again.

Hope this helps,
Gawie
 
Top