Local traffic have not local color in gnome-panel gnome-system-monitor applet

[BAleks]

Binary package hint: gnome-system-monitor

I have more local network computers than in my physical ip network range (before the gateway)

Would be nice to find a way to define ip ranges that are considered to be local or not
Becouse local traffic in this ranges is free, but other costs money.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gnome-system-monitor 2.28.0-1ubuntu2 [modified: usr/bin/gnome-system-monitor]
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
CheckboxSubmission: 78247b9a5c4cd5d4aa828dae7992c684
CheckboxSystem: c69722ecac764861be52925fa50b4dcc
Date: Thu May 13 17:17:25 2010
ProcEnviron:
 LANGUAGE=ru_RU:ru:en_GB:en
 PATH=(custom, user)
 LANG=ru_RU.utf8
 SHELL=/bin/bash
SourcePackage: gnome-system-monitor

[Pedro Villavicencio (pedro)]

you can define that color in the preferences, why having a separate one for those?

[BAleks (bukhalenkov-a)]

Pedro, question is about the meaning of "local traffic"
Color setting in preferences is ok, but need another setting defining what should be considered as LOCAL traffic.

[Pedro Villavicencio (pedro)]

This bug is an upstream one and it would be quite helpful if somebody experiencing it could send the bug the to the people writing the software. You can learn more about how to do this for various upstreams at https://wiki.ubuntu.com/Bugs/Upstream/GNOME . Thanks in advance!

[Pedro Villavicencio (pedro)]

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
 https://bugzilla.gnome.org/show_bug.cgi?id=626847

[Robert Roth (evfool)]

Thank you for reporting this bug to Ubuntu. Ubuntu 10.04 reached EOL on May 9, 2013.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

I've tried recreating this bug with your release and was unable to, given the information you've provided. Please upgrade to the latest version and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again.

Do feel free to report any other bugs you may find.