Opal Unstable Wifi Repeater Mode

Hi everyone.

I've posted a few months back about issues I was having with my Opal router on FW v.4 and I never really got it resolved, but I just made it work and dealt with the weirdness.

Now however I'm having more issues and it's getting incredibly aggravating. Basically, I will use it in Wifi repeater mode and it will work pretty good for the most part, but it will inconsistently yet regularly just drop the connection from the main Wifi network. It will usually reconnect on its own after a few seconds/minutes, but sometimes I need to go into the admin panel and manually delete the repeater network and add it back.

It's both strange and annoying. I also have other weirdness (that doesn't really affect anything though) such as the timezone keeps desynchronizing and the "Turn off LED" option, while works, doesn't seem to keep to the timings I put in and just randomly turns on and off.

To be clear, the connection to the Opal itself is strong and not flaky at all (although I still don't always see the 5GHz SSID); it's the link between the Opal and the main Wifi that's flaky. But I have other devices on the main Wifi and the connection there is rock solid, so the issue is 100% on the travel router side...

I'm up to date on FW and I've looked at all possible options and everything should work fine. It seems absolutely random.

1 Like

Yes well known, have been strugling with that since I have it.

4.3.x is very unstable ,old 3.216 was better, now the 4.7.2beta is totally different and gives a much better experience

1 Like

Ah perfect I'll give it a try, didn't really keep up with the beta releases.
Thanks!

Well I don't know if the beta would solve my wifi issues, but I encountered a blocking bug with VPN clients that forced me to revert back to stable release unfortunately... :confused:

I'm not testing the VPN yet. Now only just trying to get stable wifi uplink and downlink, and even that fails with all the releases I have tested, Be it failing for different reasons on different versions.

4.3.19 : unstable uplink, firewall reload on disconnect, no DFS connect, failed receiving AMPDU with many MPDU(index>31), enforced roaming with disconnect
4.3.21: unstable uplink, firewall reload on disconnect, but connects to DFS, failed receiving AMPDU with >31 MPDU, enforced roaming with disconnect
4.7.2beta: stable uplink if no BSSID with DFS around, no DFS connect, AMPDU ok, more settings in the GUI, but very very weak wifi TXpower

It's beta, so lets hope the fix comes soon.

2 Likes

There is a new beta version 4.7.2 (dated 2025-04-21)
The prevous (beta2) already solved the TXpower issue. Good connection. But wifi throughput was still dramatic.
Hope this is also solved now.

Update ... after some tests.
Total failure.
5GHz refuses to see DFS channels
So I have to use 2.4GHz uplink
Throughput totally unusable ... between 20 en 54Kbps (Kbps not Mbps) !!!
Cannot even load a test page in the browser
Direct use of the uplink router wifi from the same spot ... 56Mbps (my subscribed line speed)

EDIT
Throughput Improved a lot after full reset of the OPAL

1 Like

@bpwl1 I think it has more broken than just the WiFi, for example, wireguard profile doesn't work, but the same profile on my Pixel has no issues.

I've gone back to 4.3.25 for now

I'm not going back to 4.3.25 , unusable for me.
This 4.7.2beta3 can work good, but it needs tweaking again to get there.
And needs some luck, as sometimes it sucks sometimes it works great.

At least these tweaks are needed:

  • change your host 5GHz wifi to have non-DFS channels (only? Seems to fail if there are also DFS channels for the same SSID))
  • set BSSID lock when connecting the first time (this is the only moment you can set BSSID lock). BSSID roaming will kill TCP sessions. Uplink is down for a while due to involved process restarts. Only have one known SSID in the repeater list for the same reason.
  • don't be surprised to not see the OPAL 5GHz client wifi SSID appear, if uplink is connected to 5GHz. (Yet, It's non-DFS , so there is not a 1 minute (or 10 minutes) mute period)
  • go and reduce or eliminate the MultiWAN checks (any detected uplink glitch will kill all TCP sessions and restart processes with the correponding delays)