Re: last call for L2/L3 rewrite code review

2008-12-10 Thread Marko Zec
On Wednesday 10 December 2008 10:30:35 Kip Macy wrote: > > The reason I am asking is that people are still seeing panics from > > the rnh locking and aren't even able to boot machines. > > I have not seen this. Please tell me where this occurs. I had a machine with defaultrouter from /etc/rc.conf

Re: last call for L2/L3 rewrite code review

2008-12-10 Thread Kip Macy
> The reason I am asking is that people are still seeing panics from > the rnh locking and aren't even able to boot machines. I have not seen this. Please tell me where this occurs. > Mixng route > locking bugs with this rewrite will be painful. As I hope that the > rnh bugs will be solved within

Re: last call for L2/L3 rewrite code review

2008-12-10 Thread Bjoern A. Zeeb
On Wed, 10 Dec 2008, Qing Li wrote: Hi, It's becoming increasingly difficult to maintain a separate branch (p4 or svn) due to the high volume of new features' related commits. The integration and unit testing efforts increase in complexity by the week. [..] I would like to commit the code w

Re: [ipsec] aes-ctr question

2008-12-10 Thread Eygene Ryabinkin
Yvan, good day. Wed, Dec 03, 2008 at 09:25:49AM +0100, VANHULLEBUS Yvan wrote: > On Wed, Dec 03, 2008 at 10:54:55AM +0300, Eygene Ryabinkin wrote: > [...] > > Good catch. Perhaps setkey should be extended to warn the user about > > this neat. The patch is attached. George, people, what do you t

Re: [help]strange problem about gethostbyname/getaddrinfo

2008-12-10 Thread Hajimu UMEMOTO
Hi, > On Wed, 10 Dec 2008 01:58:38 -0600 > "David DeSimone" <[EMAIL PROTECTED]> said: fox> It sounds like the resolver library is running into a 1024-descriptor fox> limit. From select(2): Our resolver doesn't use select(2) but use kqueue(2). So, we don't have this limitation. Sincere