[prev in list] [next in list] [prev in thread] [next in thread] 

List:       net-snmp-bugs
Subject:    [ net-snmp-Bugs-1620424 ] snmptrap send traps on port 161
From:       "SourceForge.net" <noreply () sourceforge ! net>
Date:       2006-12-21 22:22:38
Message-ID: E1GxWJC-00026Z-MJ () sc8-sf-web9 ! sourceforge ! net
[Download RAW message or body]

Bugs item #1620424, was opened at 2006-12-21 22:25
Message generated for change (Comment added) made by magfr
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=112694&aid=1620424&group_id=12694

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: magfr (magfr)
Assigned to: Nobody/Anonymous (nobody)
Summary: snmptrap send traps on port 161

Initial Comment:
snmptrap from net-snmp 5.4 and 5.5.dev defaults to sending traps on port 161.

Example:

% snmptrap -d -v2c -c public localhost 1024 1.2.3.4

Sending 64 bytes to UDP: [127.0.0.1]:161
...


----------------------------------------------------------------------

>Comment By: magfr (magfr)
Date: 2006-12-21 23:22

Message:
Logged In: YES 
user_id=1124910
Originator: YES

The problem with patch a is that snmptrap -d -v2c -c public
--defTarget='snmptrap udp :55555' localhost 1024 1.2.3.4 still sends on
port 162 and not on 55555 as expected.

This is due to problem a) and the following patch solves it but is not in
and by itself enough to solve the original problem - both patches are
needed for that!
File Added: b

----------------------------------------------------------------------

Comment By: magfr (magfr)
Date: 2006-12-21 22:46

Message:
Logged In: YES 
user_id=1124910
Originator: YES

This patch is enough to solve the symptom and problem b) but problem a)
still remains.
File Added: a

----------------------------------------------------------------------

Comment By: magfr (magfr)
Date: 2006-12-21 22:36

Message:
Logged In: YES 
user_id=1124910
Originator: YES

The problems here is that
a) snmp_open assumes that the transport domain should be "snmp" while
"snmptrap"
   is correct for trap sending
b) NETSNMP_DS_LIB_DEFAULT_PORT is given lower priority than the result
from the
   domain lookup


----------------------------------------------------------------------

Comment By: magfr (magfr)
Date: 2006-12-21 22:26

Message:
Logged In: YES 
user_id=1124910
Originator: YES

This bug report is originally from G. S. Marzot.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=112694&aid=1620424&group_id=12694

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Net-snmp-bugs mailing list
Net-snmp-bugs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-bugs
[prev in list] [next in list] [prev in thread] [next in thread]