I have my halow link 2 configured like this, (option 2) however I also want to have the upstream link be my 2.4ghz wifi network so I can my halow is portable.
If I use option three, I can’t access the devices that are connecting to my halow client from my home network.
Is there a way to do what I’m trying to do?
Hi @Kenbsherman
We don’t expose an option for this in the Wizard as it does require your upstream 2.4 GHz AP support “WDS” (4 address mode) in the same way it is implemented in OpenWrt. So your mileage may vary.
However, it is possible to enable this.
You want to configure the 2.4 GHz interface as Client (WDS) and put it in the same “network” as your HaLow AP interface (which should be configured as Access Point (WDS).
Easiest way to do this is to start with “Wi-Fi HaLow device will get an IP on your existing router’s network” and hit the “Save” button (rather than Save & Apply). This will stage the changes but not commit them.
You can then go into Advanced Config → Network → Wireless and “Edit” the interface under MediaTek MT7603E 802.11b/g/n. Configure it as Client (WDS), set your SSID, and set the PSK in the Wireless Security tab. Make sure to add this interface to the “wlan” Network, which is the network your HaLow AP is created on.
Once you’re done here, hit Save & Apply.
Hi @ajudge ,
It doesn’t look like WDS isn’t an option on the 2.4ghz AP I’d like to connect to.
What am trying to do is use a web browser to reach a halow client device on the halow network with a web browser http://x.x.x.x:8889/stream ,from say a laptop on my
I have a raspberry pi with a camera that I’m trying to stream to the outside world. The pi connects fine to the client halow device over it’s 2.4ghz ssi and is then bridged to the halow ap. The pi get’s an ip on the subnet 192.168.4.2/24 and can successfully access google etc.
I was using a pi zero 2 w and had a mesh client and I was able to stream to the outside world on using the halow network, however this was short lived as the pi has died. Unfortunately pi zero 2w’s are out of stock nation wide, so I was able to resurrect my proof of concept project on a pi zero 1w. Unfortunately the pi zero 1w doesnt’ support my vpn and mesh client. Re-supply for pi - zero 2w’s is about six months out, hence trying to find an alternative.
Using the pi zero 1 w, I can reach external ip’s from the pi, I just haven’t been able to find a way to reach the pi from my local network using http://x.x.x.x:8889/stream. I was pretty sure I’d had some success last night after following your instrctions, pi was on my halo net using my halow client using the correct ssid, and I could ping and stream from the local network even using the host name. However I power cycled everything and haven’t been able to stream since.
I haven’t attemped to use a differenct mesh client, namely tailscale yet. Outside of this option is there a recommended approach to doing this?
I’m fine using my ethernet as the uplink as what I’m doing with the pi is proof of concept. If I can get it to stream at the rates I need and the distance, I’ll tackle portablitly later.
I might have found part of my issue of the halow client being assigned an ip on a natted subnet.
I’m using this project GitHub - gtgreenw/Xiao-Halow-to-WiFi-Bridge: Connect to a HaLow network using your 2GHz devices (Phone, Laptop, Computer, etc) with a SeeedStudio Xiao ESP32s3 and Xiao HaLow Backback · GitHub on an ESP32S3 as my client that my raspberry pi connects to.
My pi is always getting in ip of 192.168.4.2, which is coming from the esp32’s halow access point.
The project is using the morse micro sdk and api’s. Is it possible to change by code the behavior so the client doesn’t nat the devices with the sdk? I’d take a stab at changing, I’d just need some guideance on where to start.
The NAT is managed by that example - definitely possible. I’d recommend opening a ticket on that repo if you’d like their help setting up the device as an “AP + bridge” rather than with NAT, for the case where you want the 2.4 wifi device to get the IP addr etc from the Halow gateway rather than the ESP
I was able to add some code to the XIAO halow bridge to port forward tcp traffic on port 8889 to my local network. I’m using mediamtx as my media server and had to make two changes to the configuration to allow it to use webrtc over tcp.
What’s the best way to monitor realtime through put on the halow network?
