Advisory: ======================== An update to libndpi and ntopng has been pushed to Mageia 6. This fixed a crash in the previous version. References: https://bugs.mageia.org/show_bug.cgi?id=22491 Updated packages in core/updates_testing: ======================== ntopng-2.4-1..mga6 from ntopng-2.4-1.mga6.src.rpm and lib64ndpi-devel-1.8.0-1.mga6 lib64ndpi2-1.8.0-1.mga6 from libndpi-1.8.0-1.mga6.src.rpm
Mageia 6 :: x86_64 This is a network monitoring tool which depends on a redis server. Installed redis and started it as a service. As root: # ntopng Resulted in a stack dump and eventual "Aborted (core dumped)" Update the ntopng packages, which pulled in a newer version of redis. Restarted the redis server and as root (uses port 6379): # ntopng 05/Feb/2018 09:06:59 [Ntop.cpp:1121] Setting local networks to 127.0.0.0/8 05/Feb/2018 09:06:59 [Redis.cpp:92] Successfully connected to redis 127.0.0.1:6379@0 05/Feb/2018 09:06:59 [PcapInterface.cpp:85] Reading packets from interface enp3s0... 05/Feb/2018 09:06:59 [Ntop.cpp:1267] Registered interface enp3s0 [id: 0] ................................ It looks perfectly stable. Using the help command to list the available interfaces: # ntopng -h < general help information> Available interfaces (-i <interface index>): 1. enp3s0 2. any 3. lo 4. wlp6s0 5. bluetooth0 6. bluetooth-monitor 7. nflog 8. nfqueue 9. usbmon1 10. usbmon2 11. usbmon3 12. usbmon4 The ntopng command by itself is equivalent to # ntopng -i 1 That is as far as I can take it with my limited knowledge of networking.
CC: (none) => tarazed25Whiteboard: (none) => MGA6-64-OK
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
Keywords: (none) => advisoryCC: (none) => davidwhodgins
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2018-0027.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
MGA9-64 Plasma Wayland on HP-Pavillion No installation issues. $ ndptool -h ndptool [options] command -h --help Show this help -v --verbose Increase output verbosity -t --msg-type=TYPE Specify message type ("rs", "ra", "ns", "na") -D --dest=DEST Dest address in IPv6 header for NS or NA -T --target=TARGET Target address in ICMPv6 header for NS or NA -i --ifname=IFNAME Specify interface name -U --unsolicited Send Unsolicited NA Available commands: monitor send Thatlooks like this tool works on IPV6, but I've never configured my network on IPV6, but I guess some default might be OK??? [tester9@mach4 Documents]$ ndptool -i wlp0s20u2 monitor libndp: ndp_sock_open: Failed to create ICMP6 socket. Failed to open ndp: Operation not permitted So, I guess this need root access # ndptool -i wlp0s20u2 monitor after some minute, I get feedback NDP payload len 104, from addr: fe80::3631:c4ff:fe80:a9b4, iface: wlp0s20u2 Type: RA Hop limit: 255 Managed address configuration: no Other configuration: yes Default router preference: medium Router lifetime: 0s Reachable time: unspecified Retransmit time: unspecified Source linkaddr: 34:31:c4:80:a9:b4 Prefix: fd00::/64, valid_time: 7200s, preferred_time: 3600s, on_link: yes, autonomous_addr_conf: yes, router_addr: no MTU: 1500 Route: fd00::/64, lifetime: 1800s, preference: medium Recursive DNS Servers: fd00::3631:c4ff:fe80:a9b4, lifetime: 1200s NDP payload len 32, from addr: fd00::3631:c4ff:fe80:a9b4, iface: wlp0s20u2 Type: NA NDP payload len 32, from addr: fe80::3631:c4ff:fe80:a9b4, iface: wlp0s20u2 Type: NS NDP payload len 24, from addr: fe80::3631:c4ff:fe80:a9b4, iface: wlp0s20u2 Type: NA NDP payload len 32, from addr: fe80::3631:c4ff:fe80:a9b4, iface: wlp0s20u2 Type: NS NDP payload len 104, from addr: fe80::3631:c4ff:fe80:a9b4, iface: wlp0s20u2 Type: RA Hop limit: 255 Managed address configuration: no Other configuration: yes Default router preference: medium Router lifetime: 0s Reachable time: unspecified Retransmit time: unspecified Source linkaddr: 34:31:c4:80:a9:b4 Prefix: fd00::/64, valid_time: 7200s, preferred_time: 3600s, on_link: yes, autonomous_addr_conf: yes, router_addr: no MTU: 1500 Route: fd00::/64, lifetime: 1800s, preference: medium Recursive DNS Servers: fd00::3631:c4ff:fe80:a9b4, lifetime: 1200s I can ping that DNS-server address, so that is no nonsense Seems OK to me
CC: (none) => herman.viaene
Sorry, that comment 3 is misplaced here, is for bug 33304.