Anssi Saari wrote:
> Victor Sudakov writes:
>
> > It's different in *BSD which got me confused. In *BSD, even if you bind
> > to INADDR_ANY, you'll see something like this in sockstat output:
> >
> > root dovecot39601 21 tcp4 *:110 *:*
> > root dovecot39601 22 tc
Victor Sudakov writes:
> It's different in *BSD which got me confused. In *BSD, even if you bind
> to INADDR_ANY, you'll see something like this in sockstat output:
>
> root dovecot39601 21 tcp4 *:110 *:*
> root dovecot39601 22 tcp6 *:110 *:*
>
Andy Smith wrote:
>
> On Thu, Aug 20, 2020 at 12:09:03PM +0700, Victor Sudakov 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?
>
> I think it's listening on an IPv4-mapped IPv6
Hi Victor,
On Thu, Aug 20, 2020 at 12:09:03PM +0700, Victor Sudakov 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?
I think it's listening on an IPv4-mapped IPv6 address so it can
acc
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...
> > > C
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 charact
Victor Sudakov wrote:
> Dear Colleagues,
>
> 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 c
7 matches
Mail list logo