• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

pfSense 2.0 BandwidthD not working

AMD_Gamer

Fully [H]
Joined
Jan 20, 2002
Messages
18,287
Ok BandwidthD is not working on my new pfSense 2.0 box. The box has been rock solid and been up for almost a week now. Has anyone ran into this problem before?
 
"Doesn't work" isn't very descriptive.lol

I've had BandwidthD not work in several interesting ways.

I'd recommend taking a look at the raw logs and the raw config file (usually in /var/log and /etc) and see if the config file looks right there and that there isn't any error spam about it.
 
Did you set it up? It's not an install and it works package. You need to select a NIC to watch.
 
Yes i set it up and selected the LAN. I had it working great before. This started with pfSense 2.0.
 
Did you do a fresh install or a "firmware upgrade" to 2.0? I've always had issues with the upgrades in the PFSense, but fresh installs have always been flawless.
 
I restarted the service and see nothing wrong

When i click on Access BandwidthD i get the page but it is always this "bandwidthd has nothing to graph. This message should be replaced by graphs in a few minutes. If it's not, please see the section titled "Known Bugs and Troubleshooting" in the README "

Oct 4 02:34:44 bandwidthd: Monitoring subnet 192.168.1.0 with netmask 192.168.1.0
Oct 4 02:34:44 bandwidthd: Monitoring subnet 192.168.1.0 with netmask 192.168.1.0
Oct 4 02:34:44 bandwidthd: Opening em0
Oct 4 02:34:44 bandwidthd: Opening em0
Oct 4 02:34:44 bandwidthd: Opening em0
Oct 4 02:34:44 kernel: em0: promiscuous mode enabled
Oct 4 02:34:44 bandwidthd: Packet Encoding: Ethernet
Oct 4 02:34:44 bandwidthd: Opening em0
Oct 4 02:34:44 bandwidthd: Packet Encoding: Ethernet
Oct 4 02:34:44 bandwidthd: Packet Encoding: Ethernet
Oct 4 02:34:44 bandwidthd: Packet Encoding: Ethernet
Oct 4 02:35:32 kernel: em0: promiscuous mode disabled
Oct 4 02:35:34 bandwidthd: Monitoring subnet 192.168.1.0 with netmask 192.168.1.0
Oct 4 02:35:34 bandwidthd: Monitoring subnet 192.168.1.0 with netmask 192.168.1.0
Oct 4 02:35:34 bandwidthd: Opening em0
Oct 4 02:35:34 bandwidthd: Opening em0
Oct 4 02:35:34 bandwidthd: Opening em0
Oct 4 02:35:34 bandwidthd: Opening em0
Oct 4 02:35:34 bandwidthd: Packet Encoding: Ethernet
Oct 4 02:35:34 kernel: em0: promiscuous mode enabled
Oct 4 02:35:34 bandwidthd: Packet Encoding: Ethernet
Oct 4 02:35:34 bandwidthd: Packet Encoding: Ethernet
Oct 4 02:35:34 bandwidthd: Packet Encoding: Ethernet
 
I just realized it was disabling promiscuous mode, does it need that enabled?
 
"Oct 4 02:34:44 bandwidthd: Monitoring subnet 192.168.1.0 with netmask 192.168.1.0"

Shouldn`t the netmask be 255.255.255.0 (assuming you`re using a 24 bit mask)?
 
"Oct 4 02:34:44 bandwidthd: Monitoring subnet 192.168.1.0 with netmask 192.168.1.0"

Shouldn`t the netmask be 255.255.255.0 (assuming you`re using a 24 bit mask)?

it does that by itself you input 192.168.1.0/24
 
*unrelated*

Anyone notice that when you browse your network that under "Network Infrastructure" a FreeBSD router is listed.

Nifty.
 
Back
Top