That’s really a driver issue from the manufacturer. If ASUS wanted, they could have pushed a proper kernel driver a long time ago. They bet on Windows for some reason though 🤷

https://docs.datalust.co/docs/collecting-docker-container-logs

You have a formatting issue. Solve for that instead of just switching to something else hoping it will get better.

I’m not sure what you mean. You either need to post a lot more details and information about your setup, or you need to read and understand the Tailscale docs.

For all traffic. Tailscale ACLs deny by default. If you’ve never changed them, you need to do that.

You need to adjust your ACLs to allow traffic over Tailscale.

Lazy idiots

And multiple failed consoles since they took it over.

If the application supports an API of some sort, you could run OCR, then send them over API as converted input.

If the apps don’t support them, then no.

If the apps don’t support them, then no.

Lol. Free Speech guy!

If you don’t want to expose port 80 or 443, then just change the ports they are running on. Right now you’re mapping 80/443 in docker, so just change those numbers to something else if you don’t want to use them. The number on the right is the internal service port, and the left of the colon is the port you’re opening to proxy to the port on the left. Adding Caddy does exactly the same thing and serves no purpose except another layer of obfuscation you don’t need.

You’re missing the point of Caddy, and your ports are all wrong. You don’t need it if you’re already exposing ports via Docker to 80/443. Remove Caddy.

Well there’s a lot of stuff happening all at once, and without a bigger picture, I can just give you some basic steps on how I would start debugging:

• Make sure the new untagged interface is actually working as expected (check rx/tx, basic pings)
• Try pinging the devices ONLY from that interface
• Check the configuration of the devices if you can contact them and see what endpoint they think they are supposed to be talking to
• If the are WiFi, make sure that wireless network can be pinged from this new interface (join a laptop and ping back and forth)
• If all else fails, snoop that interface and see what IS traversing it

When you say “VLAN”, are you saying this a tagged network? It sounds like you just have two physical networks here. What is handling the tagging?

Run a livecd of whatever Linux distro you like, and get a USB drive. Store persistent files on the USB stick.

Hence the downvotes.

A solar cluster and whole house battery bank would do this for the majority of the day. You need to hook it into your AC circuit with microinverters, and then have a circuit switch to handoff power back and forth. You’d at least be sure to run off solar during the day.

You could probably use yours for the same, but you need that AC transfer circuit into your breakers. Never do anything like this without an electrician.

If you’re not using some sort of Domain mapping, then the use of the same mount by two different sharing services with different uids is going to break ownership. Doesn’t matter if it’s Synology or anything else.

NFSv4 domain mapping solves this by having the same domain configured in client and server. That’s probably your simplest option. From memory, I do believe Synology DOES set uid for whichever user is authenticated via SMB and NFS though, so are you using two different users for these mounts by chance?

If you don’t want to bother to setup LDAP or domain mapping, then just use SMB and that should solve the problem.

Wiregate itself is just a scripted setup of a handful of things in a docker image. Looks like a mess though, I wouldn’t bother with it.

AmneziaWG is just Wireguard with extra packet obfuscation. You’ll notice a bit more latency while using it, but overall it’s just Wireguard with extra noise in its packet stream to avoid DPI. Will still outperform OpenVPN.