🇨🇦

  • 9 Posts
  • 328 Comments
Joined 3 years ago
cake
Cake day: July 1st, 2023

help-circle



  • Darkassassin07@lemmy.caOPtoSelfhosted@lemmy.worldOpenVPN ipv4 troubles.
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    18 days ago

    To avoid this, you will need an IPv4 address on your client, or an IPv6 address on your server.

    This confuses me because I have an IPv4 address on the client, and that IPv4 is what the server is seeing make the connection…

    /edit

    I think I get it.

    The client actually only has IPv6. The IPv4 address I’m seeing in the log and whatismyipaddress.com is the address of my mobile providers NAT.

    Thanks. I still haven’t totally wrapped my head around IPv6. Stubbornly happy with IPv4 tbh, but it seems the rest of the world is moving on, understandably.








  • If you have a static IP address, you can just use A records for each subdomain you want to use and not really worry about it.

    If you do not have a static IP address, you may want to use one single A record, usually your base domain (example.com), then CNAME records for each of your subdomains.

    A CNAME record is used to point one name at another name, in this case your base domain. This way, when your IP address changes, you only have to change the one A record and all the CNAME records will point at that new IP as well.

    Example:

    A example.com 1.2.3.4

    CNAME sub1.example.com example.com

    CNAME sub2.example.com example.com

    You’d then use a tool like ACME.sh to automatically update that single A record when your IP changes.





  • Your ISP could snitch on you for tons of ‘illegal’ traffic, but they don’t because that would require deep packet inspection on an absurd amount of traffic and they gain nothing for it. Instead they pass on notices when they receive them from third parties, and take enforcement actions (like cutting off their service to you) only when they’re directed to. They want your money after all.

    Torrenting for example; only gets flagged when copyright holders join torrent trackers, then send letters to ISPs that control the IPs found in those groups. That’s not the ISP hunting you down, they’re just passing on a legal notice they’ve been given and thus are obligated to pass it to you.

    From and ISPs perspective; a VPN connection doesn’t look any different than any other TLS connection, ie https. There’s nothing for them to snitch because a) they can’t tell the difference without significant investment to capture and perform deep analysis on traffic at an absurd scale and b) they have no desire to even look and then snitch on customers, that just costs them paying customers.

    The ONLY reason this can be enforced at all, is because comercial VPN companies want to advertise and sell their services to customers; so lawmakers can directly view and monitor those services.

    Lawmakers have no way of even knowing about, let alone inspecting an individuals private VPN that’s either running from private systems or from a foreign VPS.


    All that’s not even touching things like SSH tunneling - in a sense, creating a VPN from an SSH connection; one of the most ubiquitous protocols for controlling server infrastructure around the globe. Even if traffic was inspected to find SSH connections, you CAN’T block this or you disrupt IT infrastructure at such an alarming scale there’d be riots.






  • :/ shit.

    I’m pretty sure I saw this a few months ago and moved to the beatkind/watchtower fork, but it’s not been updated in 6mo either. (Devs only been active in private repos; so they’re still around, just not actively working on watchtower)

    Guess I’ll find another solution. Hell, I might just put my own script on crontab. Looping through folders running docker compose down/pull/up isn’t too hard really.