From: Jesper FA (424242424242424242_at_j-f.dk)
Date: Fri 02 Aug 2002 - 22:58:19 BST
I run kdm in a vserver on 2 diferent root servers which both behave different
than I expected. It is regarding the tcp port it listens on shown below. It
is allowed to bind to "0.0.0.0". As I understand it it should be forced to
use 10.0.0.98 as it is the only IP it is given in the conf file.
It is not only an error in netstat. On the root server netstat doesn't report
anything listening on port 22051, but I can connect to it. If I on the root
server or any other vserver try to bind to port 22051 it failes.
The one server is patch version ctx10 and the other ctx12.
# vserver x exec netstat -nap
Server x is running
ipv4root is now 10.0.0.98
New security context is 2
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:22051 0.0.0.0:* LISTEN 1168/kdm
tcp 0 0 10.0.0.98:22 0.0.0.0:* LISTEN 1159/sshd
udp 0 0 10.0.0.98:177 0.0.0.0:* 1168/kdm
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags Type State I-Node PID/Program name
-- Jesper 11:37pm up 7 days, 8:06, 9 users, load average: 0.44, 0.29, 0.22