Project

General

Profile

Actions
Copy link

Bug #682

closed

WAN traffic graph is broken with MLPPP

Added by Jim Pingle almost 14 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Very Low
Assignee:
-
Category:
PPP Interfaces
Target version:
-
Start date:
06/21/2010
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

From http://forum.pfsense.org/index.php/topic,26126.0.html

clarknova wrote:

I was testing the mlppp package before it was integrated into the 2.0 base, and the WAN traffic graph worked, although it reported double out traffic.

I've since used the June 10 and June 19 builds with integrated mlppp and the WAN graph never shows more than 5kbps, although real traffic is anywhere up to 10mbps.

Files

Screenshot.png (35.1 KB) Screenshot.png David Burgess, 06/27/2010 11:04 PM
Actions
Copy link
 #1

Updated by David Burgess almost 14 years ago

Issue semi-fixed by deleting then recreating mlppp interface. Legacy xml from testing phase was causing this problem, according to the mlppp contributor.

WAN traffic graph now appears accurate for incoming, but outgoing is incorrect: appears to report double throughput (on a 2-link mlppp connection). See forum link for more info.

http://forum.pfsense.org/index.php/topic,26126.msg136258.html#msg136258

Actions
Copy link
 #2

Updated by David Burgess almost 14 years ago

I enabled the WAN/mlppp parent interfaces for the purpose of interacting with the modems, and noticed that the parent interfaces are reporting traffic (see attached). Each parent interface ("MODEM1" and "MODEM2") reports slightly more than half of what the WAN is reporting for incoming, i.e., MODEM1 and MODEM2 each report roughly 5.35 mbps on a full-speed download, while the WAN reports 10.45 mbps. This corresponds well with what speedtest.net and my bittorrent client are reporting.

Outgoing, on the other hand, each parent interface appears to be reporting closer to about 1/2 of what speedtest.net is reporting (which sounds right) and 1/4 of what the WAN is reporting.

Actions
Copy link
 #3

Updated by David Burgess over 13 years ago

I recently upgraded from 2-line mlppp to 4-line mlppp and the WAN:outgoing graph is still reading double. I partly expected it to show quadruple, but I'm not smart that way.

Actions
Copy link
 #4

Updated by Ermal Luçi over 13 years ago

  • Status changed from New to Feedback
Actions
Copy link
 #5

Updated by David Burgess over 13 years ago

Same issue exists for me in November 20 snapshot, all the way up to 8 lines.

Actions
Copy link
 #6

Updated by Chris Buechler over 13 years ago

  • Status changed from Feedback to New
  • Priority changed from Normal to Very Low
  • Affected Version set to 2.0
Actions
Copy link
 #7

Updated by Chris Buechler over 13 years ago

  • Target version deleted (2.0)
Actions
Copy link
 #8

Updated by Jim Thompson about 8 years ago

  • Assignee set to Jim Pingle
Actions
Copy link
 #9

Updated by Jim Pingle about 8 years ago

  • Status changed from New to Feedback
  • Assignee deleted (Jim Pingle)

I don't have a means to test this one, no access to an MLPPP setup. Tried to rig one up in mpd a few different ways but didn't land on a working config. It worked partially and I did see traffic on the graphs (Both RRD and Status > Traffic Graphs) but given the various ways the test setup was broken I couldn't accurately determine if the speed was properly represented. Looking at the underlying interface stats in netstat it appears to be correct as far as I can see.

If someone with access to a Multi-Link PPP setup can test on pfSense 2.3 and provide feedback it would help move this along.

Actions
Copy link
 #10

Updated by Jim Pingle over 6 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom PDF