“living off of your property” is shorthand (and so maybe we should be more explicit) for “living off of the production and labor of other people who need access to your property to do that labor”.

So yea, i think it is exploitative to restrict access your property to someone who would use it to reproduce themselves each day (a home) or would use it to produce other valuable goods and services (a job) and to require that person to pay you for access (that home again) or you’ll pay them wages less than what they produce (that job).

And i think exploitative is inherently bad.

The boy, sir?

I was saying to myself “404 has done so much important reporting on ICE in just the last week. I wonder how i can help them do that work.” Then i remembered that money can be exchanged for goods and services and signed up for a year

If only…

They are paying rent still.

Your loss

Archer AX11000

I just try them both every time

There are certainly are bigger issues in the world right now, sure, but it isnt about “rights for software”, it is about the ability people to talk about what they want (in this case, software)

I appreciate the ability for the tor-like layered routing with tribler. Getting the headless UI set up is annoying, though.

Ooo, interesting.

I am going for public access here, so it wont work. But i think this is how some routers are set up. Like i think asusrouter.net is set to 192.168.0.1, so anyone with the router can go to the same url / domain and itll send them each to their own router. Found that out the other week and thought it very clever.

So i had done this (with Adguard rather than pihole) and i think i was getting caching issues. Whether or not i was, though, i removed it and it looks like my router is handling it all just fine without the rewrite on the local DNS server.

Some folks mentioned “hairpin NAT” - i was reading the wiki on NAT last night but didnt get to hairpin, but that appears to be what is happening.

The conclusion is - my setup had been doing what i want the whole time without any DNS fiddling. I updated the original post with the speedtests.

I guess I should say that I think there were caching issues, but the problem was coming from an iphone and the Bitwarden app (connecting to the self-hosted vaultwarden).

i think this is what I was doing with Adguard and using the re-write rules, but then the client (my phone, for example) would cache the IP address and it would fail when I was out of the house/network.

Or am I misunderstanding what you are saying here?

ok, well that’s easy to set up if that is how it just works! i wonder if maybe i should (at least temporarily) self-host some sort of speedtest app on the server and check the speed from my phone while i’m on wifi using the IP, wifi using domain name, and off wifi using domain…

Server is running the password manager for myself and family, and that needs to stay on while gone (there are ways of handling local copies and they sync later, but when ive accidentally had to troubleshoot that it sucks).

Then ive got nextcloud, which while i don’t normally need things on there i do enough that it is nice to have.

A “TLD” is a Top-level Domain, examples of which are .com and .org. They sell names within their domains.

You’d just be buying a “domain name” within some TLD and redirecting traffic from that domain name, not from the TLD.

For a domain name:

You go to something like NameCheap.org and buy a name (hackers4life.xyz or something cool like that). Then their web interface has a place for you to enter the IP address that you want associated with that name. Whenever someone then types “hackers4life.xyz” there will br a series of computers asking other computers “do you know the IP address for this?” until they do.

If you have that Pi in your house, there are (at least) two steps for you then: (1) Getting your home IP address (2) Forwarding the port

(1) Your router admin panel may have this, or else if you search the web for “what is my ip” there are sites that will tell you (basically, you connect to their webpage and they just print out the IP they are sending data back to). There are two concerns here, though.

(a) Do you have a unique IP? There arent enough IPv4 addresses in the world for all the computers connecting to the internet. To get around this, ISPs will essentially group customers together under the same IP and then they figure out how to get the traffic to the right place. If you dont have a unique IP, you might be screwed (but i havent looked into dealing with that much).

(b) If you have a unique IP, you still probably dont have a stable IP. Your ISP might reallocate all the addresses in their network every day/week/month/whenever. This is the case for me. Namecheap (or whatever other domain vendor) has a process for you to use a script to send them your IP address, and so you make a script to recheck it and send namecheap updates every hour or something like that.

(2) Forwarding the port

Some other machine on the web knows your IP (because it is associated with hackers4life.xyz) and so they try to connect. This comes down the wire from the street into the side of your house/apartment, into the modem, and into your router. If your router isnt expecting it (or prepared to do something with it), itll just ignore it. You want the router to instead send it to your Pi. To do this, you go to your router’s admin settings and forward the messages based on the port they are coming in on. The standard ports for HTTP and HTTPS are 80 and 443, and so you can forward those ports to the Pi. Making sure that then the Pi does the right things with those is outside the scope of me writing right now.

“according to Western Officials”, i.e. the people who are (formally or informally) at war with Russia and have been isolating North Korea. They are a very biased source

I turned off QoS and immediately am getting 930 on speedtest.net from the desktop browser!

Also, very helpful to know Issue 1 here. I assumed that the router would be the best spot to test since it is farthest upstream (other than the modem). I didn’t know it could pass traffic faster than it can decode, but that makes sense that people would have tried to make that the case. The router is still getting ~500 Mbps while the browser is much closer to the full 1000.

fast.com gives 500 Mbps