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

[tmoe]

I've owned my hex net for years now and I've been able to use via IP realizably but after my last update I haven't been able to test the hex-net via my local IP and I'm not sure what it the issue is. I have ports open on my router tcp 10002 and udp 777, I see the device in my client list at the specific ip addresss that I've assigned to it in dhcp but vcds just can't find it using vcds 21.10 or 21.9. I've checked my router and Windows 10 laptop and I can ping test all other devices on my network but I can not ping test the hex-net which means it's not port tcp 10002 or udp 777 related, it also does not respond to a web request to port 80 on my internal network. If I use the hex-net net hn1-008216 it will respond.

here is my current firmware:

CB:0.4607
FW:0257
CFB:010
BL:0.28
DS:30000060

 

[Shaun]

Plug in the interface and check the main screen of VCIConfig, does it show the interface connected to your network and at the IP address you expect?

 

[tmoe]

It does, it shows the same ip address I've assigned via dhcp, that's what's odd. All of my other devices respond via ping on the network but not the hex-net. I'm baffled.

 

[Shaun]

Well then the next thing I would check is your PC network settings. Make sure it's on the same network and not a 5GHz or public access type wifi that might be a different network or something.

 

[tmoe]

Both devices on same 2.4 ghz network, windows 10 setting if private with sharing, I did have a windows 10 upgrade last week so it could be that but I'm have the same issue on 2 different laptops. What's odd is the laptop and hex will talk on hex net network but not the other way around. I know that would tend to indicate it's my network but the lack of ping, which is the most basic service or web browser port 80 not responding doesn't make sense. It could also be router related but I would think I would have ping and port 80 web page issues with other devices on the network. One other odd note, when I go into options>config config finds the hex net and will check for updates, so how is that possible on the same network that the hex net will not respond to ping? Baffling

 

[Uwe]

One other odd note, when I go into options>config config finds the hex net and will check for updates

Because you have the HEX-NET plugged into USB at that point? The VCIConfig utility only works via USB, not via WiFi.

I'm baffled.

I'm a bit puzzled as well. Process of elimination here.

Is your phone on the same network? Open a browser on your phone and point it at the HEX-NET's IP, or get a network scanner app for it. Can your phone find the HEX-NET?

Set up a hotspot on your phone. Use VCIConfig teach the HEX-NET how to connect to that hotspot. Connect your PC to that hotspot as well. Can your PC now talk to the HEX-NET?

-Uwe-

 

[tmoe]

Many thanks for the very prompt responses. I'll give the phone a try tomorrow, I'm starting to believe its router related, too many things are working on the hex-net.

 

[tmoe]

Well as it turns out, it was the router, an Asus RT-AX86u which had new firmware installed last week to address security threats FW_RT_AX86U_300438645934. I back rev'd to an older version and its working now. While I found a fix it's not a fix that's ideal, not sure what my next step is as I like to keep my router update on security patches. I guess the simple fix is use the USB cable but that's not great and defeats the purpose of the hex-net. So the question: why would all of my other ip devices work on that firmware; nas server, my ring camera's, nest thermostat's, gaming devices and many more but not my hex-net? On the ross-tech side does the new version of hex-net handle networking different? If so maybe I should upgrade and see of that works. Your thoughts would be appreciated. Once again thanks for the suggestions.

 

[Hawkeye9723]

Does the router have an option for Wireless client isolation? I've seen that setting on some of the wireless access points I've configured. It keeps wireless clients from talking directly to each other, and that could be the issue.

 

[tmoe]

Yes, the router does have that option but it is definitely not set. The only change to go from not working to working was to back rev the router firmware. My concern is that even though the hex net shows up in my lan network at the ip address that I assign, dns, sub net are correct that I couldn't ping the device or browse to the id address on port 80 to open the web browser on the hex net. I'm not having any other issues on my lan with other lan devices and ip services. The router also run trendmicro security software and it could be that the hex net is somehow identified as a security risk and locked out but I didn't see that in my logs, that's definitely a possibility as well. I guess I was just curious if the newer hex net would behave the same way as I have a fairly old hex-net.

 

[Uwe]

I guess I was just curious if the newer hex net would behave the same way as I have a fairly old hex-net.

I doubt the newer one would any different. It does use a newer WiFi module, but the general behavior is going to be the same.

-Uwe-

 

[VRS2]

I was interested to read Tmoe's problem with wireless connectivity with his Hex-Net. I have experience exactly the same with a recent update of the software. It was a headache to pin diown, but I solved it by ununstalling my AV software. I tried simply just stopping the antivirus, but that didn't work. I suspect there is a resident module in the software that stays operational even if the software is stopped. I noticed that both MalwareBytes and Avast caused the problem so it might be more widespread than just those two pieces of software.

 

[tmoe]

I was interested to read Tmoe's problem with wireless connectivity with his Hex-Net. I have experience exactly the same with a recent update of the software. It was a headache to pin diown, but I solved it by ununstalling my AV software. I tried simply just stopping the antivirus, but that didn't work. I suspect there is a resident module in the software that stays operational even if the software is stopped. I noticed that both MalwareBytes and Avast caused the problem so it might be more widespread than just those two pieces of software.

Interesting, I think it might have something to do with recent changes to address CVE's that have been posted this year. I've spent all morning changing the router software to pinpoint when ping stops working. All I have to do is back rev my router software to the beginning of the year and the hex-net works, once I apply any of the recent updates there have been quite a few this year many relating to CVE's (Common Vulnerabilities and Exposures) and the hex-net stops working. So for me I've taken my anti-virus off my laptop, (turned off Microsoft defender) during my tests to make sure the only impact is the router software. As it stands now I can't make the hex-net work with current firmware without a USB connection.

 

[Shaun]

Does your router have a wifi b\g compatibility mode that disables n and ac? I would try playing around with those kind of settings as well.

 

[tmoe]

Does your router have a wifi b\g compatibility mode that disables n and ac? I would try playing around with those kind of settings as well.

Yes, I enabled legacy mode only which uses only one channel for b\g communications. All AX features have been disabled. I also have a RT-AX82u which has both 2.4 and 5.0 radio's I've connected to that using the 2.4 radio legacy mode with the same result. What I haven't done is disable AX mode on my 5.0 radio just to test, basically make the router a b/g/n router and see what happens. I'm also going let dhcp assign ip and remove static address. I'm still trying as many things as I can. Done for the day though, have work to do :-)

 

[VRS2]

That's very interesting. Clearly it isn't just security software affecting Hex-Net. I agreee to let the DHCP be handled automatically. Best bet is to get everything back to as standard config as you can, as you appear to be doing. If it then works, re-introduce one thing at a time, starting with the thing you consider most important to your set-up and keep going until you encounter the culprit. As others contribute any findings they have experienced, it will help build a picture for the developers as to what is happening. Going b/g/n is best place to start. Bear in mind only the 2.4 GHz radio is relevant to Hex-Net as far as I'm aware. I've never had a connection on 5GHz.

 

[Uwe]

Bear in mind only the 2.4 GHz radio is relevant to Hex-Net as far as I'm aware. I've never had a connection on 5GHz.

That's correct, the HEX-NET doesn't have any 5 GHz capabilities. That said, I've used it on my networks with the laptop on a 5 GHz channel and the HEX-NET on 2.4 without any issues.

-Uwe-

 

[PetrolDave]

I noticed that both MalwareBytes and Avast caused the problem so it might be more widespread than just those two pieces of software.

Interesting, seems the problems with Malwarebytes and Avast are not universal since I run both Malwarebytes and Avast on the PC I use for VCDS (currently and on the previous PC) and have no problems.

 

[tmoe]

Does your router have a wifi b\g compatibility mode that disables n and ac? I would try playing around with those kind of settings as well.

One last thing, sometime this year there was a CVE security risk that was addressed related to WPA/2 man in the middle attacks, I've been looking for the specific patch and when that update was released as I'm thinking that "could" be part of the problem. I can't prove it but it sound reasonable as wifi drivers in the hex-net are fairly old 2.4 b/g and maybe Asus didn't take those into account in their fix. Does the new hex-net only use b/g or does it add 5.0 ghz or b/g/n? just curious.

Does your router have a wifi b\g compatibility mode that disables n and ac? I would try playing around with those kind of settings as well.

Shaun - I'm curious what wifi standards does the newer Hex-Net support? Are there any other features that might be worth upgraded to, I thought it does a better job supporting the new EV VAG models?

 

[Shaun]

Shaun - I'm curious what wifi standards does the newer Hex-Net support?

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.

Are there any other features that might be worth upgraded to, I thought it does a better job supporting the new EV VAG models?

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.