• kn33@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    I worked at an ISP. The DHCP server we use for our DSL offering was made in the 90s and hasn’t been updated since.

    • Borgzilla@lemmy.ca
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Frankly, I don’t see this a a problem as long as the software is up to date and the hardware is sound. I bet there are thousands of SPARC servers out there processing data 24/7 since 1995.

          • cbarrick@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            The alternative to IPv6 is CGNAT.

            CGNAT is really annoying for users, since the entire ISP looks like a single IP address. This can lead to situations where the entire ISP accidentally gets classified as a bot or otherwise blocked. It’s not too hard to find these kinds of stories from StarLink customers.

            We are at the point where we are are legitimately out of IPv4 addresses. Household NAT isn’t enough and CGNAT has too many problems. IPv6 code was written ages ago and is very stable in all OSs these days.

            It really is just these legacy middle boxes holding us back.

    • Maslo@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      I’ve worked for a few of the larger ISPs in the US. They all have their own special weird shit like a windows NT machine shoved in a corner in a CO in west Texas that you have to remote desktop into and run some java applet from the 90 to log into a hardwired machine from the 70s just to set up a voicemail box for a phone line. Ain’t broke don’t fix it leads to some wild setups at companies you wouldn’t expect it from.

      • Flax@feddit.uk
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 months ago

        I’d actually rather this than making new software with all kinds of bugs