trouble building FreeBSD 8.1 amd64 kernel with pfsync support
Cameron Simpson
cs at zip.com.au
Wed Aug 11 09:30:24 UTC 2010
On 11Aug2010 01:36, Rob Farmer <rfarmer at predatorlabs.net> wrote:
| On Wed, Aug 11, 2010 at 12:20 AM, Cameron Simpson <cs at zip.com.au> wrote:
| > I'm trying to build a kernel for a pair of firewalls which will be using
| > CARP and pfsync for redundancy. Since I'm new to FreeBSD the config is
| > based on the GENERIC config, thus:
| >
| > include GENERIC
| > ident NEW_FIREWALL
| > device carp
| > ##device pfsync
| >
| > and issuing the build like this:
| >
| > # cd /usr/src
| > # time make buildkernel KERNCONF=NEW_FIREWALL && echo YES
| >
| > With the config above (CARP but no pfsync) it builds just fine
| > and boots and runs happily; I've got CARP configured.
| >
| > If I uncomment the "devic pfsync" the build aborts at link time ending thus:
|
| Do you also have a "device pf" line? I think that is a prereq for
| pfsync. You may also need "device pflog" - I'm not sure because I've
| always just added them all.
Hmm. [greps GENERIC...] No, I don't. I figured that since pfctl was
working I was ok there, but I think it loads the module dynamicly. I can see
that if pfsync needs a static build it may rely on pf and pflog being static
also. I'll try that now and report.
Thanks,
--
Cameron Simpson <cs at zip.com.au> DoD#743
http://www.cskk.ezoshosting.com/cs/
Trust the computer industry to shorten Year 2000 to Y2K. It was this
thinking that caused the problem in the first place.
- Mark Ovens <marko at uk.radan.com>
More information about the freebsd-questions
mailing list