dChan - Q Origins Project Archive

Found: Reliable 8kun IP address

So I cycled through all of the 8kun IP addresses to see if one or more of them actually work reliably instead of going dead every so often. The rate of failure ranges from 1/3 to 1/20 though no particular address seems to be more vulnerable than the others and I have no way to determine if geographical location is a factor. The end result is that your 8kun client may lock up occassionally, necessitating a reload.

The only address that is consistently working is this one: 23.163.176.229

That address is not even assigned to 8kun. It is assigned to dailystormer.su which is a Vanwanet client so that's why it works. This is very suspicious. I'm thinking that Vanwanet is deliberately sabotaging 8kun. Or it could be the DDoS protection service which, as far as I know, is still DDoS-Guard (https://ddos-guard.net).

>>14869693

Vanwanet is a CDN. You can't use the direct IP. You would have to modify your "hosts" file or employ some other method to bypass the DNS.

Anonymous ID: 7229ec Oct. 27, 2021, 6:29 p.m. No.14869853 🗄️.is 🔗kun >>0163

Found: Alternative IP address block for 8kun

So I cycled through all of the 8kun IP addresses to see if one or more of them actually work reliably instead of going dead every so often. Unfortunately, they all have a failure rate ranging from 1/3 to 1/20, varying over time. I don't know if geographical location is a factor. The end result is that your 8kun client may lock up occasionally, necessitating a reload. You may also get the "deleted or pruned" error message. These are the IP addresses currently assigned to 8kun:

94.103.81.80, 94.103.82.74, 94.103.94.73, 193.178.169.19, 195.2.92.96, 195.2.93.193

I have long suspected that Vanwanet has an entire address block that can be used to access 8kun. There are two other sites that I know to be Vanwanet clients, qagg.news (23.163.176.200) and dailystormer.su (23.163.176.229). Digging further, I find that the entire block of addresses from 23.163.176.200 to 23.163.176.230 inclusive belong to Vanwanet and any of them may be used for 8kun. The few that I tested extensively work reliably, unlike the IP addresses assigned to 8kun by the Vanwanet DNS server.

We can speculate as to why this is. Is Vanwanet deliberately sabotaging 8kun? Or is it the DDoS protection service which, as far as I know, is still DDoS-Guard (https://ddos-guard.net).

Additionally, the posting server at sys.8kun.top has been slow to respond. The 8kun client is impatient and times out too soon with an error message saying that the "server took too long to respond". I'm experimenting to determine if switching the posting server to the alternative address block will help with that.