Thanks for reporting this. It is *not* a duplicate of bug 25417, which you helped with.

net_monitor maintained by no-one in particular, so assigning this globally.
However, JoséJ recently updated it, so CC'ing him.
vnstat seems to be in the hands of DavidG, CC'ing.

CC: (none) => geiger.david68210, lists.jjorge
Assignee: bugsquad => pkg-bugs

Yes, I have added tcp6 and udp6 connections. I also see the IPv6 DNS server of my system.
As for IPv6 address and route, I think I won't have time to add them, but who knows?

Hi José,
Thank you for your contribution.
I have disabled IPv6 on my Mageia 7.
I get:
net_monitor -i wlp2s0  
Traceback (most recent call last):
  File "/usr/lib64/python3.7/site-packages/net_monitor/monitor.py", line 335, in get_connections
    with open("/proc/net/%s" % proto) as fd:
FileNotFoundError: [Errno 2] Aucun fichier ou dossier de ce type: '/proc/net/tcp6'
Traceback (most recent call last):
  File "/usr/lib64/python3.7/site-packages/net_monitor/monitor.py", line 335, in get_connections
    with open("/proc/net/%s" % proto) as fd:
FileNotFoundError: [Errno 2] Aucun fichier ou dossier de ce type: '/proc/net/udp6'

CC: (none) => yves.brungard_mageia

But the program starts and continue to display the graphic.

(In reply to papoteur from comment #4)
> But the program starts and continue to display the graphic.

Yes, it should test if the file exists, maybe I can learn a little more python to do that ;-)

(In reply to José Jorge from comment #5)
> (In reply to papoteur from comment #4)
> > But the program starts and continue to display the graphic.
> 
> Yes, it should test if the file exists, maybe I can learn a little more
> python to do that ;-)

I can have a look

This is done now, with other cosmetics things.
Traffic enabled is also now detected with new vnstat.
See release 0.28
@José
Can you push it in cauldron then Mageia 7?

(In reply to papoteur from comment #7)
> @José
> Can you push it in cauldron then Mageia 7?

Done for cauldron and MGA7. I let you assign  to QA.

Assigning to QA

net_monitor-0.28-1.mga7

This new release adds monitoring of IPv6 connections.
It fixes also some other things:
- the with of the rate and volume is less variable, thus less window resizing occurs
- the name of ESSID of wireless connection doesn't start with b'
- traffic statistic enabling is detected and a button to acces it it displayed.
- traffic statistic display check the real radio button in relation to the graphic displayed.

Assignee: pkg-bugs => qa-bugs

(In reply to papoteur from comment #9)
> Assigning to QA
> 
> net_monitor-0.28-1.mga7
> 
> This new release adds monitoring of IPv6 connections.
> It fixes also some other things:
> - the with of the rate and volume is less variable, thus less window
> resizing occurs
> - the name of ESSID of wireless connection doesn't start with b'
> - traffic statistic enabling is detected and a button to acces it it
> displayed.
> - traffic statistic display check the real radio button in relation to the
> graphic displayed.

Thank you!!!!!

With the latest versions of software, I don't see any ipv6 info on main screen.

More importantly, I cannot get accounting to work for a second nic.

E.G.:  I installed cauldron on an old system, It had a 100Mb nic and a wifi. I disabled the nic, used the wifi to install from net.
Accounting works for the wifi.

Changed graphics card and added 1Gb nic.

I had accounting for the wifi, not the nic.
Removed the wfi completely, still no accounting for the nic.

Verified this on a vm, by adding a second nic. disabled the first nic, no accounting available for the second one.

Accounting is "turned on" in the ifcfg for the nic.
It shows up in net monitor, just no accounting.

(In reply to james Whitby from comment #11)
> With the latest versions of software, I don't see any ipv6 info on main
> screen.

Yes, there is still no IPv6 address. Only the DNS servers appear, if you have IPv6 ones.

> 
> More importantly, I cannot get accounting to work for a second nic.
> 

Did you reboot the system? What gives the 'vnstat' cli?

(In reply to José Jorge from comment #12)
> (In reply to james Whitby from comment #11)
> > With the latest versions of software, I don't see any ipv6 info on main
> > screen.
> 
> Yes, there is still no IPv6 address. Only the DNS servers appear, if you
> have IPv6 ones.
> 
> > 
> > More importantly, I cannot get accounting to work for a second nic.
> > 
> 
> Did you reboot the system? What gives the 'vnstat' cli?

Yes, it has been rebooted several times. 
Vnstat shows nothing for the second nic (enp0s8). 

In network manager:
disconnect 1st nic ( enp0s3 ).
connect 2nd nic ( enp0s8 ).
Reboot.
vnstat shows enp0s3 only, enp0s8 is active.

(In reply to james Whitby from comment #13)
> (In reply to José Jorge from comment #12)
> > (In reply to james Whitby from comment #11)
> > > With the latest versions of software, I don't see any ipv6 info on main
> > > screen.
> > 
> > Yes, there is still no IPv6 address. Only the DNS servers appear, if you
> > have IPv6 ones.
> > 
> > > 
> > > More importantly, I cannot get accounting to work for a second nic.
> > > 
> > 
> > Did you reboot the system? What gives the 'vnstat' cli?
> 
> Yes, it has been rebooted several times. 
> Vnstat shows nothing for the second nic (enp0s8). 
> 
> In network manager:
> disconnect 1st nic ( enp0s3 ).
> connect 2nd nic ( enp0s8 ).
> Reboot.
> vnstat shows enp0s3 only, enp0s8 is active.

So this is another bug, let's not pollute this bug report with it. You can look inside /etc/vnstat.conf first lines, they are commented.

(In reply to José Jorge from comment #14)
<snip>

 (In reply to james Whitby from comment #13)
> > (In reply to José Jorge from comment #12)
>\> 
> So this is another bug, let's not pollute this bug report with it. You can
> look inside /etc/vnstat.conf first lines, they are commented.

Thanks, will do.

Tested with my 64 bits family system. IPv6 connections are shown now.

Whiteboard: (none) => MGA7-64-OK

Validating. Advisory information in Comment 9.

Keywords: (none) => validated_update
CC: (none) => andrewsfarm, sysadmin-bugs

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2020-0154.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED