Date: Wed, 20 Feb 2019 06:43:06 -0700 (MST) From: BBlister <bblister@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: Cannot identify process of listening port 600/tcp6 Message-ID: <1550670186155-0.post@n6.nabble.com> In-Reply-To: <20190220025350.GE98237@aurora.gregv.net> References: <1550339000372-0.post@n6.nabble.com> <5b5f72fc-c054-ea43-6602-e7bdb742d657@sentex.net> <1550602404163-0.post@n6.nabble.com> <20190220025350.GE98237@aurora.gregv.net>
next in thread | previous in thread | raw e-mail | index | archive | help
The rpcinfo -p does appear to be useful but not entirely, because still some
ports are hidden.
For example, on my machine I have two listening sockets
815/tcp4 and 874/tcp6
# netstat -an | grep -E '874|815'
tcp4 0 0 *.815 *.* LISTEN
tcp6 0 0 *.874 *.* LISTEN
sockstat reports ?
# sockstat | grep -E '874|815'
? ? ? ? tcp4 *:815 *:*
? ? ? ? tcp6 *:874 *:*
rpcinfo -p reports just one port
# rpcinfo -p| grep -E '874|815'
100021 0 tcp 815 nlockmgr
100021 1 tcp 815 nlockmgr
100021 3 tcp 815 nlockmgr
100021 4 tcp 815 nlockmgr
The 874/tcp6 which belongs to rpc.lockd does not appear on this list.
Is rpcinfo only for IPv4 and if yes,what tool do I use for IPv6 ?
Thanks for your hint Greg Veldman-3
--
Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-questions-f3696945.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1550670186155-0.post>