HA2NON
sharkrf.link forwards your browser to the OS2's local IP address, but the OS2 can only report it's local IP address to the sharkrf.link service if it has a working internet access.
What you can test is to connect to the exact same network with your browser device (phone/tablet/computer) as the OS2 (to the Huawei router), and try to open the web interface by entering the OS2's IP address to the browser. You can find out the IP address assigned to the OS2 on the router's web interface (look at the DHCP clients list). Does the web interface work this way? If not, then maybe Wi-Fi client isolation is turned on, in this case turn it off and retry.
HB3XRN
I tested already from the same network.
the web interface is inaccessible.
"Wi-Fi client isolation" is perhaps "AP isolation" in Huawei.
This function is disabled and no connection possible with Openspot.
HA2NON
Then the openSPOT2's access is blocked on the IP level. Try turning off any firewall or MAC filtering or limiting in the router. Also enter the "net" command (without the double quotation marks) on the openSPOT2 USB serial console and post the output here. You can find out more about the USB serial console in the user manual.
HB3XRN
there are no firewalls, MAC filtering or limitation activated.
here is the return of the -net command
sercon: net config
hostname: openspot2
regdom: 1
mac: E8:2A:44:5F:0D:6E (orig: E8:2A:44:5F:0D:6E)
ap ssid: openSPOT2 AP (E8:2A:44:5F:0D:6F ch11)
ap key:
ap mode: 0
pwrsaving: 0
ssid1: HUAWEIopenspot (00:00:00:00:00:00)
key1: *************
act ssid: HUAWEIopenspot (4C:D1:A1:46:15:C7 ch11 -75dBm)
ip mode: dhcp
act ip: 192.168.10.102 (link up)
mask: 255.255.255.0
gw: 192.168.10.1
dns1: 192.168.10.1
dns2: 0.0.0.0
HA2NON
The net command output shows that the openSPOT2 is connected successfully to the Wi-Fi network and has acquired the IP address 192.168.10.102 from the router. If you connect to this same Wi-Fi network (HUAWEIopenspot) with your browser device (phone/tablet/computer) then you'll be able to open the web interface on IP address 192.168.10.102 (if there is no Wi-Fi client isolation or other blocking).
HB3XRN
Yes but no ...
Unable to connect, via IP or Sharkrf.link.
Whether with my laptop or my iPad.
It works with WEP.
I do not ping from laptop with 192.168.10.102
What is the connection port of the web interface?
HA2NON
80
HB3XRN
I tried with a static DHCP, always the same.
here a log the connection extracted from the console.
Maybe you see something
sercon: log on
homebrew: init reconnect
homebrew: initializing connection
homebrew: using main server 128.65.196.21:62030 pass: ******* id: *********
homebrew: connecting
homebrew: sending login
httpcln: img.sharkrf.com resolve error
nvmm: verinfo check failed
nvmm: net check
aprs: getaddrinfo rotate.aprs2.net error
aprs: uninitialized
homebrew: init reconnect
homebrew: initializing connection
homebrew: backup server toggle timeout, trying the backup server next time
homebrew: invalid backup server
homebrew: using main server 128.65.196.21:62030 pass: ******* id: *******
homebrew: connecting
homebrew: sending login
httpcln: connectivitycheck.gstatic.com resolve error
nvmm: net check failed
spk: starting voice announcement
spk: playing locally: OSINUN
spk: loading code pair OS
nvmm-csd: looking up id 9 type 0
nvmm-csd: dmr ids 9 call "Local or Reflector" name "" city "" state "" country " "
nvmm: downloading verinfo
aprs: getaddrinfo rotate.aprs2.net error
aprs: uninitialized
spk: loading code pair IN
spk: loading code pair UN
spk: sending terminator
nvmm-csd: looking up id 9 type 0
nvmm-csd: dmr ids 9 call "Local or Reflector" name "" city "" state "" country " "
homebrew: init reconnect
homebrew: initializing connection
homebrew: invalid backup server
homebrew: using main server 128.65.196.21:62030 pass: ******* id: *******
homebrew: connecting
homebrew: sending login
httpcln: img.sharkrf.com resolve error
nvmm: verinfo check retry 1/2
nvmm: net check
aprs: getaddrinfo rotate.aprs2.net error
aprs: uninitialized
homebrew: init reconnect
homebrew: initializing connection
homebrew: invalid backup server
homebrew: using main server 128.65.196.21:62030 pass: ******* id: *******
homebrew: connecting
homebrew: sending login
httpcln: connectivitycheck.gstatic.com resolve error
nvmm: net check retry 1/2
aprs: getaddrinfo rotate.aprs2.net error
aprs: uninitialized
homebrew: init reconnect
homebrew: initializing connection
homebrew: backup server toggle timeout, trying the main server next time
homebrew: using main server 128.65.196.21:62030 pass: ******* id: *******
homebrew: connecting
homebrew: sending login
nvmm: downloading verinfo
logaprs: getaddrinfo rotate.aprs2.net error
aprs: uninitialized
homebrew: init reconnect
homebrew: initializing connection
homebrew: using main server 128.65.196.21:62030 pass: ******* id: *******
homebrew: connecting
homebrew: sending login
httpcln: img.sharkrf.com resolve error
nvmm: verinfo check failed
nvmm: net check
aprs: getaddrinfo rotate.aprs2.net error
aprs: uninitialized
homebrew: init reconnect
homebrew: initializing connection
homebrew: using main server 128.65.196.21:62030 pass: ******* id: *******
homebrew: connecting
homebrew: sending login
httpcln: connectivitycheck.gstatic.com resolve error
nvmm: net check failed
aprs: getaddrinfo rotate.aprs2.net error
aprs: uninitialized
spk: starting voice announcement
spk: playing locally: OSINUN
spk: loading code pair OS
nvmm-csd: looking up id 9 type 0
nvmm-csd: dmr ids 9 call "Local or Reflector" name "" city "" state "" country " "
spk: loading code pair IN
spk: loading code pair UN
nvmm: downloading verinfo
sercon: log off
HA2NON
Sadly the log shows nothing about the errror - the OS2 can't reach the internet, but it's connected to the Wi-Fi network. Even DNS resolving does not work (indicated by getaddrinfo errors), these requests should be answered by the router, but it does not answer to them.
bholmer
I just received my new os2 yesterday.
I used the Huawai E5885 since 2018 with my os1 via LAN without any problems. At home via WLAN Extender, on the road via mobile network
Same issue here. No connection. The os2 shows red and blue led and talks "Internet unreachable" via the radio.
When I enter the same SSID and Password in the guest access of my FritzBox 7590 Router or activate the Hotspot of my Samsung S7 everything works fine.
But when I switch the E5885 from WPA to WEP encryption the o2 connects to the hotspot immediately (after new scan and password change in ap mode of course).
The local IP of the E5885 ist 192.168.8.1 7590 runs on 192.168.0.1.
HA2NON
Try enabling DNS server override on the OS2's Network page, IP settings to make the OS2 use 8.8.8.8 as the DNS server instead of the router's DNS server.
OZ9KL
Hi HA2NON.
I have already tried that, as I wrote in one of my first post about this problem:
Re: WiFi problem with Huawei E5885
Post by OZ9KL ยป Sat Mar 30, 2019 8:57 am
Hi HA2NON
I have tried to connect to the Huawei E5885 again, and still don't succeed. This time OP2 actually stays connected, but as I see it, it have some problem to resolve adresses. I have also tried to override DNS adresses in the network configuration with the DNS server from Google. Still same error.
bholmer
I now used the combination OS2 and 5885 for some days during my travel to the HamRadio Exhibition in Friedrichshafen. Everything worked fine as long as I switch the Huawei to WEP encryption.
So I would suggest that the bug is somewhere in a layer handling the WPA2 encryption/decryption below IP Level so that the OS2 cannot issue DNS requests to the Huawei or the Internet. The OS2 is not reachable in the Huawei subnet at all from a client in the same Subnet.
Danie
I've been having the same problem with OS2 and my Huawei E5885 hotspot so seems this is a general issue. I used to have a similar problem with a brand new Netgear hotspot and Waze navigation - after buying the E5885 Waze and everything worked 100% except now the problem with the E5885. Real pity as its a great hotspot but switching to WEP is a worry from a security perspective.
But the good thing is that at least now we have an idea what setting has been causing the problem.
bholmer
Are there any news regarding this issue with the Huawei hotspot?
As all other clients I have work fine with the Huawei hotpot and I doubt that Huawei proceeds and fixes their firmware to make it OS2 compatible I would really appreciate if SharkRF tries to analyze the bug in their firmware.
I really dont want to leave the E5885 on WEP-encryption too Long.
Bert DL9BBH
Danie
Any solution yet?
The WEP workaround works perfectly for me but it is not secure. All my other devices (various phones, laptops, tablets) are all connecting fine the hotspot with WPA.
DM4ZZ
Any solution yet?
The WEP workaround works perfectly for me but it is not secure. All my other devices (various phones, laptops, tablets) are all connecting fine the hotspot with WPA.
now we received this great hotspot and found out that we are facing the same problems because we both use the E5885 for connecting to the mobile network.
is there any change / solution to get it working with WPA2 ?
Danie
I'm beginning to think the E5885 has some problem as mine was also not connecting with Echolink. Went back to my Netgear hotspot which I ditched as it was not connecting with Waze, and thought I'd check the Wifi channel number. The Netgear was defaulting to a non-standard Wifi channel above 11. I forced it to use channel 6 and it now works with Waze, the Openspot2, and Echolink.
Odd issue, but maybe we must look at WiFi channel numbers possibly with the E5885 too.
bholmer
I just tried the different confgurations again. The problem is not related to the WiFi HF channel.
The Huawei 5885 can only be configured to Wifi Channels 5-11 when running as a LTE Hotspot on 2,4 GHz.
When running as a Wifi Extender the channel hops to the Wifi Channel of the host system.
Still the same effekt. In WPA2 mode the openspot2 connects to the huawei (tested on channel 5) but does not connect to any servers. The hotspot is not reachable within the internal network range (default 192.168.40.X)
All other devices in my home connect to the Huawei without problems.
When setting the Huawei to WEP everything is fine.
I assume that the openspot2 does not send correct encrypted data to the Huawei.
Any idea from the programmers to solve this persistent issue without using old WEP encryption?
OZ9KL
Hi Norbert.
I have now got a new router for home use, a Huawei 4G Router 3 Pro. Now i have the exact same problem with this router as I do with the Huawei E5885. The openSPOT2 can't connect to the WiFi. I have tried all your suggestions in this tread, but without any luck. It is exact the same issue as with the E5885. It connects, and the disconnect and you can't reach the web interface. All other 2.4 GHz device I have, connect smoohtly to this new router as they also do to the E5885.
73 de OZ9KL
