Date: Thu, 16 Sep 2004 03:49:01 -0000 From: pf-r@solarflux.org To: pf4freebsd@freelists.org Subject: [pf4freebsd] Re: 'Version' enhancement request Message-ID: <1062179079.3f4f9107b1d29@mail.fluidhosting.com> In-Reply-To: <004001c36e48$591c6680$01000001@max900> References: <006101c36dde$01cb64e0$01000001@max900> <1062160039.3f4f46a77d2d3@mail.fluidhosting.com> <004001c36e48$591c6680$01000001@max900>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks, Max. I've installed 1.63 and have verified that both methods work as
expected. Will add this info to the pf-r:
# dmesg|grep VER
pflog: $Name: VERSION_1_63 $
pfsync: $Name: VERSION_1_63 $
pfaltq: $Name: VERSION_1_63 $
pf: $Name: VERSION_1_63 $
# ident /sbin/pf*|grep VER (should get two responses, for pfctl and pflogd)
$Name: VERSION_1_63 $
$Name: VERSION_1_63 $
Max, /sbin/pftcpdump doesn't have a $Name: VERSION_1_63 string. Not sure about
any of the contrib binaries, haven't rebuilt pftop nor built any others to check.
-S
Quoting Max Laier <max@love2party.net>:
> Hello,
>
> good point! But we don't want to modify pfctl (or any of the sources) more
> than needed to make it work, hence I added another way to get version
> information:
> 1) The kernel modules will printf the following (watch your console or use
> dmesg(8)):
> pflog: $Name: VERSION_1_63 $
> pfsync: $Name: VERSION_1_63 $
> pfaltq: $Name: VERSION_1_63 $
> pf: $Name: VERSION_1_63 $
> 2) All binary files can be identified useing RCS ident(1):
> $ident /sbin/pfctl
> /sbin/pfctl:
> (...)
> $Name: VERSION_1_63 $
>
> I revised pf_freebsd_1.63.tar.gz new tarball has:
> MD5 (pf_freebsd_1.63.tar.gz) = cad275628e25058b6416457417cf93a6
>
> This might not be the cleanest possible way, but it works.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1062179079.3f4f9107b1d29>