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

[Rich Glazier]

I had a couple folks mention "nm" and "pfconfig"

I did nm -a /vmunix | grep -i packetfilter and it returned npacketfilter, so it
looks to be in the running kernel.

Then I did pfconfig and saw that non of the interfaces had sniffing turned on,
so I then set the primary interface to promiscuous mode with

pfconfig nr0 +promisc +copyall 

----- Original Message ----
From: Rich Glazier <rglazi...@yahoo.com>
To: tru64-uni...@ornl.gov
Sent: Mon, November 22, 2010 5:33:08 PM
Subject: SUMMARY: how to know what options were built into kernel

Thank you everyone, for your responses. I got a lot of good information, but I
never did effectively find out how to tell if PACKETFILER option is part of my
running kernel, other than to run tcpdump and it worked! :) Oddly, the
/dev/pfilt files were never created, but it seems to work. Some good advice I
got from this was that there is a man page on setting up packet filtering, man
packetfilter.

----- Original Message ----
From: Rich Glazier <rglazi...@yahoo.com>
To: tru64-uni...@ornl.gov
Sent: Thu, November 18, 2010 1:45:38 PM
Subject: how to know what options were built into kernel

I am trying to see if the PACKETFILTER option was built into my running kernel. 

Under /sys/conf I see several kernel config files.  The one that is my HOSTNAME,

does have "options PACKETFILTER", but how can I extrapulate this from
/usr/sys/HOSTNAME/vmunix (i.e./vmunix) to actually know it's in the kernel?

Thanks for the help,

Rich

[Rarback, Harvey M.]

Tru64 gurus,

My last Tru64 system and I are both retiring. I want to thank you all for the help and advice you all have rendered over the last twenty years. It's been fun.

--Harvey Rarback