> Ok interesting... You should NOT see thoose errors when you reboot!. But I > bet you don't have two ciscos running HSRP as we do at my web hosting > customer. However... It would probably (as for us) go away if you put IP:s > on the nics and don't just use the virtual ones OR install "arp ping" from > ports and run that from cron every 5 min.IF you test this I would really > like to have your results.... >
You're ritght: we don't have such router setup. We'll try to reboot the firewalls but I cannot assure we will be able to do so, because we need authorization. > > What type of nics do you have? There are fixes for some nics that could > cause problems like this. For xl nics (3com) for example.... If you have > unpatched xl driver for the pfsync interfaces... to bad.... And I am > talkning about 3.7 here. A stable 3.7 checkout could fix it if you use xl. > Check CVS and see. > We are using rl as external interfaces and fxp as internal interfaces for carp. Pfsync interfaces are rl, too. We might get a different setup for pf with pfsync and carp from a sysadmin. We will check the differences between his setup and ours, as he swears everything works perfect with his setup. Another question: Can P2P traffic create such a great amount of connections that we might run out of resources to keep the state of them? Could that be the reason of our problem with pfsync? Thanks again.
