Lol how funny. I was also very into modding the PSP growing up. I had a couple of Pandora batteries. The only reason I caught onto it was because my name is also Alex haha hello fellow Alex!

… are you the DaX from the PSP modding scene?!

Oh boy I went down this same rabbit hole awhile ago. Here is a git repository that will explain why this happens and also offers a fix on how to modify your IP tables to ensure that docker respects the UFW.

Docker and UFW

I prefer ZQ

I’m sorry, I’m either not that person or don’t get the reference

Hey… do yourself a favor and get a CX-3 flight computer. They’re allowed on the written. Don’t worry, you can thank me later 😜

Lol it’s from Narcos. Great show if you haven’t seen it.

Indian guy sitting? That’s Pablo Escobar!

Can you tell me more?

Which switch emulator do you use? I’m pretty savy with Linux and run it on my desktop but haven’t really taken the dive to set any of them up. Metroid has been calling my name lately and I’m thinking it’s now or never. Got any suggestions?

I’m going to suggest something a bit more out there. You can setup this whole thing with NixOS. I have a bunch of docker containers that run as a systemd service, declared with Nix and personally, I like it very much. It’s also got everything else you want but the atomic upgrades are top tier in NixOS.

For example if you want NoIP and Cockpit just add this bit to your configuration.nix

    environment.SystemPackages =[
        pkgs.noip
        pkgs.cockpit
    ];

Adding something like docker or podman is just as easy with a one line like

    virtualisation.docker.enable = true;

There is always a bit of a learning curve when doing anything with Nix but I find the buy in to be worth it. Here’s a blog post about converting docker compose files over to the Nix format. This really isnt necessary as you could just make the systemd service run a oneshot against a docker compose file but this blog has a lot of nice examples.

https://mrupnikm.github.io/en/posts/nix-docker-containers/

If you have any questions please let me know :D

No, you’re right! They have the best name, DERP relays lol. When tailscale can’t find a node over UDP , it switches over to TCP and runs the encrypted traffic through the DERP relays.

It shouldn’t mess with your current routing but if you’re running other VPNs you may run into issues.

After you join the machines to the tailnet, each machine gets a new IP address ( only visible to other machines in the tailnet), by default it’s a 100.x.y.z you can check the tailnet for the device IP.

Now you can keep the port closed on your router and it will still be accessible over the usual lan ip and port. But when you want to access remotely, turn on tailscale and connect using the tailnet IP.

Another cool thing you can do with this setup is turn your home server into an exit node. By default it will only route things that are in the tailnet (100.x.y.z subnet). But if you turn your home server into an exit node you can funnel all your traffic back through the exit node. Instant free VPN back home!

Here you go friend, enjoy! 😁

https://tailscale.com/blog/how-tailscale-works

Unencrypted HTTP can mean that anyone can see your traffic as it passes through their network. Your ISP will see that traffic. If you’re streaming pirated music and you’re in a country that cares about those things, might not go very well. From a security stand point though, you still wouldn’t want to trust the authentication on the open port. A vulnerability may exist that you don’t know about. It’s always better to keep them closed and add another layer or two between your home computer and the public.

Tailscale let’s you tunnel into your home network without opening any ports, and it encrypts the traffic. Much safer way of doing it.

Go on…

What kinda issues are you having? Most of my problems with Nix are solved with overlays or creating a module. Admittedly, in order to do that you still have to know how to fix your issue the usual linux way. Afterall, Nix is more of an abstraction tool IMO; good for replicating something across a ton if devices. If you don’t need that, there’s other distros that work much better out of the box.

Another tip, please be very careful when exposing ports to the public. With docker you’re already mitigating your attack surfaces but an open port allows anyone to make a connection and there are lots of bots out there looking for open ports and vulnerabilities. A good alternative would be to setup wireguard and instead then connect through that or if you like simplicity check out Tailscale.

This is kinda how I’ve come to look at it. You cannot ask questions of fact to a machine that works in probabilities.

Ha, ya know? I think I know some people who will just regurgitate whatever input they receive

…

:(