Forum:IPv6
Jump to navigation
Jump to search
- Executive summary: IPv6 is live. This page is the Prequel. -- Snarglefoop (talk) 02:58, 27 May 2019 (UTC)
- These discussions began at Forum:Uncyclopedia's new home
We have a V6 address but we're currently not operational on it.
- We're not advertising the V6 address via DNS, so the only ones touching our V6 port 80 are spammers who find it by port-sweeping us.
- Even the spammers can't get to the site that way because nobody's listening on the V6 address.
Both of these should get fixed. (On the positive side, a (primitive) firewall is up. It was as we were setting that up that we encountered the V6 issues.) -- Snarglefoop (talk) 15:18, 14 May 2019 (UTC)
- That sounds doubly bad! I vote that we fix the interface that real people use, and merely promise to fix the one the spammers use Spıke 🎙️15:28 14-May-19
- <grin> Well, actually, everybody uses the same interface. It's just that, until we advertise the V6 interface properly, the only way to find it is by taking shots in the dark, and nobody legit does that. (So, for the time being, it could be described as a spammers-only interface.) So, the goal is to first make somebody listen for V6 connections (because there's no point in advertising it if it doesn't work) and then try to get the DNS stuff set. Llwy-ar-lawr seems to know how to make somebody listen on the port, and if we can't figure out how to fix the DNS issue we may ask CarlB for advice, since he seems to understand it. (And I'm putting this here so it doesn't get lost, not because I, personally, know what to do about it.) -- Snarglefoop (talk) 15:52, 14 May 2019 (UTC)
- I think the problem is that Squid needs to listen on IPv6 and I didn't set it up. I may have fixed this just now by adding some lines to the Squid config file. I might need to change the DNS records for uncyclopedia.ca as well because at the moment it's pointed here with a CNAME record for the server hostname rather than A. This could also be the reason why wiki email comes from an address ending in the server name instead of "uncyclopedia.ca". ❦ Llwy-ar-lawr • talk • contribs • 16:33 14 May 2019
- I didn't think it was possible to CNAME the base domain, according to the standard. That may mean that your provider's DNS setup is hiding this limitation by silently replacing CNAME with A or some other record. A subdomain can be CNAME'd... but even then, whatever that CNAME is pointing to would have to have a valid AAAA record to do IPv6. carlb (talk) 16:56, 14 May 2019 (UTC)
- I think the problem is that Squid needs to listen on IPv6 and I didn't set it up. I may have fixed this just now by adding some lines to the Squid config file. I might need to change the DNS records for uncyclopedia.ca as well because at the moment it's pointed here with a CNAME record for the server hostname rather than A. This could also be the reason why wiki email comes from an address ending in the server name instead of "uncyclopedia.ca". ❦ Llwy-ar-lawr • talk • contribs • 16:33 14 May 2019
- <grin> Well, actually, everybody uses the same interface. It's just that, until we advertise the V6 interface properly, the only way to find it is by taking shots in the dark, and nobody legit does that. (So, for the time being, it could be described as a spammers-only interface.) So, the goal is to first make somebody listen for V6 connections (because there's no point in advertising it if it doesn't work) and then try to get the DNS stuff set. Llwy-ar-lawr seems to know how to make somebody listen on the port, and if we can't figure out how to fix the DNS issue we may ask CarlB for advice, since he seems to understand it. (And I'm putting this here so it doesn't get lost, not because I, personally, know what to do about it.) -- Snarglefoop (talk) 15:52, 14 May 2019 (UTC)
Some work was going on with this earlier. Can the site identify people/IPs by IPv6 now? Last I saw in the end days at Wikia, more and more US accounts and our users had IPv6s. And it might be nice to pinpoint vandals a little better based on location/ISP. --
(talk) 03:08, 26 May 2019 (UTC)
- Yes, we're recording IPv6 connections to sockets 80 and 443 (I really wanted to know if there were any). However, nobody's listening on those sockets at our v6 address, and we're not yet advertising our v6 address via DNS, so IPv6 connection attempt log entries don't make for fascinating reading. (It's not forgotten but it got pushed down the stack a bit by some other stuff that seemed more urgent.) -- Snarglefoop (talk) 03:27, 26 May 2019 (UTC)
- I changed the DNS record to have A and AAAA for the IP addresses instead of CNAME. IPv6 seems to work now. ❦ Llwy-ar-lawr • talk • contribs • 06:06 26 May 2019
- Llwy-ar-lawr from ipv6proxy.net. No native IPv6 on my network. 2600:3C00:0:0:F03C:91FF:FE93:DCD4 06:10, 26 May 2019 (UTC)
- I changed the DNS record to have A and AAAA for the IP addresses instead of CNAME. IPv6 seems to work now. ❦ Llwy-ar-lawr • talk • contribs • 06:06 26 May 2019