Bandwidthd issues
-
I get this response whenever i try to start bandwidthd…
Please start bandwidthd to populate this directory.
How do I go about this coz I cant see the bandwidthd graphs
Help please.
-
I would be worth looking at this thread: http://forum.pfsense.org/index.php/topic,49165.30.html
and this GitHub change: https://github.com/phil-davis/pfsense-packages/commit/c918257082611cc9d9e9f9987a0a317d629885d7
If you are on 2.1-RELEASE full install, that information might help you. I need to test a few permutations of 2.1 32 and 64 bit full installs to see what is really needed. My production systems are all nanoBSD CF card! -
Is BandwidthD listed in Status, Services? If so, is the service running?
-
I get this response whenever i try to start bandwidthd…
Please start bandwidthd to populate this directory.
How do I go about this coz I cant see the bandwidthd graphs
Help please.
-
Difficult to help with repeated questions and no answers.
-
- What pfSense version are you running? (2.0.n or 2.1)
- 32 or 64 bit?
- full install or nanoBSD on a CF card?
- Status->Services - does it show bandwidthd is running?
- System Log - what bandwidthd messages are there?
-
Apologies for resurrecting this thread.
I have the same issue as the OP, however, I'm able to add a few extra details and information :
pfSense version :
2.1-RELEASE (i386)
built on Wed Sep 11 18:16:22 EDT 2013
FreeBSD 8.3-RELEASE-p112. 32-bit version
3. Full install (running as a virtual machine)
4. Status - Services do show bandwidthd is running
5. System log - the last few messages I have from bandwidthd is
Mar 6 10:43:03 bandwidthd: Monitoring subnet 192.168.0.0 with netmask 192.168.0.0 Mar 6 10:43:03 bandwidthd: Monitoring subnet 192.168.48.0 with netmask 192.168.48.0 Mar 6 10:43:03 bandwidthd: Monitoring subnet 192.168.80.0 with netmask 192.168.80.0 Mar 6 10:43:03 bandwidthd: Opening em3 Mar 6 10:43:03 bandwidthd: Opening em3 Mar 6 10:43:03 bandwidthd: Opening em3 Mar 6 10:43:03 bandwidthd: Opening em3 Mar 6 10:43:03 bandwidthd: Packet Encoding: Ethernet Mar 6 10:43:03 kernel: em3: promiscuous mode enabled Mar 6 10:43:03 bandwidthd: Packet Encoding: Ethernet Mar 6 10:43:03 bandwidthd: Packet Encoding: Ethernet Mar 6 10:43:03 bandwidthd: Packet Encoding: Ethernet
I must add that it did work for about 4 to 5 hours before stopping. Now I only get the "has nothing to graph" message. >:(