Fw: Cannot see a process listening on 127.0.0.1

[Matthew Campbell <trenix25@pm.me>]

It looks like you've got a web server listening there.  Try GET / HTTP/1.1 to see what it returns.  You might also try port scanning 127.0.0.1 with nmap to see what it can find.

name=Matthew%20Campbell&email=trenix25%40pm.me





-------- Original Message --------
On Aug 20, 2020, 4:17 AM, Dan Ritter < dsr@randomstring.org> wrote:

Victor Sudakov wrote:
> Dan Ritter wrote:
> > >
> > > There is a process listening on 127.0.0.1:8081 but for some reason
> > > netstat/sockstat/ss do not show it listening on IPv4. Is this a bug or a
> > > feature?
> > >
> > > root@test4:~# telnet 127.0.0.1 8081
> > > Trying 127.0.0.1...
> > > Connected to 127.0.0.1.
> > > Escape character is '^]'.
> > > dd
> > > HTTP/1.1 400 Bad Request
> > > Connection: close
> > >
> > > Connection closed by foreign host.
> > > root@test4:~# netstat -lpn | grep 8081
> > > tcp6 0 0 :::8081 :::* LISTEN 10872/node /home/ad
> >
> > Feature-bug. It's listening on both IPv4 and IPv6; if you want to
> > see them differently, add the 4 or 6 flag to netstat
>
> Nope, the -4 flag does not help:
>
> root@test4:~# telnet localhost 8081
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> dd
> HTTP/1.1 400 Bad Request
> Connection: close
>
> Connection closed by foreign host.
> root@test4:~# netstat -4lpn | grep 8081
> root@test4:~#
>

That's a bug, then.

-dsr-