Re: Tor relay on vserver exeeding numtcpsock
Am Mittwoch, 12. Januar 2011, um 22:44:12 schrieb Moritz Bartl: Hi, You should probably contact the ISP first to see if they will raise the limit. Mine was low on file descriptors and they upped it generously 5 minutes later (on a cheap $20 vserver). Moritz Thanks for all your suggestions. This morning I contacted the HostEurope support. They were very friendly but refused to increase the parameter. They told me that the product is designed this way and they cannot change anything. They advised me to order a product with a higher number of tcp sockets. But even the high-end vserver product for EUR 70 ($90) per month only provides 1550 tcp connections (http://faq.hosteurope.de/index.php?cpid=13281). All these HostEurope vserver products are crippled regarding numtcpsock. Bottom line: HostEuropes vserver cannot be recommended for tor relays. I will update the wiki accordingly. I will move to another ISP. In the meantime I will play around with the ConstrainedSocksSize parameter to get the most out of the vserver. Moritz, from which ISP did you get this $20 vserver? Regards, Klaus -- Klaus Layer Walldorf, Germany GPG Fingerprint: 466D 12F8 28A3 D137 A77E FC3B 271C 2D79 6F5E 94C9 signature.asc Description: This is a digitally signed message part.
Re: Tor relay on vserver exeeding numtcpsock
On 12.01.2011 22:02, coderman wrote: On Wed, Jan 12, 2011 at 7:57 AM, Klaus Layer klaus.la...@gmx.de wrote: ... Error creating network socket: No buffer space available errors. The numtcpsocks parameter limit is set to 550 on the vserver. Before asking the ISP to increase the value I would like to ask you what a reasonable value of this parameter would be. 550 is ridiculous. it should be at least 4096, more if they are accomodating. here's some data for the machine running my four nodes: anonymizer2:~# netstat -tn | wc -l 54157 anonymizer2:~# netstat -tn | grep ESTABLISHED | wc -l 30708 regards Olaf *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: Tor relay on vserver exeeding numtcpsock
2011/1/13 Olaf Selke olaf.se...@blutmagie.de: On 12.01.2011 22:02, coderman wrote: On Wed, Jan 12, 2011 at 7:57 AM, Klaus Layer klaus.la...@gmx.de wrote: ... Error creating network socket: No buffer space available errors. The numtcpsocks parameter limit is set to 550 on the vserver. Before asking the ISP to increase the value I would like to ask you what a reasonable value of this parameter would be. 550 is ridiculous. it should be at least 4096, more if they are accomodating. here's some data for the machine running my four nodes: anonymizer2:~# netstat -tn | wc -l 54157 anonymizer2:~# netstat -tn | grep ESTABLISHED | wc -l 30708 regards Olaf *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talk in the body. http://archives.seul.org/or/talk/ Well, I don't think a cheap VPS is capable of creating this much connections anyways. I got a relay with a limit of 800kb/sec (I don't think a cheap VPS can do more traffic due to traffic limitations) and I got this: jan@puerta:~$ netstat -tn | wc -l 1002 jan@puerta:~$ netstat -tn | grep ESTABLISHED | wc -l 976 But I would agree that diversity is needed and good, and there are plenty of ISPs out there. I would advice to look for a smaller one. Those are often more helpful if you have got some special requests. best regards, Jan *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Tor relay on vserver exeeding numtcpsock
Hi all, after running 2 tor relays over dialup connections for several weeks, I recently ordered a vserver (Hosteurope Virtual Server Linux L 4.0) and setup a middleman tor relay. Very fast the vserver run into shortage of tcp sockets which indicate lots of Error creating network socket: No buffer space available errors. The numtcpsocks parameter limit is set to 550 on the vserver. Before asking the ISP to increase the value I would like to ask you what a reasonable value of this parameter would be. The tor wiki describe several parameters and values for SWSoft's Virtuozzo here https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Virtualserver but for numtcpsock a recommendation is missing. Thanks for your help. Klaus -- Klaus Layer Walldorf, Germany GPG Fingerprint: 466D 12F8 28A3 D137 A77E FC3B 271C 2D79 6F5E 94C9 signature.asc Description: This is a digitally signed message part.
Re: Tor relay on vserver exeeding numtcpsock
On Wed, Jan 12, 2011 at 7:57 AM, Klaus Layer klaus.la...@gmx.de wrote: ... Error creating network socket: No buffer space available errors. The numtcpsocks parameter limit is set to 550 on the vserver. Before asking the ISP to increase the value I would like to ask you what a reasonable value of this parameter would be. 550 is ridiculous. it should be at least 4096, more if they are accomodating. you may or may not find the ConstrainedSocksSize option useful as well. good luck! you may want to update the good / bad ISP entry with your experience. *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: Tor relay on vserver exeeding numtcpsock
Hi, You should probably contact the ISP first to see if they will raise the limit. Mine was low on file descriptors and they upped it generously 5 minutes later (on a cheap $20 vserver). Moritz On 12.01.2011 22:02, coderman wrote: Error creating network socket: No buffer space available errors. The numtcpsocks parameter limit is set to 550 on the vserver. 550 is ridiculous. it should be at least 4096, more if they are accomodating. good luck! you may want to update the good / bad ISP entry with your experience. *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: Tor relay on vserver exeeding numtcpsock
I believe that Klaus is already planning to contact his ISP, and was seeking to learn more about reasonable values for numtcpsock. Unfortunately different ISPs do this in different ways, and some cannot easily change just that parameter in isolation. Before paying much money for a numtcpsock increase (my ISP charges a lot for this) it is worth considering whether the increase in numtcpsock will greatly increase the utility of the relay. If the numtcpsock increase is cheap or free, then of course one would go for the most sockets one can get. In my case I find that when I trim my bandwidth to about what I can afford per month I need ballpark of the number of sockets that I am currently permitted. Unfortunately this balance changes with each new version of Tor. I'm not exactly sure why, but I wonder whether performance improvements mean that I can handle more circuits at a time, making the number of sockets the limiting factor again. Does anybody here know whether this is so? On Wed, Jan 12, 2011 at 4:44 PM, Moritz Bartl mor...@torservers.net wrote: Hi, You should probably contact the ISP first to see if they will raise the limit. Mine was low on file descriptors and they upped it generously 5 minutes later (on a cheap $20 vserver). Moritz On 12.01.2011 22:02, coderman wrote: Error creating network socket: No buffer space available errors. The numtcpsocks parameter limit is set to 550 on the vserver. 550 is ridiculous. it should be at least 4096, more if they are accomodating. good luck! you may want to update the good / bad ISP entry with your experience. *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talk in the body. http://archives.seul.org/or/talk/ -- Sincerely Yours, ---Thomas S. Benjamin *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
