Live data from Hacker News

Icanhazip: A simple IP address tool survived a deluge of users (2021)

blog.apnic.net

141–146 of 146 posts

Re: Icanhazip: A simple IP address tool survived a deluge of users (2021)

#141
post #82

Earlier quoted context omitted.

I would trust the rust compile/rerun process a lot more than an auto-updating linux distribution, personally. Sooner or later that auto-updating package manager will break your config file, itself, or both.

The majority of nginx distributions will not get any major bumps during the lifetime of the distros they're in. Whether that's because the distro itself has policies against that (Debian, Ubuntu) or because the distro version expires before nginx' stable release does (most of the ones with a higher update frequency, ie. Fedora) so by the time the version expires, they can just go to the next stable version on the rel…

> The majority of nginx distributions will not get any major bumps during the lifetime of the distros they're in. Whether that's because the distro itself has policies against that (Debian, Ubuntu) or because the distro version expires before nginx' stable release does (most of the ones with a higher update frequency, ie. Fedora) so by the time the version expires, they can just go to the next stable version on the release after.

If you're following that approach then having auto updates enabled is kind of irrelevant/meaningless; at some point you're going to be running a very old (and unsupported) version of your distro with all that that implies.

Re: Icanhazip: A simple IP address tool survived a deluge of users (2021)

#142
post #30

For ridiculously easy things like this, I think it's smarter for you to just host it yourself. This way you are not forcing other people to carry your burden. nginx config example: location /ip { add_header Content-Type "application/json"; return 200 '{"host":"$server_name","ip":"$remote_addr","port":"$remote_port","server_ip":"$server_addr","server_port":"$server_port "}\n'; } Which will return something like this i…

great callout! A more advanced self hosted option can be https://github.com/mpolden/echoip

Re: Icanhazip: A simple IP address tool survived a deluge of users (2021)

#143
I use icanhazip. It is good; just the plain IP address, no HTML and no JSON. It could be done even simpler by just nc to a specified host and port and no HTTP is needed either; it need not wait for a request and will not need response headers.

I made a shell script with:

  curl -s 'http://icanhazip.com/' | cat -v

Re: Icanhazip: A simple IP address tool survived a deluge of users (2021)

#144
post #118
post #67

Earlier quoted context omitted.

I’d say that is up you. I can never remember what tld those other sites used. I’ve been using icanhazip since many years. I seem to remember it fine.

Replace the double nn in your post by nh and it will work better ;-)

Thanks. Phone keyboards are hard sometimes.

Re: Icanhazip: A simple IP address tool survived a deluge of users (2021)

#145
post #30

For ridiculously easy things like this, I think it's smarter for you to just host it yourself. This way you are not forcing other people to carry your burden. nginx config example: location /ip { add_header Content-Type "application/json"; return 200 '{"host":"$server_name","ip":"$remote_addr","port":"$remote_port","server_ip":"$server_addr","server_port":"$server_port "}\n'; } Which will return something like this i…

Another one https://whatismyip.akamai.com/advanced?debug https://ipv4.whatismyip.akamai.com DNS-based drill whoami.akamai.net The second one might be useful to verify one is not using local, ISP-provided DNS, or to see whether a DoH provider effectively geolocates its users, e.g., Cloudflare.

Another one

Send a request to stackexchange.com or any of its subdomains without a user-agent header.

Re: Icanhazip: A simple IP address tool survived a deluge of users (2021)

#146
post #125
post #114

Earlier quoted context omitted.

Great service! Very informative. If you could also implement ip.wtf/ip or some such, it might decrease your bandwidth..!

Thanks! No need for a /ip, just doing: $ curl ip.wtf ... will do the right thing, or if your user-agent isn't curl send a header of "Accept: text/plain" and you'll get the plain text version (see https://ip.wtf/about for more).

And no need for an IPv4 or IPv6 mode url/param since curl -4 or curl -6 will do the trick!
Post reply on HN