[Bug 918654] New: ndpmon stops silently to work
http://bugzilla.opensuse.org/show_bug.cgi?id=918654 Bug ID: 918654 Summary: ndpmon stops silently to work Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: tschaefer@t-online.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Using the following paket: rpm -qi ndpmon Name : ndpmon Version : 1.4.0 Release : 8.1 Architecture: x86_64 Install Date: Do 11 Dez 2014 11:11:33 CET Group : Productivity/Networking/Diagnostic Size : 1304023 License : LGPL-2.1+ Signature : DSA/SHA1, Mi 15 Okt 2014 17:26:58 CEST, Key ID ff9db4771bce05ef Source RPM : ndpmon-1.4.0-8.1.src.rpm Build Date : Mi 15 Okt 2014 17:26:32 CEST Build Host : cloud118 Relocations : (not relocatable) Vendor : obs://build.opensuse.org/home:gregfreemyer:Tools-for-forensic-boot-cd URL : http://ndpmon.sourceforge.net/ Summary : IPv6 Neighbor Discovery Protocol Monitor Description : NDPMon, Neighbor Discovery Protocol Monitor, is a tool working with ICMPv6 packets. NDPMon observes the local network to see if nodes using neighbor discovery messages behave properly. When it detects a suspicious Neighbor Discovery message, it notifies the administrator by writing in the syslog and in some cases by sending an email report. Distribution: home:gregfreemyer:Tools-for-forensic-boot-cd / openSUSE_13.2 ndpmon starts and is running for a while: systemctl status ndpmon.service ndpmon.service - LSB: IPv6 Neighbor Discovery Protocol Monitor Loaded: loaded (/etc/init.d/ndpmon) Active: active (running) since Do 2015-02-19 15:58:57 CET; 44s ago Process: 19017 ExecStop=/etc/init.d/ndpmon stop (code=exited, status=0/SUCCESS) Process: 19028 ExecStart=/etc/init.d/ndpmon start (code=exited, status=0/SUCCESS) CGroup: /system.slice/ndpmon.service └─19035 /usr/sbin/ndpmon Feb 19 15:59:32 pflaume ndpmon[19028]: ------------------ Feb 19 15:59:32 pflaume ndpmon[19028]: ----- ND_NEIGHBOR_ADVERT ----- Feb 19 15:59:32 pflaume ndpmon[19028]: Reset timer for 0:19:99:f3:0:42 fe80:0:0:0:219:99ff:fef3:42 Feb 19 15:59:32 pflaume ndpmon[19028]: ------------------ Feb 19 15:59:33 pflaume ndpmon[19028]: ----- ND_NEIGHBOR_SOLICIT ----- Feb 19 15:59:33 pflaume ndpmon[19028]: Reset timer for b4:b5:2f:f3:b5:ac fe80:0:0:0:b6b5:2fff:fef3:b5ac Feb 19 15:59:33 pflaume ndpmon[19028]: ------------------ Feb 19 15:59:33 pflaume ndpmon[19028]: ----- ND_NEIGHBOR_ADVERT ----- Feb 19 15:59:33 pflaume ndpmon[19028]: Reset timer for 0:19:99:f3:0:42 fe80:0:0:0:219:99ff:fef3:42 Feb 19 15:59:33 pflaume ndpmon[19028]: ------------------ But after some time/days: there are no mails and the state is: systemctl status ndpmon.service ndpmon.service - LSB: IPv6 Neighbor Discovery Protocol Monitor Loaded: loaded (/etc/init.d/ndpmon) Active: active (running) since Mo 2015-02-09 16:22:46 CET; 1 weeks 2 days ago Process: 762 ExecStart=/etc/init.d/ndpmon start (code=exited, status=0/SUCCESS) CGroup: /system.slice/ndpmon.service └─809 /usr/sbin/ndpmon Feb 19 15:58:31 pflaume ndpmon[762]: Ethernet type 0 is not an IPv6 packet Feb 19 15:58:31 pflaume ndpmon[762]: ------------------ Feb 19 15:58:31 pflaume ndpmon[762]: Ethernet type 0 is not an IPv6 packet Feb 19 15:58:31 pflaume ndpmon[762]: ------------------ Feb 19 15:58:32 pflaume ndpmon[762]: Ethernet type 0 is not an IPv6 packet Feb 19 15:58:32 pflaume ndpmon[762]: ------------------ Feb 19 15:58:32 pflaume ndpmon[762]: Ethernet type 0 is not an IPv6 packet Feb 19 15:58:32 pflaume ndpmon[762]: ------------------ Feb 19 15:58:44 pflaume ndpmon[762]: Ethernet type 0 is not an IPv6 packet Feb 19 15:58:44 pflaume ndpmon[762]: ------------------ I don't know, what is going wrong here. I have seen that there is a complete new version at http://ndpmon.sourceforge.net/ Or can somebody recommend alternatives? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=918654 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwiedemann@suse.com, | |Greg.Freemyer@gmail.com Assignee|bnc-team-screening@forge.pr |jfunk@funktronics.ca |ovo.novell.com | --- Comment #1 from Bernhard Wiedemann <bwiedemann@suse.com> --- There is also a version maintained in https://build.opensuse.org/package/show/security/ndpmon which should be preferred to home projects but it is also 2 years old and not part of Factory. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=918654 --- Comment #2 from Greg Freemyer <Greg.Freemyer@gmail.com> --- I would at least try upgrading to the latest upstream version. I only have a version in my home project because I fixed the 12.2 build and did not delete it after the fact. But my version and the one in security should be identical. Do I need to do a test version bump in my home project? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=918654 James Oakley <jfunk@funktronics.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #3 from James Oakley <jfunk@funktronics.ca> --- I created an updated package and sent a submit request: https://build.opensuse.org/request/show/287183 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=918654 --- Comment #6 from Thomas Schäfer <tschaefer@t-online.de> --- Thank you very much for providing the packet. Sorry for the delay. It works at the moment. Of course the old xml configuration files were not accepted. Two things are wrong: /etc/ndpmon/config_ndpmon.xml exec_pipe_program="/usr/ndpmon/alerts_to_xml.py" should be exec_pipe_program="/usr/lib/ndpmon/alerts_to_xml.py" There is also an xml violation <route> <address>2001:db8:abcd:ef01::</address> <mask>64</mask> <param_pref_reserved>8</param_flags_reserved> <lifetime>2592000</lifetime> </route> Also the generated emails are not unique. Some of write the header in different order, that sometimes User-Agent: Heirloom mailx 12.5 7/5/10 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit appeared within the mail body, sometimes it doesn't. But this was also a problem with version 1.4. At the moment I can nothing say about stability or behaviour after reboots. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=918654 --- Comment #7 from James Oakley <jfunk@funktronics.ca> --- I submitted a new package with the config fixes. The email issue should be reported upstream. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=918654 --- Comment #8 from Thomas Schäfer <tschaefer@t-online.de> --- (In reply to James Oakley from comment #7)
The email issue should be reported upstream.
I wrote an email with examples to the contact-address of the project. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=918654 http://bugzilla.opensuse.org/show_bug.cgi?id=918654#c9 Karl Cheng <qantas94heavy@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED CC| |qantas94heavy@gmail.com Component|Network |3rd party software Version|13.2 |unspecified Resolution|--- |FIXED Product|openSUSE Distribution |openSUSE.org QA Contact|qa-bugs@suse.de |opensuse-communityscreening | |@forge.provo.novell.com --- Comment #9 from Karl Cheng <qantas94heavy@gmail.com> --- Package update has been accepted: https://build.opensuse.org/request/show/290362 -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com