On Monday 16 October 2006 17:25, Time Bandit wrote: > Same thing happens with a webserver. It listen for connections on port > 80 (default port) and when a connection comes in, it is handed to > another free port on the server so the "main" server can continue
You've got a very poor grasp on how things work. Please don't pretend to know what you're talking about. # netstat -apn | grep :80 tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 782/httpd tcp 0 0 204.xxx.yyy.188:80 80.xxx.yyy.167:58620 ESTABLISHED 814/httpd tcp 0 0 204.xxx.yyy.188:80 62.xxx.yyy.15:55384 ESTABLISHED 1068/httpd tcp 0 0 204.xxx.yyy.188:80 165.xxx.yyy.230:4392 ESTABLISHED 1084/httpd tcp 0 0 204.xxx.yyy.188:80 65.xxx.yyy.111:6982 TIME_WAIT - tcp 0 0 204.xxx.yyy.188:80 200.xxx.yyy.43:8198 ESTABLISHED 817/httpd tcp 0 0 204.xxx.yyy.188:80 165.xxx.yyy.230:4304 ESTABLISHED 815/httpd As you can see, I am *still* listening on port 80 and have numerous connections from different systems, even numerous connections from the same system. -A. _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
