On the trail of a dummynet/bridge/ipfw bug.
AT Matik
asstec at matik.com.br
Fri Mar 14 07:46:31 UTC 2008
On Thursday 13 March 2008 18:06:40 Wade Klaver wrote:
> OK, here's something weird then. ipfw pipe show | wc -l has reported
> higher numbers:
> [root at ibm3550b ~]# ipfw pipe show | wc -l
> 3453
> This was reported after the bridge "died" attempting 2600 simultaneous
> connections... it had been running at 2400 before I added 200 more.
> Now, immediately after the above crash, I do a /etc/rc.d/netif restart,
> and then:
> [root at ibm3550b ~]# ipfw pipe show | wc -l
> 3900
> Then as long as I add additional connections very slowly, I can manage
> to get more established until it dies at 2800 with:
> [root at ibm3550b ~]# ipfw pipe show | wc -l
> 4160
> At this point I am only using these numbers as a general indication of
> pipe activity as the output is not 1 pipe per line. In fact there is
> more often than not two lines per pipe. However, the end problem
> remains the same. After a point, the bridge doesn't get saturated, it
> crashes and requires that the network be restarted before continuing.
> The fact that it is necessary only to restart the network and not to
> flush ipfw's pipes (which has no effect without a network restart)
> perhaps suggests the problem lies in a different subsystem? The
> broadcom driver perhaps?
hard to say because you do not tell so very much about your machine, it might
be too weak for so many pipes (mem or cpu?), I do not know your setup or the
nics you use
you say it crash but can restart the network? probably you have some error in
your script or since you run bridge some mac issue?
--
Participe no BAIXO ASSINADO SCM:
http://info.matik.com.br
--
Atenciosamente, J.M.
Responsável Plantão Site Support Matik
Infomatik Internet Technology
(18)3551.8155 (18)8112.7007
A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura.
Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br
More information about the freebsd-ipfw
mailing list