Hi,
I had been using RADIX_MPATH as well until investigated that problem was in
RADIX_MPATH. Also router had crashes after changing route weight (-weight key).
The code is very unstable, therefore I had to switch to use FIBs.
--
Cheers
> Hi all,
>
> I am facing some problems using RADIX_MPATH,
Hi all,
I am facing some problems using RADIX_MPATH, and quagga. Doing some
research I can see a some people had the same problem:
like this:
http://lists.freebsd.org/pipermail/freebsd-current/2011-August/026794.html
unfortunatelly the patch is not available anymore.
But this is not the worst p
> How do you plan to handle the fact that most of tcp_input() and
> tcp_do_segment() require at least a read lock held on the pcbinfo lock?
Yes, I realized that after some experiments yesterday.
> Is your goal to reduce the amount of code that gets executed under the write
> lock protection of pc
On 19/12/2012 6:40 PM, Vijay Singh wrote:
Sure but syncache_expand() is entered with the tcbinfo already write locked
which also protects the unlocking of the listening connection and the
locking of the newly created socket. Around this part:
/*
* Socket is created in
Hi!
Recently libradius(3) got long-awaited 'dead_time' option
that allows to skip 'dead' radius servers for 'dead_time' timeout
while dealing with multiple servers.
I'd like to ask for small improvement of the code.
Presently it will fail without a try if all servers marked 'dead'.
Instead, in t
