This looked like just the ticket for me, so I install the package. No obvious errors, but checking shows the program not running. I try manually starting it and it complains that libpng.so.5 is missing. I try 'pkg_add -r libpng' from a command prompt, and get this:
Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7.2-release/Latest/libpng.tbz: File unavailable (e.g., file not found, no access)
pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7.2-release/Latest/libpng.tbz' by URL
Boy, is this my lucky day. I decided to give ntop a shot instead. Guess what? It's broken too! And here is why:
Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7.2-release/Latest/libfreetype.tbz: File unavailable (e.g., file not found, no access)
pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7.2-release/Latest/libfreetype.tbz' by URL
I'm guessing I am running into package repo breakage and not package breakage here? More than a little frustrated :(
Okay, it IS package breakage. I found that libfreetype.so (or whatever) is in freetype2, not libfreetype. So I installed that manually and it still didn't work. That turned out to be libpng just like bandwidthd. I then installed png instead of libpng and now it is running. A little frustrated that something this basic was committed to the repo :(
What version of pfSense are you trying this on?
It's possible the package as it exists was intended for an older version of pfSense and hasn't been updated (or vice versa and it expects a newer one)
Maybe looking for a libpng.so.? and manually linking to the found lib will help:
find / -name "libpng.so.?", when it finds a /lib/libpng.so.4 you van do a ln -s /lib/libpng.so.4 /lib/libpng.so.5.
And so on for other missing libs.
This is 1.2.3 RC3 on a full install.
Igor, maybe I wasn't clear. The problem is that the package installer is trying to download the wrong files. For example, it is trying to ftp libfreetype, but the library is actually in freetype2. And ntop is trying to do the same thing, along with trying to get libpng via ftp when the package to install is png. It all works now, once I loaded the correct names. I did:
pkg_add -r png
pkg_add -r freetype2
and then re-did the bandwidthd and ntop installs (I did both because I want to test drive both).
This is even weirder than I thought. I created a VM and installed pfsense into it and both packages install fine. I reinstalled the VM with no packages and found:
so, apparently those come preinstalled, NOT installed by the package requirements, so much of this was a red herring (sorry!). That begs the question of why my production install didn't have either of those libraries :( At least I know how to get around this for now. Sorry for the false alarm.
The only thing I recall being odd about my production install was that the easy install didn't work - I had to nuke the first N blocks on the disk and then it installed. Oh well, a mystery…
Seems to work for me on a 1.2.3-RC system updated last Saturday.
The package add went fine, and it starts up and runs:
ov 20 09:32:35 pfSense-123test php: /pkg_mgr_install.php: Beginning package installation for bandwidthd. Nov 20 09:32:50 pfSense-123test php: /pkg_mgr_install.php: You should specify a interface for bandwidthd to listen on. exiting. Nov 20 09:32:52 pfSense-123test bandwidthd: Opening fxp0 Nov 20 09:32:52 pfSense-123test kernel: fxp0: promiscuous mode enabled Nov 20 09:32:52 pfSense-123test bandwidthd: Opening fxp0 Nov 20 09:32:52 pfSense-123test bandwidthd: Packet Encoding: Ethernet Nov 20 09:32:52 pfSense-123test bandwidthd: Opening fxp0 Nov 20 09:32:52 pfSense-123test bandwidthd: Opening fxp0 Nov 20 09:32:52 pfSense-123test bandwidthd: Packet Encoding: Ethernet Nov 20 09:33:24 pfSense-123test kernel: fxp0: promiscuous mode disabled Nov 20 09:32:52 pfSense-123test last message repeated 2 times Nov 20 09:33:26 pfSense-123test bandwidthd: Monitoring subnet 192.168.30.0 with netmask 192.168.30.0 Nov 20 09:33:26 pfSense-123test kernel: fxp0: promiscuous mode enabled Nov 20 09:33:26 pfSense-123test kernel: vlan1: promiscuous mode enabled Nov 20 09:33:26 pfSense-123test bandwidthd: Opening vlan1 Nov 20 09:33:26 pfSense-123test bandwidthd: Opening vlan1 Nov 20 09:33:26 pfSense-123test bandwidthd: Packet Encoding: Ethernet Nov 20 09:33:26 pfSense-123test bandwidthd: Packet Encoding: Ethernet Nov 20 09:33:26 pfSense-123test bandwidthd: Opening vlan1 Nov 20 09:33:26 pfSense-123test bandwidthd: Opening vlan1 Nov 20 09:33:26 pfSense-123test bandwidthd: Packet Encoding: Ethernet
(Though the subnet mask is printed incorrectly…)
This is a testing box so it has a few other random packages on it, which might explain the difference
# pkg_info bandwidthd-2.0.1_1 Tracks bandwidth usage by IP address daemontools-0.76_12 Service monitoring and logging utilities by djb db41-4.1.25_4 The Berkeley DB package, revision 4.1 denyhosts-2.5 Script to thwart ssh attacks djbdns-1.05_12 A collection of secure and reliable DNS tools gd-2.0.35,1 A graphics library for fast creation of images grub-0.97_3 GRand Unified Bootloader host-991529 An utility to query DNS servers jpeg-6b_4 IJG's jpeg compression utilities libiconv-1.11_1 A character set conversion library mbmon-205_4 A tty motherboard monitor for LM78/79, W8378x, AS99127F, VT openldap-client-2.4.10 Open source LDAP client implementation openldap-client-2.4.11 Open source LDAP client implementation packages BSD Installer mega-package perl-5.8.8_1 Practical Extraction and Report Language python24-2.4.3_3 An interpreted object-oriented programming language squid-2.6.21 HTTP Caching Proxy squidGuard-1.3_1 A fast redirector for squid squid_radius_auth-1.10 RADIUS authenticator for squid proxy 2.5 and later stunnel-4.25 SSL encryption wrapper for standard network daemons tcpflow-0.21_1 A tool for capturing data transmitted as part of TCP connec ucspi-tcp-0.88_2 Command-line tools for building TCP client-server applicati
I don't have a fresh install to try at the moment.
yes, a mystery. i have tried on 3 different virtual machines and it works fine everytime. must have been some kind of odd glitch when i did that first install. sigh…