Hello folks,

I got my static IP and I am very happy now, I have been hosting a lot of services since I got the static IP, however I still have to host a fediverse service however it’s not that easy to host any fediverse service, I tried to host GoToSocial but the devs said they don’t support Podman and my server is podman only ( I tried installing docker but it was failing for some reason so I gave up and used podman instead of docker).

these are the services I am currently hosting ( basically all the easy services which you can host with just “docker compose up -d” :p ):

feel free to suggest some other cool services which I can host :D

  • dysprosium@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 days ago

    Still kinda sad that ip6 still hasn’t taken off, that would give literally every toaster in the world its own static ip

    • Darkassassin07@lemmy.ca
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 days ago

      I really don’t like the idea of every device automatically having a publicly reachable IP.

      There’s certainly situations where that would be nice; but I’m quite fond of most equipment and services being behind a router and it’s firewall, requiring explicit configuration to be exposed to the open net.

      Nobody outside my home network ever needs access to my toaster… (btw, why tf is my toaster wifi enabled…?)

      • timbuck2themoon@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        0
        ·
        4 days ago

        Nat is not a firewall…

        Seriously. Unless you open up your Lan to the internet it functions the same way as ipv4 in respect to receiving unsolicited queries from the internet. All those are dropped.

      • Possibly linux@lemmy.zip
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        4 days ago

        A Firewall and NAT are to different things. All devices would still be behind a Firewall so they would effectively be invisible from the outside except for when they make an out going connection.

        If you really want NAT for IPv6 you could use NAT66. It isn’t technically the IPv6 way of doing things but it works. The main benefit with NAT is that you don’t need to worry about prefixes.

      • cmnybo@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        0
        ·
        4 days ago

        You would have to specifically open a port in your firewall before anyone could access a device over IPv6 on your network from the internet. Just like you would have to forward a port on IPv4.

    • surewhynotlem@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      4 days ago

      I’m convinced it hasn’t taken off because they’re too complicated for the human brain to easily reference. Four triplets is simple enough.

      • Possibly linux@lemmy.zip
        link
        fedilink
        English
        arrow-up
        0
        ·
        4 days ago

        It really isn’t all that complicated. Honestly in some ways it is easier since you don’t need to worry about subnetting. Also SLAAC is pretty cool.

        The key to IPv6 is to not apply your IPv4 brain to it. It works very differently and in some ways it is better.

        • surewhynotlem@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          4 days ago

          Well, yes, for users. But I’m in tech. And it’s the tech people that need to implement it. And when I’m trying to hunt down why something about DNS or a firewall rule isn’t working, I really don’t want to be juggling gigantic alphanumeric strings.

      • qwerty@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        4 days ago

        All the shortening rules trip me up. I’d much rather work with addresses with standardized number of hextets and ideally the same number of digits than not have to type a few zeros.

        all of these are the same address: 2041:0000:0001:0000:0000:0000:875B:131B 2041:0000:0001::875B:131B 2041:0:0001::875B:131B 2041:0000:1:0000:0000:0000:875B:131B 2041::0001:0000:0000:0000:875B:131B 2041::1:0000:0000:0000:875B:131B 2041::0001:0:0:0:875B:131B 2041:0:1::875B:131B 2041:0:1:0:0:0:875B:131B 2041:0000:1:0000:0000:0000:875B:131B 2041:0000:01:000:00:0:875B:131B 2041:00:1::0:875B:131B

        • Possibly linux@lemmy.zip
          link
          fedilink
          English
          arrow-up
          0
          ·
          4 days ago

          What’s the problem?

          Once you learn IPv6 it isn’t bad. I would highly recommend that you check out onemarcfifty IPv6 videos

        • surewhynotlem@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          4 days ago

          Ugh. Yes.

          The fact that they have shortening rules already shows it’s too complicated.

          They would’ve been better off with a shorter length, and ditching hex for a base 32 string.

          • qwerty@discuss.tchncs.de
            link
            fedilink
            English
            arrow-up
            0
            ·
            edit-2
            4 days ago

            Imo they should have kept the ipv4 format but instead of maxing out at 255.255.255.255 make it 65535.65535.65535.65535 this aproach makes the address pool more than 4000000000 times larger and is backward compatible with ipv4 so it could be a drop in replacement for most things. And if we ever do end up running out of over quintilion (18446744073709551616) ips we can just keep going up, to 4294967295.4294967295.4294967295.4294967295.