Odd fstat(1) results for IPv6 listening ports on netbsd-6 (amd64)

[Matthew Mondor]

Hello,

Before filing a PR or checking the source, I wanted to check if anyone
also experience this, as I also have local changes in my tree.

When sshd(8) listens on IPv6 (that may occur with any daemon, I
couldn't check yet), although netstat(1) shows that the port really is
22, and that I can connect to it fine, fstat(1) reports port 5632 for
me.

Thanks,

[Christos Zoulas]

Post by Matthew Mondor
Hello,
Before filing a PR or checking the source, I wanted to check if anyone
also experience this, as I also have local changes in my tree.
When sshd(8) listens on IPv6 (that may occur with any daemon, I
couldn't check yet), although netstat(1) shows that the port really is
22, and that I can connect to it fine, fstat(1) reports port 5632 for
me.

fixed.

christos


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Matthew Mondor]

On Sat, 24 Mar 2012 21:51:34 +0000 (UTC)

Post by Christos Zoulas

Post by Matthew Mondor
When sshd(8) listens on IPv6 (that may occur with any daemon, I
couldn't check yet), although netstat(1) shows that the port really is
22, and that I can connect to it fine, fstat(1) reports port 5632 for
me.

fixed.

Thanks, to get this endian fix pulled up to netbsd-6, should a PR exist?