![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
That wouldn’t help with deep packet inspection but only those firewalls too lazy to check what’s actually being sent there. Even then I doubt it would work because WireGuard uses UDP, not TCP.
That wouldn’t help with deep packet inspection but only those firewalls too lazy to check what’s actually being sent there. Even then I doubt it would work because WireGuard uses UDP, not TCP.
Storj bucket synced with rclone
. It’s also great for using as a “cloud NAS.”
Sidestepping the nightmare everyone else is bringing up: could they containerize their workloads? To me it’d sound simpler to just give them access to a Docker instance or Kubernetes on your machine.
Upvoted for “not GoDaddy.” GoDaddy is by far the worst tech company I’ve ever dealt with, and I’m being generous calling them a tech company.
CGNAT, A records, usual ports blocked by default
Aussie Internet sounds like a real shitshow
Glad to hear! 🎉
I’m guessing that both routers are running DHCP and/or running NAT at the same time. You need only one to do all that (the one attached to the WAN/Internet) and the other needs to act as a switch only (usually called access point mode).
Not sure about all the mesh stuff, but traditionally you’d switch off all the routing functions of the second router and connect it to the other router via the LAN ports. Again, DHCP and actual routing would need to be turned off on the “secondary” routers.
If all these “routers” (really we should be calling them access points to distinguish which function we’re referencing) are part of the same mesh networking system I’d imagine they’d take care of these issues on their own though, so more details about the network topology would be necessary to be helpful.
GoDaddy is known to be a terrible company for a multitude of reasons (both technical and non-).
My last experience with them involved completely migrating a client away from them as they were paying significantly more than I’d ever seen for the services they were using.
For the client, what drove them to finally dump GoDaddy was their email server only pushing new messages every 10 minutes (even on a manual fetch); not good in an email-heavy industry.
I couldn’t even get DNSSEC working at the time and if I remember correctly you had to pay more for AAAA records — something crazy like that.
I’ve got a base64 encoded URL to that video in one of my DNS records somewhere. I think it’s called “secret” and it’s a TXT record.
I imagine you’d probably put Flask behind nginx. At least in Ruby (another interpreted language) I don’t want all requests hitting the framework.
Lol, I wonder what terrible programming language you’re working in. Why would you need x86 to host a website?
OP wants to circumvent deep packet inspection.