I’ve got a pair of HaLowLink 2 (JP) and setup one of them as an AP. Firmware is 2.11.13 (latest).
Edgecore EAP112 has a built-in Morse Micro system and a pair were working well as AP-STA configuration.
I tried connecting EAP112 (STA) to HaLowLink 2 (AP).
The radio association seemed good (temporarily) but IP communication didn’t work.
DHCP didn’t work.
By changing the SSID only, the EAP112 connects to another EAP112 (AP) quite well.
Another HaLowLink 2 as STA joins the network without an issue, without changing the AP side at all.
The opposite configuration, i.e., HaLowLink 2 as STA, and EAP112 as AP didn’t work either.
Apologies for the slow reply here. There shouldn’t be any incompatibility between an EAP112 and a HaLowLink hardware wise.
Does the EAP112 give you any visibility into the driver version it is using? The Japanese regulatory has been evolving and there may be instances where certain channels are no longer available.
The radio association seemed good (temporarily)
What do you mean by temporarily here? Did the EAP112 remain associated?
I’ve relocated the HaLowLink 2 (STA, the opposite case) by 3 meters (only) and it’s working well today against EAP112 (AP). I’m using 38 ch w/ 4MHz bandwidth.
I suspect another device is malconfigured or defective, and will try swapping the units.
What do you mean by temporarily here? Did the EAP112 remain associated?
I meant that the radio association seemed all right but unstable, often cause disruptions.
Back to the original question about HaLowLink 2 (AP) vs EAP112 (STA), the configuration seems to have a DHCP or another IP issue.
HaLowLink 2 (STA) has no issue with “this” HaLowLink 2 (AP), but EAP112 fails.
The status on the HaLowLink 2 AP-side looks like the attached image. The client with MAC 0C:BF:74… is EAP112 (STA).
The association looks okay, but DHCP fails
br-wan on EAP112 defaults to 192.168.1.10 (factory default), and IP connection fails even if I set 192.168.14.x on br-wan manually. The same EAP112 connects to another EAP112 (AP mode) successfully by changing the SSID only.
From the screenshots you’ve shared I’m confident the EAP112 is associating correctly.
Unfortunately I don’t have an EAP112 on hand myself to try to reproduce the issue, so I’ll need to ask for any additional logs/configuration.
It sounds like you have console access to the EAP112 so if you could collect the output of
ifconfig
ip route show
morse_cli version
On the HaLowLink2 side, you should be able to enable ssh to get console access, and tcpdump should be pre-installed. I’d love to know if the HL2 is receiving the DHCP requests from the EAP112 and if it is responding. tcpdump -i wlan0 -w capture.pcap would be helpful.
admin@EAP112:~# morse_cli version
Morse_cli Version: rel_1_11_3_2024_Mar_28
NL80211, code -95: Error callback called
NL80211, code -10: Failed to rcvmsgs
Get firmware version failed (-10)
I’ve got it work after switching the Network Mode once to “router’s network” and back to “local network”. I didn’t change anything on the EAP112 (STA) side.
It’s quite mysterious that EAP112 (STA) failed and HaLowLink 2 (STA) had no issue earlier.
I’ve failed to track down the real cause. There might have been a problem in dhcpd caching?
I’ll continue testing for a while anyway.
Thanks for the command line for checking the version.
Interesting.
I’ll check internally if there are any known issues communicating between a device with a 1.11 driver version and a device with a 1.17 driver version.
