[cobalt-users] odd results (SNPP) on netstat -a

["A Larter" <alarter@xxxxxxxxxxxxxxxxxxx>]

Hi,

Back again. I've found some more odd behaviour, this time on the snpp
port. This is on a Qube3. It functions as a firewall for a small network
and died for about five minutes. Immediately after it came back up, I
logged into it and saw the following on netstat -a:

tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1088
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1087
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1086
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1085
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1084
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1083
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1082
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1081
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:socks
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1079
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1078
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1077
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1076
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1075
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1074
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1073
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1072
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1071
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1070
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1069
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1068
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1067
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1066
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1065
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1064
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1063
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1062
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1061
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1060
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1059
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1058
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1057
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1056
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1055
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1054
TIME_WAIT
tcp        0      0 my-machine.client:snpp aaa.bbb.ccc.ddd:1053
TIME_WAIT

I'm wondering what causes this. The only thing I can think of is that
it's the web management tool. The IP listed was that of the machine of
someone who would have logged into the tool to look at the status of
various things.

If anyone has any insights, I'd be really grateful to hear them.

Thanks :)

---