[spam][crazy][logs] Funny things computers can do
My system right now gives a routing error trying to connect to port 3000, but connects to port 22 fine. I'm sure this is normal now, but it isn't something I'm used to. Routing errors are usually not given related to ports or processes connected via. $ curl -v [gently-censored-ip]:3000 * Trying 108.26.195.204:3000... * connect to 108.26.195.204 port 3000 failed: No route to host * Failed to connect to 108.26.195.204 port 3000: No route to host * Closing connection 0 curl: (7) Failed to connect to 108.26.195.204 port 3000: No route to host $ ssh user@[gently-censored-ip] Welcome to Ubuntu 20.04.4 LTS (GNU/Linux 5.4.0-109-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support: https://ubuntu.com/advantage System information as of Fri 29 Apr 2022 05:59:42 AM EDT ...
It's a port thing: $ nc -nv [ip-gently-censored] 3000 nc: connect to 108.26.195.204 port 3000 (tcp) failed: No route to host $ nc -nv 108.26.195.204 22 Connection to [ip-gently-censored] 22 port [tcp/*] succeeded! SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.4
I'm vaguely recalling that this means that your ISP is censoring ports. Maybe the port is closed, and it's a new policy to reduce port-scanning? If so it is one that makes it hard to detect that a port is closed.
This one is kind of weird. It displays the page on the local system, but not when the TCP connection is forwarded over SSH. ssh -D 3000 user@[gently-censored] user@[gently-censored]:~$ curl -v 127.0.0.1:3000 [91/948] * Trying 127.0.0.1:3000... * TCP_NODELAY set * Connected to 127.0.0.1 (127.0.0.1) port 3000 (#0)
GET / HTTP/1.1 > Host: 127.0.0.1:3000 User-Agent: curl/7.68.0 Accept: */*
* Mark bundle as not supporting multiuse < HTTP/1.1 200 OK $ curl -v 127.0.0.1:3000 * Trying 127.0.0.1:3000... * Connected to 127.0.0.1 (127.0.0.1) port 3000 (#0)
GET / HTTP/1.1 Host: 127.0.0.1:3000 User-Agent: curl/7.74.0 Accept: */*
* Empty reply from server * Connection #0 to host 127.0.0.1 left intact curl: (52) Empty reply from server
thankfully works over SSH. just a network behavior issue. not necessarily an AI living on both systems mutating their functionality.
participants (1)
-
Undiscussed Horrific Abuse, One Victim of Many