5 ms·

Looking forward to ipv6!

by zxwrt 4y ago

tambre 4y ago
It's on their list fortunately. Until then you can derive and use the IPv6 address for their old Cloudflare endpoint. I pinged them to update the backend IP for it after the outage switched to a new server. Might need to do that again now.
- zxwrt 4y ago
  > It's on their list fortunately. Do you know why they fail to implement ipv6 for years? I mean it's shame when tech-oriented website/service can't keep up with new technologies. > Until then you can derive and use the IPv6 address for their old Cloudflare endpoint. Would be cool if you could share more information how to do that.
  - uo21tp5hoyg 4y ago
    I've always assumed it has something to do with HN being written in its own programming language.
    - epicTaters 4y ago
      So it's written in Lisp, am I right?
      - joveian 4y ago
        https://en.wikipedia.org/wiki/Arc_programming_language https://en.wikipedia.org/wiki/Arc_programming_language
  - tambre 4y ago
    > Do you know why they fail to implement ipv6 for years? Little motivation to make changes and their anti-spam systems only handle IPv4. > Would be cool if you could share more information how to do that. Put the bytes of the IPv4 Cloudflare endpoint at the end of a Cloudflare IPv6 Anycast prefix and voila. Fastly is similar but you take the bytes containing the site ID in the IPv4 address. Also seems they didn't forget to update Cloudflare this time around. :) HN Cloudflare IPv4: 104.16.104.110 HN Cloudflare IPv6: 2606:4700::6810:686e
bdlowery 4y ago
Why is switching to ipv6 something to look forward too? What are the benefits?
- fzfaa 4y ago
  Easier to bypass bans.
  - pilif 4y ago
    not really. By banning the whole /64 prefix, you get the same effect that you got from banning a single IPv4 address.
    - xena 4y ago
      Unless the person uses t-mobile, which puts a lot of people on very small IP blocks, which is such a huge logistical nightmare for enforcing bans. https://news.ycombinator.com/item?id=32038215 https://news.ycombinator.com/item?id=32038215
    - d110af5ccf 4y ago
      You have to be careful about that, not everyone hands out /64. They can be as small as /128 and I've seen some providers give out as large as /48.
      - blurrybird 4y ago
        /48 is the recommendation for home users now. My ISP (Aussie Broadband) follows that recommendation and provides me with a /48 that I can break into multiple /56s or /64s.
        d110af5ccf 4y ago
        I'd prefer a much smaller range but being able to request as many as I want via DHCP (or equivalent mechanism). That way it wouldn't be contiguous so I wouldn't feel as much of a need to use a VPN for privacy. As it is, what's the point of handing me an entire /48 if I just end up forcing most of my traffic through a single IPv4 address with a VPN for most of my web browsing anyway? Although to be fair even with non-contiguous address space I might still want a VPN since ISPs in the US are allowed to sell your browsing history. Also if I'm hosting a public facing service at home I'm going to proxy it via wireguard through a VPS I rent for obvious security reasons. I don't actually want public facing services directly exposed from my home network and I have to question the sanity of anyone who says they do. And I've always disabled webrtc for obvious privacy (ie network fingerprinting) reasons. What's so great about getting rid of NAT again?

Looking forward to ipv6!

by zxwrt 4y ago

Looking forward to ipv6!

It's on their list fortunately. Until then you can derive and use the IPv6 address for their old Cloudflare endpoint. I pinged them to update the backend IP for it after the outage switched to a new server. Might need to do that again now.

zxwrt 4y ago
> It's on their list fortunately. Do you know why they fail to implement ipv6 for years? I mean it's shame when tech-oriented website/service can't keep up with new technologies. > Until then you can derive and use the IPv6 address for their old Cloudflare endpoint. Would be cool if you could share more information how to do that.
- uo21tp5hoyg 4y ago
  I've always assumed it has something to do with HN being written in its own programming language.
  - epicTaters 4y ago
    So it's written in Lisp, am I right?
    - joveian 4y ago
      https://en.wikipedia.org/wiki/Arc_programming_language https://en.wikipedia.org/wiki/Arc_programming_language
- tambre 4y ago
  > Do you know why they fail to implement ipv6 for years? Little motivation to make changes and their anti-spam systems only handle IPv4. > Would be cool if you could share more information how to do that. Put the bytes of the IPv4 Cloudflare endpoint at the end of a Cloudflare IPv6 Anycast prefix and voila. Fastly is similar but you take the bytes containing the site ID in the IPv4 address. Also seems they didn't forget to update Cloudflare this time around. :) HN Cloudflare IPv4: 104.16.104.110 HN Cloudflare IPv6: 2606:4700::6810:686e

bdlowery 4y ago

Why is switching to ipv6 something to look forward too? What are the benefits?

fzfaa 4y ago
Easier to bypass bans.
- pilif 4y ago
  not really. By banning the whole /64 prefix, you get the same effect that you got from banning a single IPv4 address.
  - xena 4y ago
    Unless the person uses t-mobile, which puts a lot of people on very small IP blocks, which is such a huge logistical nightmare for enforcing bans. https://news.ycombinator.com/item?id=32038215 https://news.ycombinator.com/item?id=32038215
  - d110af5ccf 4y ago
    You have to be careful about that, not everyone hands out /64. They can be as small as /128 and I've seen some providers give out as large as /48.
    - blurrybird 4y ago
      /48 is the recommendation for home users now. My ISP (Aussie Broadband) follows that recommendation and provides me with a /48 that I can break into multiple /56s or /64s.
      - d110af5ccf 4y ago
        I'd prefer a much smaller range but being able to request as many as I want via DHCP (or equivalent mechanism). That way it wouldn't be contiguous so I wouldn't feel as much of a need to use a VPN for privacy. As it is, what's the point of handing me an entire /48 if I just end up forcing most of my traffic through a single IPv4 address with a VPN for most of my web browsing anyway? Although to be fair even with non-contiguous address space I might still want a VPN since ISPs in the US are allowed to sell your browsing history. Also if I'm hosting a public facing service at home I'm going to proxy it via wireguard through a VPS I rent for obvious security reasons. I don't actually want public facing services directly exposed from my home network and I have to question the sanity of anyone who says they do. And I've always disabled webrtc for obvious privacy (ie network fingerprinting) reasons. What's so great about getting rid of NAT again?