Bug 268022

*** Bug 276109 has been marked as a duplicate of this bug. ***

*** Bug 277001 has been marked as a duplicate of this bug. ***

*** Bug 286694 has been marked as a duplicate of this bug. ***

Reassign Network Management bugs to new maintainer.  Have a lot of fun, Lamarque!

*** Bug 316537 has been marked as a duplicate of this bug. ***

I'm not sure this is even possible... let's see

I already tried to implement this. I had found a way do make it work with NetworkManager 0.8, just had not implemented it by that time. The same way does not work with NM 0.9.x, so I have postponed this until I could find a way do make it work. Since the traffic plotter just need the interface name used in plasmaengineexplorer as long as NetworkManager can provide the interface name used by the vpn connection we can make the traffic plotter work. The other info (ip address, gateway, etc) is not tha simple to find without NetworkManager support.

It should not be a problem, but I'm not sure whether it makes sense to display the traffic monitor for VPN connections, because it will show the same info as the active connection which was for activation.

(In reply to comment #8)
> It should not be a problem, but I'm not sure whether it makes sense to
> display the traffic monitor for VPN connections, because it will show the
> same info as the active connection which was for activation.

That is true if vpn is the default gateway (all traffic passing through it). You can also use vpn  to access just your company's network and the remaining traffic goes to the "active connection", then the traffic plots will be different.

That's not actually true, because traffic monitor displays traffic for devices and not for connections.

vpn connections create virtual devices (e.g. tun0), remember? They can be monitored like any other physical device (eth0, wlan0, etc). If we can get the virtual device for the vpn connection we can pass it to Plasma's systemmonitor engine and it will provide the download and upload rates needed to plot a graph.

Ah, I didn't know that and I've never seen any tun device in NM and now I just opened qdbusviewer and see there is a tun device, but this device is new in NM 0.9.9.0 (at least managed by NM and visible on dbus). Ok, I'll add support for traffic monitor in plasma-nm for VPN connections.

When you activate some VPN connection, NM creates a new tun device, but it's not associated with any active connection and if you check the new tun device and try to get its active connections, it shows you an empty path. I thought that the new VPN connection will have some tun device in devices property, but there is only device which was used for activation. Question is, how to get the right tun device for active VPN connection? So far we can only guess that the newly created tun device is for the newly activated connection. Any ideas?

Maybe we can use the org.freedesktop.NetworkManager.VPN.Plugin.Config signal to get that value. The problem is only root is allowed to connect to org.freedesktop.NetworkManager.VPN.Plugin interface, so we need some support in NetworkManager to send that kind of information to Plasma NM.

Is there any progress in implementing the output of details and/or traffic monitoring VPN connections?

Sorry, but I have not had the time to implement this. I guess neither do other Plasma NM developers.

In the new version of NetworkManager when you activate a vpn connection NM automatically creates and activates a tun connection which now can be monitored for traffic. It works automatically without any extra work.

Sorry, may fault. We shouldn't display created tun0/vpn0 connections which are automatically created by NetworkManager and until NetworkManager 1.2.0 there is no way how to pair an activated VPN connection with a tun device, but after discussion with NM developers I had recently this possibility will be added.

Should be possible after https://bugzilla.gnome.org/show_bug.cgi?id=743309 is solved.

(In reply to Jan Grulich from comment #19)
> Should be possible after https://bugzilla.gnome.org/show_bug.cgi?id=743309
> is solved.

Looks like it was never solved before GNOME closed their Bugzilla.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.

Hi,

behaviour is now different (plasma-nm 5.18.5-1) for VPN connections. There is no details and traffic window anymore. 

In my PoV at least connection details should be available for VPN connections and as far as I know it is easy to obtain them from the system.

If VPN traffic info is not easily available to be shown, I think it is better not to have a traffic window at all than have a traffic window with no information (as it is now).

So sumarily, I think that at least connection details (IPs, gatways, etc) should be shown in nm-applet for VPN connections, same way they are shown for a LAN or WLAN connections.

Thanks for confirming, I think this certainly should be looked at, either disable the graph or provide the info like other connections.

Created attachment 133523 [details]
For LAN or WLAN details are available

For LAN or WLAN details are available

Created attachment 133524 [details]
For VPN no details are available

For VPN no details are available. It would be useful if they would be available.