I use FreeBSD 7.2 with CUSTOM variant of GENERIC kernel. I added to my kernel a few of ALTQ options required by pf.
After the update of the system I encountered some problems with pf...
Here are my ALTQ options:
Here are my upadte logs:
# freebsd-update fetch
# freebsd-update install
Before the update I saw during the boot procedures these messages:
After the update I see during the boot procedures these messages:
Modules pf and pflog are still in the same place:
# cd /boot/kernel
# ls pf*
So I have two questions:
* Assuming that pf isn’t loaded during the boot procedures is it safe to connect my FreeBSD box to Internet before repairing the system (I ask that question from within Linux box)?
* What should I do to restore the valid work of pf and pflog modules?
After the update of the system I encountered some problems with pf...
Here are my ALTQ options:
Code:
options ALTQ
options ALTQ_CBQ # Class Bases Queuing (CBQ)
options ALTQ_RED # Random Early Detection (RED)
options ALTQ_RIO # RED In/Out
options ALTQ_HFSC # Hierarchical Packet Scheduler (HFSC)
options ALTQ_PRIQ # Priority Queuing (PRIQ)
options ALTQ_NOPCC # Required for SMP build
Here are my upadte logs:
# freebsd-update fetch
Code:
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching public key from update5.FreeBSD.org... done.
Fetching metadata signature for 7.2-RELEASE from update5.FreeBSD.org... done.
Fetching metadata index... done.
Fetching 2 metadata files... done.
Inspecting system... done.
Preparing to download files... done.
Fetching 29 patches.....10....20.... done.
Applying patches... done.
Fetching 6 files... done.
The following files will be updated as part of updating to 7.2-RELEASE-p3:
/boot/kernel/if_bce.ko
/boot/kernel/if_bce.ko.symbols
/boot/kernel/if_fxp.ko
/boot/kernel/if_fxp.ko.symbols
/boot/kernel/kernel
/boot/kernel/kernel.symbols
/lib/libc.so.7
/lib/libthr.so.3
/rescue/[
/rescue/atacontrol
/rescue/atmconfig
/rescue/badsect
/rescue/bsdlabel
/rescue/bunzip2
/rescue/bzcat
/rescue/bzip2
/rescue/camcontrol
/rescue/cat
/rescue/ccdconfig
/rescue/chflags
/rescue/chio
/rescue/chmod
/rescue/chroot
/rescue/clri
/rescue/cp
/rescue/csh
/rescue/date
/rescue/dd
/rescue/devfs
/rescue/df
/rescue/dhclient
/rescue/disklabel
/rescue/dmesg
/rescue/dump
/rescue/dumpfs
/rescue/dumpon
/rescue/echo
/rescue/ed
/rescue/ex
/rescue/expr
/rescue/fastboot
/rescue/fasthalt
/rescue/fdisk
/rescue/fsck
/rescue/fsck_4.2bsd
/rescue/fsck_ffs
/rescue/fsck_msdosfs
/rescue/fsck_ufs
/rescue/fsdb
/rescue/fsirand
/rescue/gbde
/rescue/getfacl
/rescue/groups
/rescue/gunzip
/rescue/gzcat
/rescue/gzip
/rescue/halt
/rescue/hostname
/rescue/id
/rescue/ifconfig
/rescue/init
/rescue/ipf
/rescue/kenv
/rescue/kill
/rescue/kldconfig
/rescue/kldload
/rescue/kldstat
/rescue/kldunload
/rescue/ldconfig
/rescue/link
/rescue/ln
/rescue/ls
/rescue/md5
/rescue/mdconfig
/rescue/mdmfs
/rescue/mkdir
/rescue/mknod
/rescue/mount
/rescue/mount_cd9660
/rescue/mount_msdosfs
/rescue/mount_nfs
/rescue/mount_ntfs
/rescue/mount_nullfs
/rescue/mount_udf
/rescue/mount_unionfs
/rescue/mv
/rescue/newfs
/rescue/newfs_msdos
/rescue/nos-tun
/rescue/pax
/rescue/ping
/rescue/ping6
/rescue/ps
/rescue/pwd
/rescue/rcorder
/rescue/rcp
/rescue/rdump
/rescue/realpath
/rescue/reboot
/rescue/red
/rescue/rescue
/rescue/restore
/rescue/rm
/rescue/rmdir
/rescue/route
/rescue/routed
/rescue/rrestore
/rescue/rtquery
/rescue/rtsol
/rescue/savecore
/rescue/sconfig
/rescue/setfacl
/rescue/sh
/rescue/slattach
/rescue/spppcontrol
/rescue/startslip
/rescue/stty
/rescue/swapon
/rescue/sync
/rescue/sysctl
/rescue/tar
/rescue/tcsh
/rescue/test
/rescue/tunefs
/rescue/umount
/rescue/unlink
/rescue/vi
/rescue/whoami
/rescue/zcat
/sbin/devd
/sbin/init
/usr/bin/ar
/usr/bin/as
/usr/bin/cc
/usr/bin/gcc
/usr/bin/ld
/usr/bin/make
/usr/bin/ranlib
/usr/lib/libc.a
/usr/lib/libc_p.a
/usr/lib/libc_pic.a
/usr/lib/libkse.so.3
/usr/libexec/cc1
/usr/libexec/cc1obj
/usr/libexec/cc1plus
/usr/sbin/lwresd
/usr/sbin/named
/usr/sbin/nologin
/usr/sbin/ntpd
/usr/src/contrib/bind9/bin/named/update.c
/usr/src/contrib/ntp/ntpd/ntp_crypto.c
/usr/src/lib/libc/stdlib/malloc.c
/usr/src/sys/conf/newvers.sh
/usr/src/sys/dev/bce/if_bce.c
/usr/src/sys/dev/fxp/if_fxp.c
/usr/src/sys/kern/sys_pipe.c
/usr/src/sys/netinet6/in6.c
# freebsd-update install
Code:
Installing updates... done.
Before the update I saw during the boot procedures these messages:
Code:
Starting pflog.
pflog0: promiscuous mode enabled
Enabling pf.
Sep 25 22:48:45 pflogd[314]: [priv]: msg PRIV_OPEN_LOG received
pf enabled
After the update I see during the boot procedures these messages:
Code:
link_elf: symbol altq_disable undefined
KLD pflog.ko: depends on pf - not available
kldload: can't load pflog: No such file or directory
/etc/rc: WARNING: Unable to load kernel module pflog
link_elf: symbol altq_disable undefined
kldload: can't load pf: No such file or directory
/etc/rc: WARNING: Unable to load kernel module pf
Modules pf and pflog are still in the same place:
# cd /boot/kernel
# ls pf*
Code:
pf.ko
pf.ko.symbols
pflog.ko
pflog.ko.symbols
So I have two questions:
* Assuming that pf isn’t loaded during the boot procedures is it safe to connect my FreeBSD box to Internet before repairing the system (I ask that question from within Linux box)?
* What should I do to restore the valid work of pf and pflog modules?