Re: CARP and pfsync weird behaviour

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: openbsd firewall
Date: Thursday, April 10, 2008 - 3:07 pm

Hello,

This got even more interesting. After reading your email I had the idea to
start turning off the various carp interfaces to see what would be the
effect.
I have two onboard "Broadcom BCM5704C" and a "Intel PRO/1000MT QP (82546GB)"
quad nic.
One carp is configured for one onboard nic and two other for the quad nic.
I removed the two carps for the quad nic at backup node and rebooted it a
few times. There are no failures in iperf test (I used a long time to make
sure it was always running between all the tests) which is the same as your
tests and normal expected result.
Removing the onboard carp and activating both or one of the quad nic carps
gives the failures I reported previously. Without pfsync active in the
master node, I get a  small failure in iperf tests while the backup node is
coming back. If I activate pfsync, I get the same small failure plus
sometimes a total mess up of iperf connection states.
So it seems the problem is happening with the quad nic. I don't see any
performance problems with the quad nic because I left iperf running for 2
days without any problem. CPU usage in interrupts is around 15% and load
0.20 while doing tests. The firewall is still not in production, so only
traffic is only my test and internet junk being dropped.
Kernel is GENERIC 4.2 without any patches (I don't see any of them relevant
to this problem). I doubt about any hardware problems because the same
happens if I exchange their roles as master and backup.

I can't understand how the backup node can generate these results with a
reboot. While writing this I remembered to do another test. I destroyed the
quad nic carps (with ifconfig carpX destroy) and then brought them back with
sh /etc/netstart. Iperf keeps running smoothly this time... Master node
receives the bulk update requests without any problems. Did this a few times
and nothing happened.
Even more weird now !!! Something is being done while those interfaces got
up for the first time after the reboot!
Any ideas ?

Thanks,
John

On 10/04/2008, Calomel <avertege@calomel.org> wrote:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
CARP and pfsync weird behaviour, openbsd firewall, (Thu Apr 10, 4:35 am)
Re: CARP and pfsync weird behaviour, Calomel, (Thu Apr 10, 10:14 am)
Re: CARP and pfsync weird behaviour, openbsd firewall, (Thu Apr 10, 3:07 pm)
Re: CARP and pfsync weird behaviour, Jason Dixon, (Thu Apr 10, 4:02 pm)
Re: CARP and pfsync weird behaviour, openbsd firewall, (Thu Apr 10, 4:08 pm)
Re: CARP and pfsync weird behaviour, Jason Dixon, (Thu Apr 10, 4:17 pm)
Re: CARP and pfsync weird behaviour, openbsd firewall, (Fri Apr 11, 7:25 am)
Re: CARP and pfsync weird behaviour, Jason Dixon, (Fri Apr 11, 7:42 am)
Re: CARP and pfsync weird behaviour, openbsd firewall, (Fri Apr 11, 8:10 am)
Re: CARP and pfsync weird behaviour, openbsd firewall, (Mon Apr 14, 7:01 am)
Re: CARP and pfsync weird behaviour, Henning Brauer, (Mon Apr 14, 8:07 am)