3 ms·
This looks really good. :) Pity it's on GitHub Pages though, so people using IPv6 only can't access it. :(
by justinclift 5y ago
This looks really good. :)
Pity it's on GitHub Pages though, so people using IPv6 only can't access it. :(
- rolph 5y agothis appears to be a link to .PDF of the content : https://github.com/sysprog21/lkmpg/releases/download/latest/lkmpg.pdf https://github.com/sysprog21/lkmpg/releases/download/latest/... [PDF]
- laumars 5y agoSo offer to mirror it then. The D in git’s DVCS stands for “decentralised”. I’ve heard some dumb complaints in my time but the real beauty of this one is you made it on another site that’s IPv4 only (HN doesn’t yet support IPv6 either).
- turminal 5y agoD in DVCS actually stands for distributed, but your point still stands ;)
- laumars 5y agoDamn it, I knew that as well. That’ll teach me not to post on HN at 1 in the morning! Thanks for the correction :)
- justinclift 5y agoIf it were something I was likely to be using a bunch, then I probably would. Saying that it's a "dumb complaint" to point out that large parts of the world can't access the content is kind of taking the piss though. :(
- deleted 5y ago[deleted]
- laumars 5y agoSaying “large parts of the world can’t access [IPv4]” is massively over exaggerating the situation. Particularly when most of the web is still IPv4 only. You do actually realise that even users with only an IPv6 address can still get access to IPv4 sites via bridges (the names of which escape me off hand)?
- junon 5y agoNot the world's biggest fan of GitHub myself but to be fair they're about to support ipv6. They've started putting up AAAA records around other parts of the site if memory serves.
- justinclift 5y agoCool, that's really good news. :)
- zrail 5y agoDo you have real examples of people that actually have zero access to IPv4 sites, or is this just a theoretical concern?
- est31 5y agoMy ISP sometimes has outages of their carrier grade NAT infrastructure. Then the ipv4 is broken, but services that use ipv6 still work.
- justinclift 5y agoQuite a few of our (sqlitebrowser.org) users weren't able to access our download server, nor nightly build server, until we made it available over IPv6 in addition to just IPv4. Seems to be mainly people located in South East Asian countries, though I'd have to go trawling back through log history to get the exact details.
- zrail 5y agoThanks, that makes sense. Often it feels like that argument gets thrown around disingenuously. It's nice to have specific examples to talk about.
- Arnavion 5y agoSee if your router supports DNS64 (DNS server maps IPv4 addresses in responses to IPv6 addresses under a chosen prefix) and NAT64 (firewall translates IPv6 LAN packets with addresses under that prefix to the original IPv4 packets, and back). I don't know about consumer routers, but it's relatively straightforward to do on pfSense / OPNsense. It doesn't work for protocols that embed IP addresses, like BitTorrent, since you'd need a protocol-aware proxy for that rather than just an IP firewall, but for something like HTTP there won't be any problem.
- stjohnswarts 5y agoHold up.... People are using IPV6 only networks now? There aren't ipv4 bridges? That's kind of disconcerting. This is a first time hearing of such. While I have no doubt it can be done technically but why can't you get to IPV4 networks?