[Bug 254384] net/vnstat: occasionally does not log traffic & regularly gets the MaxBandwidth wrong

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Thu Mar 18 16:34:18 UTC 2021


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254384

            Bug ID: 254384
           Summary: net/vnstat: occasionally does not log traffic &
                    regularly gets the MaxBandwidth wrong
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: sunpoet at FreeBSD.org
          Reporter: walter.von.entferndt at posteo.net
             Flags: maintainer-feedback?(sunpoet at FreeBSD.org)
          Assignee: sunpoet at FreeBSD.org

For a long time, net/vnstat did work fine.  But since some days (weeks?), it
started to fail to log all traffic occasionally, and it gets the bandwidth of
my ppp(8)-tun(4) interface wrong everytime.  When I notice that it fails to log
the traffic, I have to restart it manually, until it starts to log the traffic.
 I guess this behaviour started with the last update.  I'm using packages on a
stock FreeBSD 12.2-RELEASE-p4, amd64 laptop with internet from WWAN (mobile
phone radio network) with a built-in Ericsson HSDPA+ modem.

Please note the bandwidth applied to the tun0 interface (excerpt from
/var/log/messages.log):
Mar 18 16:25:06 t450s vnstatd[98496]: Monitoring (5): wlan0 (300 Mbit) ue0
(2500 Mbit) tun0 (115200 Mbit) ipfw0 (2500 Mbit) em0 (1000 Mbit)

but in vnstat's config I set (/usr/local/etc/vnstat.conf):
BandwidthDetection 1
MaxBandwidth 2500
MaxBWem0        1000
MaxBWwlan0       300
MaxBWtun0         50

Note that 115200 baud is the default speed of the virtual serial line to the
modem; that has never hindered the modem to supply bandwidth of up to 18 Mbit/s
(usually ~1-12 Mbit/s, my ISP's max. is 20 Mbit/s).

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list