This actually sounds like a problem I hit once where the default settings actually restrict the number of ports.
net.inet.ip.portrange.lowfirst: 1023 net.inet.ip.portrange.lowlast: 600 net.inet.ip.portrange.first: 1024 net.inet.ip.portrange.last: 5000 net.inet.ip.portrange.hifirst: 49152 net.inet.ip.portrange.hilast: 65535 specifically, portrange.first and portrange.last are set a bit low for some applications. By default you only get 5000-1024 ports (3976). set net.inet.ip.portrange.last=16384 or higher to get more ports. - Mark On Wed, Oct 10, 2001 at 08:46:38AM -0700, John Polstra wrote: > In article <[EMAIL PROTECTED]>, > Nguyen-Tuong Long Le <[EMAIL PROTECTED]> wrote: > > > > I have a software that simulates web clients and servers to create > > network congestion (for the purpose of doing research in network > > congestion). In our experiment, a client opens an HTTP connection > > to a server, fetches a number of objects, and then closes the > > connection. A problem I seem to have right now is that a client > > machine cannot simulate more than 3000 connections. When my client > > machine simulates more than 3000 connections, it's able to open > > a socket but then connect(2) fails with errno 35 (Resource > > temporarily unavailable). Another interesting notice is that the > > connect(2) system call blocks for a few miliseconds before it > > fails although fcntl(2) was used to make the socket non-blocking. > > The OS version I am using is FreeBSD 4.3-release. > > In addition to the suggestion from Alex Rousskov, adding these lines > to "/boot/loader.conf" may help: > > kern.ipc.maxsockets="8192" > kern.ipc.nmbclusters="32768" > > John > -- > John Polstra > John D. Polstra & Co., Inc. Seattle, Washington USA > "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
