Re: [netnice-users] Rate Limiting with Netniced problems.

[Takashi O. <ta...@wi...>]

Hi Chris,

I suggest you to use gdb to check each step of the control, in the
second trial. It might be caused by bugs in netniced, or, by the
kernel module. I would appreciate if you rule out the former case,
by the stepwise execution. Then, if you're sure that it is caused
by the kernel, please let me know how to reproduce the bug, without
netniced. Actually, I'm working on the beta version of the package
right now, and it is highly likely that I can include the bug fix
in the latest version.

Thanks,

-- taka

P.S. You may directly send the materials to me. Or, you may switch to
another mailing list, netnice-developers. Thanks.

Christopher Garman wrote:
> I'm trying to test out the rate limiting facilities of netnice but I  am 
> having a few problems.  We are using netniced with the snort  module to 
> detect a "bad" process and then limit it.  For the first  experiment we 
> are limiting the rate of the process to zero.  This  way, we know if it 
> is working if there is no network activity.  The  process is 
> successfully rate limited one time.  If we restart the  process or the 
> experiment the next time we limit the process nothing  happens (by this 
> I mean there is no limitation of the traffic).  We  have to reboot the 
> machine in order for the limiting to work again.   If anyone has an idea 
> on what we might be doing wrong, or where the  problem might lie, let me 
> know.  I can provide the netnice.cf file to  anyone who wants to see it.
> 
> Thanks,
> 
> Chris
>