some IPs block Linode
I CAN access these sites from other shells at other accounts I have, e.g., directly from a Caltech account as well as from my local Charter ISP (turning VPN off). E.g., I can test this under ssh-X with a browser like Firefox/Chrome, or with elinks, lynx, etc.
Out of 100's of sites I connect to via 2 PCs and 2 phones, there are less than half a dozen with this blocking problem, but these are pretty public sites, e.g.,
I have checked numerous sites that test for blacklisted IPs, and I am on none of these 100 or so sites. These sites are not listed in any of my iptables, etc.
I have had this Linode at Fremont for over 4 years, with the same static IPv4 address.
7 Replies
i did contact the sites – the only way I could was to use email addresses in the whois database. I'll see where that goes …
wget –spider
Spider mode enabled. Check if remote file exists.
--2014-12-30 19:40:14--
Resolving researchgate.net (researchgate.net)… 69.174.243.184
Connecting to researchgate.net (researchgate.net)|69.174.243.184|:80… failed: No route to host.
Then I tried the wget from my Desktop and it attempted 20 different 301 redirects before wget stopped. Oddly, it worked when I hit the site from my desktop in my Chrome browser.
The site's IP is clean here:
Thanks. That's obviously a big help. I've flushed (and saved) my iptables to prove the problem is not there. Your comments should help support look elsewhere.
From my linode
$ telnet researchgate.net 22
Trying 69.174.243.184...
Connected to researchgate.net.
Escape character is '^]'.
SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
Protocol mismatch.
Connection closed by foreign host.
$ telnet researchgate.net 80
Trying 69.174.243.184...
telnet: connect to address 69.174.243.184: Connection refused
So something is blocking port 80 traffic but letting port 22 traffic through.
I'm not too surprised. In the past I've caught a few Linode users trying to hack into my VPS. It's bound to come home to us …
If I'm correct, I still have to explain why my Linode IP is not blacklisted. Perhaps some sites getting hacked do what a lot of us under similar circumstances -- we block ranges of IPs, and don't bother trying to get specific hackers' IPs blacklisted. In many cases, blacklisting hackers' IPs is a waste of time as they just change IP addresses.
It would be nice if some of the blocking sites I've contacted would reply back with their reasons, but I'm not holding my breath.