-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi,
On 22/8/22 9:41 am, Russell Coker via luv-main wrote:
> Resolving laptop006.livejournal.com (laptop006.livejournal.com)... 81.19.74.0
> Resolving laptop006.livejournal.com
> (laptop006.livejournal.com)... 81.19.74.0 Resolving laptop006.livejournal.com
> (laptop006.livejournal.com)...
> 81.19.74.5
Just to point out that the destination IP is different, I expected dig to
return a bunch of IPs, but I got a different one:
$ dig -t a laptop006.livejournal.com +short
clb.livejournal.com.
81.19.74.1
The server could be doing fail2ban or it could be blocking for other reasons.
The target server(s) is in Russia according to whois on the IP addresses.
$ subnetcalc 81.19.74.0/24
Address = 81.19.74.0
01010001 . 00010011 . 01001010 . 00000000
Network = 81.19.74.0 / 24
Netmask = 255.255.255.0
Broadcast = 81.19.74.255
Wildcard Mask = 0.0.0.255
Hosts Bits = 8
Max. Hosts = 254 (2^8 - 2)
Host Range = { 81.19.74.1 - 81.19.74.254 }
Properties =
- 81.19.74.0 is a NETWORK address
- Class A
GeoIP Country = Russian Federation (RU)
DNS Hostname = livejournal.com
So, perhaps the IP you are coming from may be considered unfriendly to the
Russian server?
One of the failed wget attempts used a specific user agent, that too might be
the issue; the default user agent for wget
might vary as well between the systems.
This via tor network through privoxy:
$ curl -IL4s https://laptop006.livejournal.com/data/rss
HTTP/1.1 200 Connection established
HTTP/1.1 403 Forbidden
Server: nginx
Date: Mon, 22 Aug 2022 16:10:23 GMT
Content-Type: text/html
Connection: keep-alive
Keep-Alive: timeout=50
A little more debugging and not using tor, so without privroxy:
$ curl -IL4s --noproxy * https://laptop006.livejournal.com/data/rss|grep -Ei
'^location:|^HTTP'
HTTP/1.1 503 Forwarding failure
HTTP/1.1 301 Moved Permanently
Location: http://dan.com/buy-domain/000.sh?redirected=true
HTTP/1.1 301 Moved Permanently
Location: https://dan.com/buy-domain/000.sh?redirected=true
HTTP/1.1 200 Connection established
HTTP/2 200
HTTP/1.1 503 Forwarding failure
HTTP/1.1 503 Forwarding failure
HTTP/1.1 503 Forwarding failure
HTTP/1.1 503 Forwarding failure
^C
Don't know if I've helped at all, but there could be some DNS problems if the
domain(s) are properly active.
Cheers
A.
-----BEGIN PGP SIGNATURE-----
iHUEAREIAB0WIQTJAoMHtC6YydLfjUOoFmvLt+/i+wUCYwOrRgAKCRCoFmvLt+/i
+/ykAQDZjBxMNh7CNyuHJfKBOGiIh2BuRnKZSBIXRqr81SBpiAD+LEvPucrhz6uY
tvTE6/dKBg0Ah18rxJ7m0XG2s/vtz04=
=oBMv
-----END PGP SIGNATURE-----
_______________________________________________
luv-main mailing list -- [email protected]
To unsubscribe send an email to [email protected]
