It seems to me that the preposition usage corresponds to the boarding language pretty closely. Where “on” sounds most natural is also where “boarding” seems most appropriate.

Here is one linguist’s take, with proposed usage cases at the end: http://itre.cis.upenn.edu/~myl/languagelog/archives/005224.html

The schedule/route condition makes a lot of sense to me. Consider a bus converted to personal use as an rv:

“I boarded my bus and drove to the mountains” is a valid English sentence, but it sounds odd to me. But if it’s still a regular bus and drove->rode it works.

“I drove to the mountains in my bus” sounds better. Same vehicle as a city/school bus, different context. Change to a regular bus and drove->rode doesn’t sound right without also changing “in my” to “on the”.

Ah, ok

Do they? I don’t see any nel0x PRs. I moved away from it out of an abundance of caution.

The movie Matewan (1987) is a good look at some of the conditions and events leading up. It’s worth a watch.

So you have a single mobile device connecting via wg, correct? Not a second network?

If so the only configuration you should need on the router are firewall rules to allow forwarding from wg to lan. I am guessing that’s what the second step in the GL-iNet help accomplishes. That’s what I would recommend trying.

If I was doing this on “normal” OpenWRT I would create a firewall zone wg, and allow traffic to/from it and lan.

On the client device you should be good to go without changes if AllowedIPs is set to 0.0.0.0/, ::/0 (sending all traffic through wg).

That rule is supposed to be set on the “server” at the other end of the wg connection, using its own wg address as gateway. Not on the router for the lan you’re trying to access. That seems like a pretty easy mistake to make given that documentation.

You could try a short reset of just the network configuration. Hold reset for like 5 seconds. Might need to do a full reset (10+ seconds) if that doesn’t get you back in.

I use Dumbass in a similar vein. But maybe something like Bro would be more neutral.

Cool, thanks. I’ll take a look.

I have heard that. Can it be given run conditions, like only on wifi, and respecting the Android battery saving setting?

My phone has an always on split tunnel VPN to home, so the other sync devices are always accessible. Without the Syncthing-Fork run conditions it chews through mobile data and battery.

Same here. It was already a little bit concerning that I was relying on a smaller fork to get syncthing on Android. It was on my to do list to figure out options. Now it’s at the top of the list, and I’m not doing updates for the time being on Android. That’s almost the entirety of my reliance on syncthing - phone to PC sync. I don’t really need it that much for sync between PCs.

To be fair it wasn’t a random banana.

It was this specific banana.

Just throwing out more ideas:

Is there a CPU spike on the VPS?

Anything weird about Wireguard on either end? Using kernel mode WG everywhere and not a user mode version, right?

As a test I would be inclined to try a very small mtu to see if it makes a difference. 1280 is a failsafe that I use when on unknown networks and trying to wg out.

Maybe try with a smaller packet size, like 1KB which I think is -l 1K

Are you specifying bandwidth (-b) on the iperf UDP test? It defaults to 1M if I recall correctly, which would explain the result.

If not, try -b 10M or -b 0 for unlimited (the behavior used for TCP).

I’m doing this on a couple of machines. Only running NFS, Plex (looking at a Jellyfin migration soon), Home Assistant, LibreNMS and some really small other stuff. Not using VMs or LXC due to low-end hardware (pi and older tiny pc). Not using containers due to lack of experience with it and a little discomfort with the central daemon model of Docker, running containers built by people I don’t know.

The migration path I’m working on for myself is changing to Podman quadlets for rootless, more isolation between containers, and the benefits of management and updates via Systemd. So far my testing for that migration has been slow due to other projects. I’ll probably get it rolling on Debian 13 soon.

What number am I thinking of?

I’m using Mikrotik and Ruckus. Would recommend both. I like that they are both at the level of reliability that I don’t think about them at all for months at a time. I update quarterly or less and they require no other attention from me. They also work well with my centralized data collection and alerting via LibreNMS.

OPNSense would be high on my list of alternatives when I reevaluate next time. And all Mikrotik would be a good option for me as well. Their Wi-Fi gear is not as strong as Ruckus or Ubiquiti, but they are super solid.

The Unifi ecosystem is a bit too centralized for me. I don’t want to create an account in order to use the hardware.

Matewan (1987) is a good movie covering aspects of this story. Great cast and an engaging story. The cinematography won an Oscar.

We still quote this game in our house at random moments. “Willie know what to do!” and “Klayman, up here!”