Bug 874092 - Can't use shinken-discovery for discovery our network
Summary: Can't use shinken-discovery for discovery our network
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: shinken
Version: el6
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: David Hannequin
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-07 13:22 UTC by Sébastien Andreatta
Modified: 2013-01-20 19:03 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-20 19:03:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Patch to use shinken-discovery (525 bytes, application/octet-stream)
2012-11-07 13:22 UTC, Sébastien Andreatta
no flags Details

Description Sébastien Andreatta 2012-11-07 13:22:25 UTC
Created attachment 640061 [details]
Patch to use shinken-discovery

Description of problem:

Can't use discovery script for shinken because nmap doesn't support idle or connect scan.

Version-Release number of selected component (if applicable):

nmap-5.51-2.el6.x86_64
shinken-1.0.1-5.el6.noarch

How reproducible:

Always

Steps to Reproduce:
1. Install shinken ( yum install shinken shinken-{arbiter,broker,poller,reactionner,receiver,scheduler} )
2. Launch discover script ( shinken-discovery -o /etc/shinken/objects/discovery -r nmap ) with root 
  
Actual results:

Doesn't work , exit on error

Launching command, sudo nmap localhost www.google.fr -sU -sT -T4 -O --traceroute  -oX /tmp/tmp_aSCuz
Try to communicate
Error : the nmap return an error : 'Traceroute does not support idle or connect scan
QUITTING!


Expected results:

Generate the config file into /etc/shnken/objects/discovery 

Additional info:

nmap is call'd in /usr/lib/shinken/plugins/nmap_discovery_runner.py

     cmd = "sudo nmap %s -sU -sT -T4 -O --traceroute -oX %s" % (' '.join(targets) , tmppath)

I have made a patch ( see attachment )

Comment 1 David Hannequin 2013-01-20 19:03:09 UTC
Hi,

Thank for patch. This bug is fix on version 1.2.2.

Best regard


Note You need to log in before you can comment on or make changes to this bug.