Bug 789303 – Network speed incorrectly reported when using VPN

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 789303 - Network speed incorrectly reported when using VPN


Summary:	Network speed incorrectly reported when using VPN


Status:	RESOLVED OBSOLETE

Product:	system-monitor
Classification:	Core
Component:	resources
Version:	unspecified
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	System-monitor maintainers
QA Contact:	System-monitor maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2017-10-21 16:37 UTC by gpothier
Modified:	2018-05-22 12:19 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description gpothier 2017-10-21 16:37:43 UTC

(description adapted from Ubuntu bug report https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1076880)

When using a VPN and monitoring up and download speeds shown in System monitor, then the indicated speeds are much greater than they apparently should be. When VPN is stopped and normal connection used, then indicated speeds are as expected.

The system monitor appears to double network throughput when using a VPN (likely because its adding the VPN interface throughput to the underlying wlan/eth interface throughput, effectively double counting it). 

Possibly related to this bug: https://bugzilla.gnome.org/show_bug.cgi?id=535544

Here is my current ifconfig:

gpothier@tadzim3:~$ ifconfig
eth3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.50.150  netmask 255.255.255.0  broadcast 192.168.50.255
        inet6 fe80::2e0:1eff:fe70:1597  prefixlen 64  scopeid 0x20<link>
        ether 00:e0:1e:70:15:97  txqueuelen 1000  (Ethernet)
        RX packets 1848753  bytes 487533528 (487.5 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3274146  bytes 4273795139 (4.2 GB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 8854673  bytes 557447086 (557.4 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8854673  bytes 557447086 (557.4 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1500
        inet 10.8.1.2  netmask 255.255.255.0  destination 10.8.1.2
        inet6 fe80::941:34b1:bbce:b20c  prefixlen 64  scopeid 0x20<link>
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 100  (UNSPEC)
        RX packets 1537752  bytes 90249558 (90.2 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3006869  bytes 3783306360 (3.7 GB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:08:e8:1e  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Comment 1 GNOME Infrastructure Team 2018-05-22 12:19:37 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-system-monitor/issues/73.