My setup is as follows.
Two Morse Micro HaLow Routers.
One configured to AP running a DHCP server.
One configured to STA trying to connect to the AP.
AP: 192.168.1.1 and eth access with 10.42.0.1
STA: waiting for connection from AP eventually got 192.168.1.168, laptop connected over eth eventually got 192.168.1.213
Was trying to debug why the station wasn’t connecting and wasn’t giving an IP to my laptop to connect locally to the stations web ui.
connected UART to the station and observed the following messages repeatedly being reported:
what do these error messages mean?
and is there a better way to configure this where a station can both route traffic from the halow link to ethernet and use the APs DHCP, while also still allowing a local connection to access the station over ethernet while it does not have an ip assigned yet from the DHCP on the AP.
I would like to dig a bit further to help speed up your association times, or otherwise identify exactly what’s going on. Can you specify which Morse Micro HaLow Routers are being used? Are they our EKH03 or EKH01 evaluation kits? Can you also confirm which version of the firmware is being used, and the region used?
In some older versions of the driver/firmware, if the board calibration file disabled some channels (eg, to meet regulatory requirements), then driver would throw these errors as it performs scanning. They shouldn’t impact functionality if the AP is operating on a channel the station supports.
Running morse_cli -i wlan0 version will return the version of the chip firmware.
Assuming this is one of our evaluation kits running OpenWrt, there are more complex ways of configuring the station with alias interfaces on the network containing the ethernet interface to enable what you’re attempting. We don’t configure these on the evaluation kits by default as it does add to the overall complexity in the flexibility of modes we try to support.
For example, when using a station in a bridged mode you could add the following to /etc/config/network
Then you should be able to configure your laptop for a static IP address in the 192.168.2.x range and connect to the station. Alternatively, you can also use IPv6 link local addresses to connect to the devices.
Another approach, if you’re using an EKH01 or EKH03, is to select ‘Extender’ rather than ‘Bridge’ on the Traffic Mode page of the wizard. This is not ideal, because you will likely have ‘double-NAT’, but should let you easily access the station before it’s connected to the AP.
I ran another test and the station didn’t connect to the AP for over an hour. After I power cycled the station (unintentionally) it did connect, but it’s not very reliable.
Can you specify which Morse Micro HaLow Routers are being used? Are they our EKH03 or EKH01 evaluation kits?
These are the EKH03 evaluation kits.
Can you also confirm which version of the firmware is being used, and the region used?
This is in the US region.
I ran morse_cli -i wlan0 version as suggested and this is what I got for the ap:
Question: how can I attach logs to my posts? I have the system and the kernel logs from the station and the ssh and uart logs from the ap and station, respectively as I was connected to it.
Question: how can I attach logs to my posts? I have the system and the kernel logs from the station and the ssh and uart logs from the ap and station, respectively as I was connected to it.
I’ve just bumped you out of the “new user” tier, so you should be able to attach text files or archives to a post.
Thanks for all the information you’ve provided so far! Judging from the error log in your first post, this is likely going to be something radio specific, preventing the chip from changing channel. System boot logs will be helpful in determining the right calibration file is being used.
But there is no entry for it in the DHCP leases.
from the configuration and ifconfig output you have shown me, I am reminded of an old bug which would have affected the 2.4.4 release.
When the AP is configured as a standalone AP (ie, the Ethernet and HaLow networks are separate), a bridged station is not able to communicate with any of the network services configured on the HaLow network.
The solution to this is to create a bridge device for the ahwlan network to bond the wlan0 and wlan0.sta1 network interfaces automatically.
Can you run the following:
uci add network device
uci set network.@device[-1].name='br-halow'
uci set network.@device[-1].type='bridge'
uci set network.ahwlan.device='br-halow'
uci commit
reload_config
and see if that improves the station, and your laptops, ability to acquire a DHCP lease after association?
As mentioned, I don’t think this will resolve the long association times, as they look like a deeper problem. Logs should tell me more about these.
Hey @ajudge here are the logs I had collected. Only have the kernel and system logs from the AP. Can set this test up again and collect them from Station as well.
One thing that’s not clear to me is whether this issue is something happening on the AP or the station or if it’s a combination of the two.
I tried using the morse_cli to understand what’s happening on the morse chip but could not find anything that struck me as being an issue.
Apologies for the delay! We have not been able to reproduce the morse_mac_set_channel error messages you are seeing internally on freshly produced devices. Are you using the power supplies which came with the devices? Otherwise, I worry there may be some hardware failure occurring here.
Can you also share the output of iw reg get?
Did you try the creation of the bridge device on the ahwlan interface to verify if it improved some of the communication problems? It likely won’t resolve the set_channel issues, but should improve any connectivity issues you mentioned after authentication does succeed.
We’re still trying to reproduce this internally. Will definitely reply back in this thread when we are able to reproduce it.
1.10 firmware would also be consistent with the 2.4.4 release.
@Luisschubert We’re in the middle of a transition in how we distribute our software, but for the moment you can find updated images for the EKH03 in the Customer Portal. You may need to register to get access there, but that should be approved quickly.
Thanks for looking into this. For the power supply I have been using this solar power bank: Solar Charger, 38800mAh Portable Solar Power Bank and also this BK Precision 1550 as well as the power supply that came with the EKH03. I haven’t done any testing if it happens only on some of them. But this is an interesting point I’ll investigate further.
I have been able to resolve it most times with power cycling the station and AP but no clear pattern that I have been able to observe on what fixes it.
Do you have any specific suggestions on what the power/ current requirements are that need to be met for the device to operate normally. I do plan on powering it directly off of a battery so will not be using the power supply that shipped with the kit. When I was using the bk precision I saw current draws of around 0.28A at “idle” and 0.4A at “max duty”.
