I've been using SSH to forward a port on a machine to inside a private network using SSH. I've been noticing that for some reasons the connections that are made via this seem to stay open... (SSH is supposed to keep the redirection enabled at all times) The attatchment shows an example of this. Has anyone seen this behavior before? Does anyone have any suggestions on how to keep this from happening (while keeping the same functionality) Matthew Matthew Phelps Walker mwalker@cstonesystems.com (812) 423-7676 http://www.cstonesystems.com Matthew Matthew Phelps Walker mwalker@cstonesystems.com (812) 423-7676 http://www.cstonesystems.com
-- BEGIN included message
- To: mwalker@mail.cstonesystems.com
- From: mwalker@cstonesystems.com
- Date: Sun, 15 Mar 1998 21:19:05 -0600
Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 localhost:1023 localhost:22 ESTABLISHED tcp 0 0 localhost:22 localhost:1023 ESTABLISHED tcp 0 0 titan.cstonesystem:1234 pm22-s15-tier1.eva:1229 ESTABLISHED tcp 0 0 titan.cstonesystem:2571 192.168.97.2:www ESTABLISHED tcp 0 0 titan.cstonesystem:1234 pm22-s15-tier1.eva:1232 ESTABLISHED tcp 0 0 titan.cstonesystem:2632 192.168.97.2:www ESTABLISHED tcp 0 0 titan.cstonesystem:1234 pm22-s15-tier1.eva:1234 ESTABLISHED tcp 0 0 titan.cstonesystem:2634 192.168.97.2:www ESTABLISHED tcp 0 0 titan.cstonesystem:1234 pm22-s15-tier1.eva:1236 ESTABLISHED tcp 0 0 titan.cstonesystem:2677 192.168.97.2:www ESTABLISHED tcp 0 0 titan.cstonesystem:1234 pm22-s15-tier1.eva:1238 ESTABLISHED tcp 0 0 titan.cstonesystem:2679 192.168.97.2:www ESTABLISHED tcp 0 0 titan.cstonesystem:1234 pm22-s15-tier1.eva:1240 ESTABLISHED tcp 0 0 titan.cstonesystem:2681 192.168.97.2:www ESTABLISHED tcp 0 0 titan.cstonesystem:1234 pm22-s15-tier1.eva:1242 ESTABLISHED tcp 0 0 titan.cstonesystem:2725 192.168.97.2:www ESTABLISHED tcp 0 0 titan.cstonesystem:1234 ts4.dyn149.dynast:63800 ESTABLISHED tcp 0 0 titan.cstonesystem:3564 192.168.97.2:www ESTABLISHED tcp 0 0 titan.cstonesystem:1234 ts4.dyn149.dynast:63825 CLOSE tcp 0 0 titan.cstonesystem:3823 192.168.97.2:www CLOSE tcp 0 4380 titan.cstonesystem:1234 ts4.dyn149.dynast:63828 CLOSE tcp 0 0 titan.cstonesystem:1234 ts4.dyn149.dynast:63829 CLOSE tcp 0 0 titan.cstonesystem:3829 192.168.97.2:www CLOSE tcp 0 0 titan.cstonesystem:3830 192.168.97.2:www CLOSE tcp 0 1 titan.cstonesystem:1234 ts4.dyn103.dynast:64047 CLOSE tcp 0 1 titan.cstonesystem:1234 ts4.dyn103.dynast:64056 CLOSE tcp 0 1 titan.cstonesystem:1234 ts4.dyn103.dynast:64057 CLOSE tcp 0 1 titan.cstonesystem:1234 ts4.dyn103.dynast:64058 CLOSE tcp 0 0 titan.cstonesystem:8250 192.168.97.2:www FIN_WAIT2 tcp 0 0 titan.cstonesystem:8251 192.168.97.2:www FIN_WAIT2 tcp 0 1 titan.cstonesystem:1234 ts4.dyn103.dynast:64059 CLOSE tcp 0 1 titan.cstonesystem:1234 ts4.dyn103.dynast:64061 CLOSE tcp 0 1 titan.cstonesystem:1234 ts4.dyn103.dynast:64062 CLOSE tcp 0 0 titan.cstonesystem:8254 192.168.97.2:www FIN_WAIT2 tcp 0 0 titan.cstonesystem:8255 192.168.97.2:www FIN_WAIT2 tcp 0 0 titan.cstonesystem:8256 192.168.97.2:www FIN_WAIT2 tcp 0 0 titan.cstonesystem:8257 192.168.97.2:www FIN_WAIT2 tcp 0 0 titan.cstonesystem:8273 192.168.97.2:www FIN_WAIT2 tcp 0 0 titan.cstonesystem:1234 ts4.dyn103.dynast:64107 CLOSE tcp 0 0 titan.cstonesystem:8313 192.168.97.2:www FIN_WAIT2 tcp 0 0 titan.cstonesystem:1234 ts4.dyn148.dynast:64292 FIN_WAIT2 tcp 0 0 titan.cstonesyste:10391 192.168.97.2:www CLOSE_WAIT tcp 0 0 titan.cstonesystem:1234 208.205.50.170:61175 FIN_WAIT2 tcp 0 0 titan.cstonesyste:23060 192.168.97.2:www CLOSE_WAIT tcp 0 0 titan.cstonesystem:1234 208.205.50.170:61196 FIN_WAIT2 tcp 0 0 titan.cstonesyste:23509 192.168.97.2:www CLOSE_WAIT tcp 0 0 titan.cstonesystem:1234 pm05-s16-tier1.eva:1186 CLOSE_WAIT tcp 0 0 titan.cstonesyste:24302 192.168.97.2:www FIN_WAIT2 tcp 0 0 titan.cstonesystem:1234 208.205.50.170:61252 FIN_WAIT2 tcp 0 0 titan.cstonesyste:24683 192.168.97.2:www CLOSE_WAIT tcp 0 20 titan.cstonesystems.:22 208.205.50.170:1023 ESTABLISHED
-- END included message