On Oct 30, 2006, at 7:47 AM, Christoph Kaegi wrote:

> On 26.10-20:24, Manuel Bouyer wrote:
>>>
>>> # sysctl -w net.inet.ip.ifq.maxlen=512
>>>
>>> I'll watch if this helps now.
>>
>> I would sent it even larger. If you have several wm(4) cards, I think
>> you should make this at last 256 * the number of adapters.
>
> I've set net.inet.ip.ifq.maxlen to 1024 on friday. Then, during the
> weekend, the machine seemed to forward less and less packets,
> until sunday evening, when it stopped completely forwarding.
>
> There was no Message on the console, in the kernel message buffer
> or in the logs. The machine just was stuck and didn't respond
> to network packets or even the keyboard anymore.
>
> What could be the reason for this?
> And, more importantly for me, how can I prevent this from occuring
> again or how can I measure this slow dying?

Maybe you run out of mbufs ?
netstat -m can help you. If you have a lot of calls to protocol drain  
routines, you need to bump NMBCLUSTERS.
Eitherway, if you reached mclpool limit, a message should've been  
printed in the console/dmesg.

--
Rui Paulo