SUMMARY UPDATE: how to know what options were built into kernel

I had a couple folks mention "nm" and "pfconfig"=0A=0AI did nm -a /vmunix |=
 grep -i packetfilter and it returned npacketfilter, so it =0Alooks to be i=
n the running kernel.=0A=0AThen I did pfconfig=A0and saw that non of the in=
terfaces had sniffing turned on, =0Aso I then set the primary interface to =
promiscuous mode with=0A=0Apfconfig=A0nr0 +promisc +copyall=A0=0A=0A=0A=0A-=
---- Original Message ----=0AFrom: Rich Glazier <[email protected]>=0A=
To: [email protected]=0ASent: Mon, November 22, 2010 5:33:08 PM=
=0ASubject: SUMMARY: how to know what options were built into kernel=0A=0AT=
hank you everyone, for your responses. I got a lot of good information, but=
 I =0Anever did effectively find out how to tell if PACKETFILER option is p=
art of my =0Arunning kernel, other than to run tcpdump and it worked! :)=A0=
Oddly, the =0A/dev/pfilt files were never created, but it seems to work. So=
me good advice I =0Agot from this was that there is a man page on setting u=
p packet filtering, man =0Apacketfilter.=0A=0A=0A=0A----- Original Message =
----=0AFrom: Rich Glazier <[email protected]>=0ATo: tru64-unix-manager=
[email protected]=0ASent: Thu, November 18, 2010 1:45:38 PM=0ASubject: how to know=
 what options were built into kernel=0A=0AI am trying to see if the PACKETF=
ILTER option was built into my running kernel.=A0 =0A=0A=0AUnder /sys/conf =
I see several kernel config files.=A0=A0The one that is my HOSTNAME, =0A=0A=
=0Adoes have "options PACKETFILTER", but how can I extrapulate this from =
=0A/usr/sys/HOSTNAME/vmunix (i.e./vmunix) to actually know it's in the kern=
el?=0A=0AThanks for the help,=0A=0ARich=0A=0A=0A