Thomas Gfeller

I would greatly appreciate that feature - that we can at least be sure to have the same APKs like Google Play distributes (without having to share all of our...

The migration to Wayland is gaining momentum. Perhaps as an input (I'm not yet very deep into the technical details): Sunshine (https://github.com/LizardByte/Sunshine) uses a KMS screen capture. This is GPU-accelerated,...

> Tailscale's apparently binding to the wrong device. > > What does your route table look like normally, without Tailscale running, and without deleting the default route for Tailscale? >...

It seems that Tailscale binds to 0.0.0.0 - but why is it losing connection with mwan3 and a static IP on wanA? ``` root@gw-di-01:/# netstat -tulpn | grep -E "wireguard|tailscale"...

This is how mwan3 works. It uses multiple routing tables; checkout https://openwrt.org/docs/guide-user/network/wan/multiwan/mwan3. I think tailscale suffers from the same issue like described here: https://github.com/openwrt/packages/issues/16920#issuecomment-946400880. Looking for a workaround or fix...

After further investigation, we believe we've identified the root cause of the issue. Tailscale relies on the "main" routing table, which becomes dysfunctional during a failover event with a static...

We are currently using a workaround through the mwan3.user file to manage this issue. This solution involves dynamically modifying the main routing table and adding a new route with a...

> > We are currently using a workaround through the mwan3.user file to manage this issue. This solution involves dynamically modifying the main routing table and adding a new route...

> @qdrop17 Why do I feel like your issue isn't really related to mwan3? > > Could it be that your static WAN interface is unable to connect to the...

We've migrated to a custom-built failover script. It significantly reduces complexity and ensures Tailscale works flawlessly. While our script handles complete traffic failover, it doesn't support load balancing—though we don't...