Ok, the operator sent the output of netstat -n to me:
tcp 0 0 192.168.1.55:3000 10.10.2.10:55740
CLOSE_WAIT
tcp 0 0 192.168.1.55:3000 10.10.2.10:41852
CLOSE_WAIT
tcp 0 0 192.168.1.55:3000 10.10.2.10:40574
CLOSE_WAIT
tcp 0 0 192.168.1.55:3000 10.10.2.10:45049
CLOSE_WAIT
tcp 0 0 192.168.1.55:3000 10.10.2.10:43960
CLOSE_WAIT
tcp 0 0 192.168.1.55:3000 10.10.2.10:45496
CLOSE_WAIT
tcp 0 0 192.168.1.55:3000 10.10.2.10:56315
CLOSE_WAIT
tcp 0 0 192.168.1.55:3000 10.10.2.10:57205
CLOSE_WAIT
.....
.....
where 192.168.1.55 is the local ip for his smsc server, and 10.10.2.10
is my ip (yes, I've chage that!).
That's NAT, that's normal. But, I admit, I have forgot a lot about the
TCP stack since my apprentienceship, but doesn't CLOSE_WAIT mean, the
foreign side (you) closed the connection and the stack is waiting for
the LOCAL software to acknowledge the FIN?
http://en.wikipedia.org/wiki/File:Tcp_state_diagram_fixed.svg
Regards
Falko
