Faraday

New UA, new IP range

[jonasjacek]

UA: Faraday v0.9.2
Protocol: HTTP/1.1
Robots.txt: No
Host: HETZNER
NetRange: 2A01:04F8:0210:220D:0000:0000:0000:0000 - 2A01:04F8:0210:220D:FFFF:FFFF:FFFF:FFFF
CIDR: 2a01:4f8:210:220d::/64

Previous: [webmasterworld.com...]

"Faraday is an HTTP client lib that provides a common interface over many adapters (such as Net::HTTP) and embraces the concept of Rack middleware when processing the request/response cycle." You can find it on GitHub.

[MitchNginx]

Just spotted this one today too.
"GET /.well-known/acme-challenge/xxxxxx HTTP/1.1" 404 134 "-" "Faraday v0.13.1"

Robots.txt: No
IP: 41.203.16.***

[edited by: MitchNginx at 8:17 am (utc) on Jul 24, 2018]

- - -

[edited by: keyplyr at 10:03 am (utc) on Jul 24, 2018]
[edit reason] Obscured IP address per Forum Charter [/edit]

[keyplyr]

Thanks jonasjacek

When posting bot ranges, please include IPv4 ranges so that more members can use this information.

Just a FYI - Anyone can run this bot, for any reason.

[fix typo]

[edited by: keyplyr at 12:03 am (utc) on Aug 27, 2018]

[keyplyr]

This UA seen from...
Host: hetzner.co.za
41.203.16.0 - 41.203.19.255
41.203.16.0/20

[lucy24]

Please post only IPv4 ranges

Do you have a translator handy? If something visits an IPv6 site from an IPv6 location, all I see is the IPv6 address. Human requests are often mixed (I do not understand why this is so), but robots may only request one thing, so there’s nothing to compare.

[keyplyr]

You see IPv6 because your server, thus the access log, is set up for IPv6. Otherwise you could not "see" IPv6.

A significant amount of WW members are still on IPv4 servers. If/when the majority of members show support for IPv6, we should probably switch.

Until then, let's keep reporting IPv4, or if you like, include both IPv4 & IPv6... so you could use that translator [ultratools.com]. Just make sure to use ranges and not specific addresses.

[lucy24]

Oops, missed this.

All IPv4 addresses can obviously be expressed as IPv6, since 2^32 is just a tiny subset of the 2^64-or-whatever-the-heck-it-is. That's what the linked translator does. But IPv6 addresses don't necessarily have an IPv4 analogue, since that's kinda the whole point of IPv6.

[keyplyr]

Correct, the IPv6 addresses derived from the existing IPv4 can be processed to display either. Those IPv6 addresses created after IPv4 stops can not.

</ end OT discussion about IPv6 >