• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Bandwidthd reports syntax error at boot time

Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
4 Posts 3 Posters 3.1k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • W
    wallabybob
    last edited by Mar 10, 2011, 9:51 PM

    At boot time:

    clog /var/log/system.log | grep -i bandwidthd

    Mar 10 17:10:07 pfsense bandwidthd: Monitoring subnet 192.168.211.128 with netmask 192.168.211.128
    Mar 10 17:10:07 pfsense bandwidthd: Syntax Error "syntax error" on line 17
    Mar 10 17:10:07 pfsense bandwidthd: Syntax Error "syntax error" on line 17
    Mar 10 17:10:15 pfsense bandwidthd: Monitoring subnet 192.168.211.128 with netmask 192.168.211.128
    Mar 10 17:10:15 pfsense bandwidthd: Syntax Error "syntax error" on line 17
    Mar 10 17:10:15 pfsense bandwidthd: Syntax Error "syntax error" on line 17

    I presume its complaining about something in the file:

    more /usr/local/bandwidthd/etc/bandwidthd.conf

    This file was automatically generated by the pfSense

    package management system.  Changing this file

    will lead to it being overwritten again when

    the package manage resyncs.

    ####################################################

    Bandwidthd.conf

    Commented out options are here to provide

    documentation and represent defaults

    Subnets to collect statistics on.  Traffic that

    matches none of these subnets will be ignored.

    Syntax is either IP Subnet Mask or CIDR

    subnet 192.168.211.128/25
    subnet

    Device to listen on

    Bandwidthd listens on the first device it detects

    by default.  Run "bandwidthd -l" for a list of

    devices.

    dev "bridge0"

    ###################################################

    Options that don't usually get changed

    An interval is 2.5 minutes, this is how many

    intervals to skip before doing a graphing run

    Graph cutoff is how many k must be transfered by an

    ip before we bother to graph it

    #Put interface in promiscuous mode to score to traffic
    #that may not be routing through the host machine.

    #Log data to cdf file htdocs/log.cdf

    #Read back the cdf file on startup

    #Libpcap format filter string used to control what bandwidthd sees
    #Please always include "ip" in the string to avoid strange problems

    #Draw Graphs - This default to true to graph the traffic bandwidthd is recording
    #Usually set this to false if you only want cdf output or
    #you are using the database output option.  Bandwidthd will use very little
    #ram and cpu if this is set to false.

    #Set META REFRESH seconds (default 150, use 0 to disable).

    and by my counting line 17 is the third line of

    Syntax is either IP Subnet Mask or CIDR

    subnet 192.168.211.128/25
    subnet

    This system has been upgraded from 1.2.3 to a 2.0 snapshot build and then multiple times from snapshot builds. I have no idea when this started happening.

    1 Reply Last reply Reply Quote 0
    • J
      jimp Rebel Alliance Developer Netgate
      last edited by Mar 14, 2011, 3:03 PM

      The bandwidthd package was updated last week to handle multiple subnets. It's possible there is a bug in the code that is causing this to happen.

      Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

      Need help fast? Netgate Global Support!

      Do not Chat/PM for help!

      1 Reply Last reply Reply Quote 0
      • T
        tsk
        last edited by Mar 20, 2011, 4:23 PM

        Just get rid of the second subnet line (or comment it out) and it should boot up fine.

        1 Reply Last reply Reply Quote 0
        • W
          wallabybob
          last edited by Mar 20, 2011, 7:48 PM

          @tsk:

          Just get rid of the second subnet line (or comment it out) and it should boot up fine.

          Thanks. Doesn't seem to cause any boot problem.

          1 Reply Last reply Reply Quote 0
          1 out of 4
          • First post
            1/4
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
            This community forum collects and processes your personal information.
            consent.not_received