trouble building FreeBSD 8.1 amd64 kernel with pfsync support

2010-08-11 Thread Cameron Simpson
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:

  MAKE=make sh /usr/src/sys/conf/newvers.sh NEW_FIREWALL cc -c -O2 
-frename-registers -pipe -fno-strict-aliasing  -std=c99 -g -Wall 
-Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes 
-Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign 
-fformat-extensions -nostdinc  -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq 
-D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=8000 --param inline-unit-growth=100 --param 
large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel 
-mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow  
-msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector 
-Werror  vers.c
  linking kernel.debug
  in_proto.o(.data+0x698): undefined reference to `pfsync_input'
  *** Error code 1

  Stop in /usr/obj/usr/src/sys/NEW_FIREWALL.
  *** Error code 1

  Stop in /usr/src.
  *** Error code 1

  Stop in /usr/src.

  real11m33.795s
  user7m19.405s
  sys 0m40.068s

Am I doing something obviously wrong here?

Cheers,
-- 
Cameron Simpson  DoD#743
http://www.cskk.ezoshosting.com/cs/

Once a Junior Programmer interrupted a Great Guru of the Sun to ask a
Question of no importance. The Great Guru replied in words which the Junior
Programmer did not understand. The Junior Programmer sought to rephrase the
Question, saying, "Stop me if I appear stupid." The great Guru, without
speaking, reached over and pressed L1-A.
The Junior Programmer achieved Enlightenment.   - Jon Green
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: trouble building FreeBSD 8.1 amd64 kernel with pfsync support

2010-08-11 Thread Rob Farmer
On Wed, Aug 11, 2010 at 12:20 AM, Cameron Simpson  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.

-- 
Rob Farmer

>
>  MAKE=make sh /usr/src/sys/conf/newvers.sh NEW_FIREWALL cc -c -O2 
> -frename-registers -pipe -fno-strict-aliasing  -std=c99 -g -Wall 
> -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes 
> -Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign 
> -fformat-extensions -nostdinc  -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq 
> -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
> -finline-limit=8000 --param inline-unit-growth=100 --param 
> large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel 
> -mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow  
> -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector 
> -Werror  vers.c
>  linking kernel.debug
>  in_proto.o(.data+0x698): undefined reference to `pfsync_input'
>  *** Error code 1
>
>  Stop in /usr/obj/usr/src/sys/NEW_FIREWALL.
>  *** Error code 1
>
>  Stop in /usr/src.
>  *** Error code 1
>
>  Stop in /usr/src.
>
>  real    11m33.795s
>  user    7m19.405s
>  sys     0m40.068s
>
> Am I doing something obviously wrong here?
>
> Cheers,
> --
> Cameron Simpson  DoD#743
> http://www.cskk.ezoshosting.com/cs/
>
> Once a Junior Programmer interrupted a Great Guru of the Sun to ask a
> Question of no importance. The Great Guru replied in words which the Junior
> Programmer did not understand. The Junior Programmer sought to rephrase the
> Question, saying, "Stop me if I appear stupid." The great Guru, without
> speaking, reached over and pressed L1-A.
> The Junior Programmer achieved Enlightenment.   - Jon Green
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: trouble building FreeBSD 8.1 amd64 kernel with pfsync support

2010-08-11 Thread Cameron Simpson
On 11Aug2010 01:36, Rob Farmer  wrote:
| On Wed, Aug 11, 2010 at 12:20 AM, Cameron Simpson  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  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 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: trouble building FreeBSD 8.1 amd64 kernel with pfsync support

2010-08-11 Thread Cameron Simpson
On 11Aug2010 19:30, I wrote:
| On 11Aug2010 01:36, Rob Farmer  wrote:
| | On Wed, Aug 11, 2010 at 12:20 AM, Cameron Simpson  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
[...]
| | > 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.

Victory! Thanks!

I'm a little surprised that the error I got:

  in_proto.o(.data+0x698): undefined reference to `pfsync_input'   

seemed to be a complaint about pfsync rather than missing pf stuff.

Cheers,
-- 
Cameron Simpson  DoD#743
http://www.cskk.ezoshosting.com/cs/

Tis better to have test ridden and lost, than to never have test ridden at all.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"