Cannot View MM8108-EKH05 Demo HTTP Server

General
1

Hello,

I have one pair of EKH05 and EKH19 boards. I first configured the EKH19 board in AP mode. I am using the EKH05 following the MM8108-EKH05 User Guide. I have downloaded the precompiled files and flashed them using STM32CubeProgrammer. The EKH05 board can respond correctly and establish a connection.

However, I am unable to access the HTTP server at the corresponding IP address, and I also cannot obtain the image information that I expected to see. Could you please help me resolve this issue?

image
image800×415 33.8 KB

image
image800×415 42.8 KB

Thank you.

2

Hi @Ziyao

Would you be able to check if the AP is able to see the web page?

From the Services > Terminal tab (you may have to enable in in the config tab)

Run:

wget -s http://192.168.12.155/index.html 2>&1

If it says ‘Download completed’ the AP can see it so it’s a routing/network issue, if not it’ll likely be on the EKH05’s side.

3

Hi Michael,

I have tried but there is still no reaction.

image
image1026×991 51.7 KB

How could this be? I have follow all the instructions and using the brand new EKs, I am quite confused and please help me out.:melting_face:

4

And I am using this offcial sample from the website

image
image317×323 5.89 KB

5

From the Services > Terminal tab can you try ping the EKH05 to rule out basic networking issues?

ping -c3 192.168.12.155

6

Hi，

Yes, it’s available.

image
image881×790 54.7 KB

7

Hi there, is there any update?

8

Hi,

May I know if this is a hardware issue? Could I try to apply for another new one. My project is urgent and requires me to make it work asap.

Thank you so much for your help!

9

Hi @Ziyao

It seems there might be something funny about the wget implementation on OpenWrt. I am seeing a similar output to you

Connecting to 192.168.12.237:80
(null)                5224  --:--:-- ETA
Connection reset prematurely

It has detected the file size and re-running the command without “spider” mode show’s it can actually reach my EKH05 and download a page.

root@halowlink1-b0af:~# wget http://192.168.12.237/index.html 2>&1
Downloading 'http://192.168.12.237/index.html'
Connecting to 192.168.12.237:80
Writing to 'index.html'

Connection reset prematurely
root@halowlink1-b0af:~# ls -la index.html
-rw-r--r--    1 root     root          5224 Jun  1 12:08 index.html

If you can successfully download the index.html as above, then your issue will be one of routing between your PC and the EKH05 through the AP.

Do you have any other interfaces on your PC in the 192.168.12.0/24 subnet? What is the output of ipconfig on your PC?

10

Hi

image
image923×894 66.5 KB

I try to figure out the reason. But some weried thing happen. I can get 192.168.12.1 but not the 192.168.12.155

Microsoft Windows [Version 10.0.26200.8524]
(c) Microsoft Corporation. All rights reserved.
C:\Windows\System32>route add 192.168.12.0 mask 255.255.255.0 192.168.8.1
 OK!
C:\Windows\System32>ping 192.168.12.155
Pinging 192.168.12.155 with 32 bytes of data:
Reply from 192.168.8.1: Destination port unreachable.
Reply from 192.168.8.1: Destination port unreachable.
Reply from 192.168.8.1: Destination port unreachable.
Reply from 192.168.8.1: Destination port unreachable.
Ping statistics for 192.168.12.155:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
C:\Windows\System32>ping 192.168.12.1
Pinging 192.168.12.1 with 32 bytes of data:
Reply from 192.168.12.1: bytes=32 time<1ms TTL=64
Reply from 192.168.12.1: bytes=32 time<1ms TTL=64
Reply from 192.168.12.1: bytes=32 time<1ms TTL=64
Reply from 192.168.12.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.12.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Windows\System32>

 OpenWrt 23.05.5, Morse-2.9.3
 ---------------------------------------------------------
root@GL-MT3000-dc2:~# ping 192.168.12.155
PING 192.168.12.155 (192.168.12.155): 56 data bytes
64 bytes from 192.168.12.155: seq=0 ttl=255 time=171.013 ms
64 bytes from 192.168.12.155: seq=1 ttl=255 time=190.111 ms
64 bytes from 192.168.12.155: seq=2 ttl=255 time=212.708 ms
64 bytes from 192.168.12.155: seq=3 ttl=255 time=31.864 ms
64 bytes from 192.168.12.155: seq=4 ttl=255 time=55.975 ms
64 bytes from 192.168.12.155: seq=5 ttl=255 time=79.080 ms
64 bytes from 192.168.12.155: seq=6 ttl=255 time=102.959 ms
64 bytes from 192.168.12.155: seq=7 ttl=255 time=127.297 ms
64 bytes from 192.168.12.155: seq=8 ttl=255 time=149.893 ms
64 bytes from 192.168.12.155: seq=9 ttl=255 time=173.753 ms
64 bytes from 192.168.12.155: seq=10 ttl=255 time=197.603 ms
64 bytes from 192.168.12.155: seq=11 ttl=255 time=220.714 ms
64 bytes from 192.168.12.155: seq=12 ttl=255 time=39.868 ms
^C
--- 192.168.12.155 ping statistics ---
14 packets transmitted, 13 packets received, 7% packet loss
round-trip min/avg/max = 31.864/134.833/220.714 ms
root@GL-MT3000-dc2:~#
11

It looks like you’ve selected “None” as the Upstream Network from the Wizard when configuring your GL.iNet. This mode effectively isolates the 192.168.8.0/24 subnet (ethernet) from the 192.168.12.0/24 subnet (HaLow), and is therefore only useful for testing Wi-Fi HaLow in isolation. To make this mode work for what you want to do, you will need to configure firewall rules to enable the static route you’ve configured above to be accepted as an input to the HaLow network. Honestly, this is more complicated than it is worth.

The recommended option in the wizard of the EKH19 is simpler. Just plug your laptop into the LAN port of the GL.iNet router to get an address in the 192.168.12.0/24 subnet.

image
image962×1052 68.2 KB

For your benefit, this is what my home page looks like on my EKH19

image
image1273×1095 69.8 KB