On Mon, Apr 16, 2007 at 02:05:53PM -0400, Jayson Robinson wrote:
> Hey all,
>
> I was trying to run an snmptrap on a newly compiled 5.4 agent and couldn't
> get anything on the trap receiver side. I found that it appears to default
> to port :161 for snmptrap traffic as well instead of :162. Is this a design
> change? I also found that if I specified the port as :162 everything worked
> as expected.
>
> -dAll output shows the following when grepping for 161.
>
> defaults: netsnmp_lookup_default_target("snmp", "udp") -> ":161"
> tdomain: domain "udp" address "ino0s295.svr.bankone.net" default address
> ":161"
> netsnmp_sockaddr_in: addr 2ff224c0, inpeername "ino0s295.svr.bankone.net",
> default_target ":161"
> netsnmp_sockaddr_in: addr 2ff224c0, inpeername ":161", default_target
> "[NIL]"
> netsnmp_sockaddr_in: check user service 161
> netsnmp_sockaddr_in: return { AF_INET, 0.0.0.0:161 }
> netsnmp_sockaddr_in: return { AF_INET, 155.180.224.66:161 }
> netsnmp_udp: open remote UDP: [155.180.224.66]:161:161
> netsnmp_udp: send 141 bytes from 200afe3b to UDP: [155.180.224.66]:161 on fd
> 3
>
>
> Any ideas? Is this a bug or was there a design change?
This is a bug. In fact it is patch #1620424 in the net-snmp tracker.
There is a patch as well.
If the patch won't fix your problem or doesn't apply then please tell so I can
update it.
/MF
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
