@biomed32uk I tried for weeks to get Wireguard working, I'm pretty sure it's flat-out broken. I had to resort to throwing out my ER605 and returning to using OPNsense as my router and handling everything through it.

It feels like everything Omada-related is in perpetual beta at best. I have tons of features in my SDN that I can't use because none of the devices have been updated to support them, despite the fact, all those devices were purchased in the last 6 months. It makes no sense that these are sold as business products. I work for a very large software company and if we released our products like this, our customers would revolt.

I agree, I am also convinced it does not work properly, think it's very early days yet and is not to be depended on yet.

The release of software / firmware does seem particularly disjointed where there are inter dependancies.

jaymac1 wrote

  @biomed32uk I tried for weeks to get Wireguard working, I'm pretty sure it's flat-out broken. I had to resort to throwing out my ER605 and returning to using OPNsense as my router and handling everything through it.

It feels like everything Omada-related is in perpetual beta at best. I have tons of features in my SDN that I can't use because none of the devices have been updated to support them, despite the fact, all those devices were purchased in the last 6 months. It makes no sense that these are sold as business products. I work for a very large software company and if we released our products like this, our customers would revolt.

  @jaymac1   Ohh so true - we have resorted back to OPNsense, using OC200 to control switches & EAP's.  Future projects look like a switch back to OPNsense / Ubiquity UniFi kit.  At TP-Links rate of development it will be several years before the system is really usable

If I leave my android device on my local Wifi pings to its wireguard IP work absolutely fine

If I then disable the WiFi so it goes over to the cellular data the tunnel remains connected and shows the public IP in the dashboard, however the connection is then unreliable, I have tried this on two devices now - iOS and Android and they do the same. Seems as soon as WireGuard has to cross LAN to WAN in the router it breaks ?.

I'll draw out y network later on but don't think it is anything my side as such, I have tried various IP addresses for the wireguard tunnel, Class A, B and C with no difference made. Nothing is overlapping and should route.

best regards.