Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 10 Sep 2005 00:13:13 +0100
From:      Dominic Marks <dom@goodforbusiness.co.uk>
To:        Max Laier <max@love2party.net>
Cc:        freebsd-hackers@freebsd.org, dominic.marks@graphdata.co.uk, Dominic Marks <dom@helenmarks.co.uk>
Subject:   Re: FreeBSD 6.0-BETA4 panics when when configuring pfsync0
Message-ID:  <200509100013.14759.dom@goodforbusiness.co.uk>
In-Reply-To: <200509100101.13974.max@love2party.net>
References:  <2845.195.12.22.194.1126261787.squirrel@www.helenmarks.co.uk> <200509091919.22875.max@love2party.net> <200509100101.13974.max@love2party.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 10 September 2005 00:00, Max Laier wrote:
> On Friday 09 September 2005 19:19, Max Laier wrote:
> > On Friday 09 September 2005 15:05, Dominic Marks wrote:
> > > Dominic Marks wrote:
> > > > Hello,
> > > >
> > > > I am setting up a redundant firewall setup for our company, the
> > > > systems are identically configured Dell servers running FreeBSD
> > > > 6.0-BETA4. Software being used is pf, carp, pfsync and altq.
> > > >
> > > > When I attempt to configure the pfsync0 interface the systems
> > > > panic. The systems currently have HTT enabled, I've googled but
> > > > I didn't find anything to suggest pfsync was not SMP/HTT
> > > > friendly. Could this be a configuration problem?
> > > >
> > > > interface:
> > > >
> > > > # ifconfig em2
> > > > em2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu
> > > > 1500 options=b<RXCSUM,TXCSUM,VLAN_MTU>
> > > >         inet 172.16.254.2 netmask 0xffffff00 broadcast
> > > > 172.16.254.255 ether 00:04:23:bd:7a:ef
> > > >         media: Ethernet autoselect (100baseTX <full-duplex>)
> > > >         status: active
> > > >
> > > > command:
> > > >
> > > > # ifconfig pfsync0 syncdev em2 syncpeer 172.16.254.1
> > >
> > > Following a little more testing:
> > >
> > > If I don't specify a syncpeer I don't get the panic.
> >
> > Thanks for the dump.  Seems like we were leaking a lock from
> > pfsyncioctl(). Can you please try this patch and report back. 
> > Thanks in advance.

AWESOME!!

I'll test this on Monday when I'm back at work and report on the 
outcome.

> And the patch ... sorry.

:)

-- 
Dominic Marks



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200509100013.14759.dom>