Hi,
I want to redistribute a upstream connection on bridge mode from a router to the AP’s 2.4GHz WiFi and the HaLow connection.
So in the end I would want AP’s 2.4GHz and the Stations’s 2.4GHz.
If I’m understanding correctly, you’re looking for a configuration like this:
2.4GHz → EKH03 → HaLow → EKH03 → 2.4GHz
This is close to what we describe in the documentation as a “Virtual Wire”. If you want to use 2.4GHz WiFi for the upstream, though, you’ll need to use NAT on the HaLow AP.
On the AP side, use the configuration wizard to set the device up as an AP, with the upstream network set to “WiFi”, and provide the credentials for your 2.4GHz network.
Then on the STA side configure the station as a Client, select Bridge mode, and enable the 2.4GHz access point.
This is how I want it to look.
| Column 1 | Column 2 | Column 3 | Column 4 | E |
|---|---|---|---|---|
| 2.4Ghz | ||||
| 2.4GHz → | EKH03 → | Halow → | EKH03 → | 2.4GHz |
I want the both EKH03 to send 2.4GHz signals and I also want the first EKH03 send a Halow signal.
This will result in two EKH03 2.4GHz SSIDs
Unfortunately it isn’t possible to use the 2.4GHz radio as STA (for upstream connection) and AP (for clients) simultaneously. This will work using Ethernet for uplink, of course.
1 Like
Hmm, maybe I’m misunderstanding something, but this should work. In fact, it’s one of the configurations the normal wizard sets up, and I run it on my desk on an ekh03. The one thing to be wary of is the AP will be forced to change channel to whatever channel the Client link is using, since it can only support one actual frequency at a time.
Oh, my mistake. I didn’t think that would work. On other devices I’m used to “WiFi-as-WAN” being a cross-band arrangement.
How would I achieve this?
The end result will be two SSIDs from the AP and the client. A HaLow link from the AP to the client as well.
Connecting to both SSIDs provide connection to the internet from a single upstream point.
If you’re using a recent Morse OpenWrt (2.5+ from memory; I’m not sure), this should be configurable in the wizard (or refer to the user guide). Otherwise, you can use luci or uci to set it up, in the same way you would configure any wifi interface.
https://openwrt.org/docs/guide-quick-start/basic_wifi
If you want a better experience with the 2.4GHz, you may want to set up [OpenWrt Wiki] Wifi Roaming
However, since presumably the reason you’re using HaLow is to increase your range beyond 2.4, this may not be that useful.
Now that I’m involved, though, I’m a bit confused as to why you want it. The 2.4 WiFi on the EKH03 doesn’t have a great antenna, so using the HaLow AP EKH03 (which is connected to 2.4) as a 2.4 extender won’t be very useful for additional range, particularly given it will be on the same channel as the uplink. i.e. I would recommend:
Existing AP (mySSID) <---2.4--- EKH03 <--- HaLow --- EKH03 (mySSID) <---2.4--- Client
So that 2.4 devices would switch between your existing AP and the EKH03 at the end of the HaLow link.
I’m trying to do some long range testing with the EKH03. I want to have a upstream from a starlink via WiFi and not ethernet. Then I would like to redistribute it as 2.4GHz and HaLow via the EKH03. So I would have a HaLow SSID and a 2.4GHz SSID.
Using the HaLow SSID, it connect to the 2nd KH03 device and redistribute it as 2.4GHz.
Right, I’m just not sure why you need to redistribute the WiFi via 2.4 on the AP, since at that point you’re in range of the Starlink 2.4 WiFi. It’s fine to do this, I’m just not sure it will be that useful and it will have relatively poor performance, since it will have to use the same channel it’s using for the upstream on its small antenna.
Anyway, let us know if you get blocked setting it up. If you run into troubles, copy your existing /etc/config/network and /etc/config/wireless from the AP so we can debug.