Re: [snmptrap] : source ip 0.0.0.0
On Wed, Oct 10, 2018 at 4:35 AM Pushpa Thimmaiah wrote: > Hi All, > Following is debug/trace message of tool 'snmptrap' while sending > snmpv2c traps. What does '0.0.0.0' means here? > Does the data sent to all interfaces of device (snmpagent) ? > 172.16.4.12 is trap destination. > > --- > trace: netsnmp_udpipv4base_transport(): > transports/snmpUDPIPv4BaseDomain.c, 163: > netsnmp_udpbase: client open UDP: [172.16.4.12]:162->[0.0.0.0]:56615 > > > transport:send: 89 bytes to UDP: [172.16.4.12]:162->[0.0.0.0]:56615 > > > The arrow is in the wrong direction in those debug messages. It means, you are sending from any local address, 0.0.0.0 means you don't care, port 56615, to 172.16.4.12 port 162. Bill ___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
RE: snmptrap source ip
Thank you for you detailed response. I meant traps and not informs. In any case, I rechecked it without a port (giving clientaddr only an IP and not of the form ip:port like I tried until now), and it worked both on 5.4.1 and 5.4.2. So, the problem was that I assumed that the regular structure of ip:port is permitted. Thanks again, Elad Shavit GlassHouse Technologies Ltd. -Original Message- From: Tackabury, Wayne [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 11, 2008 10:57 PM To: net-snmp-users@lists.sourceforge.net Subject: RE: snmptrap source ip Hi Elad: I hope I'm not confusing matters for you, but it sounds like you're encountering the same situation we encountered a year or so ago, where we needed to have V1 traps sent with a specific chosen interface addr of the options available on a multihomed system--reason being that only one of the addresses on the agent would properly reverse-DNS map when looked up by our management station client that was running its own trap daemon and receiving the trap. Aside from the fact you're using informs, sound like you? OK, either way, it might be worth reading my original bug report with submitted patch to 5.4.1: http://sourceforge.net/mailarchive/message.php?msg_id=E1KL19H-0003hG-Ja% 40b55xhf1.ch3.sourceforge.com There is some history here. A guy named Jan Safranek from Red Hat got me constructively motivated to actually submit this patch, but it was after he'd submitted his own, which as I recall was almost identical (certainly was functionally) to solve the same problem (my snmpd.conf param is agenttrapaddr, Jan's was something else. The discussion in this report discussed why I don't think clientaddr affects what you want to affect. Now, both Jan and I submitted our patches (Jan's came in much earlier because he's more on top of it it sounds like :), and net-snmp bug authorities were piecing out which or what kind of hybrid to use. I don't know if that was resolved for an official patch release or not. If so, use that. Either way, we've been running with this patch successfully for over a year now. Note that this *only* affects agent-initiated traps (from monitor directives in snmpd.conf). Also, I didn't test this with informs yet, but as I recall the code flow, both should be positively affected. I'll try to follow the digest better than usual if you have any followup questions here...hope this helps! Regards, Wayne Tackabury Mirror Image Internet -Original Message- -- Date: Tue, 11 Nov 2008 15:51:59 +0200 From: Elad Shavit [EMAIL PROTECTED] Subject: RE: snmptrap source ip Thank you Glenn. I have tried using the -Y clientaddr=ip:port flag but with no success. I also tried setting the clientaddr parameter in the snmp.conf file. The outcome is always the same - the outgoing port is the same (I have only one IP on my testing machine so I assume that if I could preset the port, the ip will be also set. Please mind I am working with 5.4.1 netsnmp version. Does snmptrap.exe (windows XP) suppose to be influenced from this parameter or is it only for snmpd and snmptrapd? If only for snmpd and snmptrapd, how can I set the source ip of outgoing traps if I am using the snmptrap.exe to send them? Thanks in advance, Elad Shavit GlassHouse Technologies Ltd. -Original Message- From: Glenn McAllister [mailto:[EMAIL PROTECTED] Sent: Monday, November 03, 2008 6:25 PM To: Elad Shavit Cc: net-snmp-users@lists.sourceforge.net Subject: Re: snmptrap source ip Elad Shavit wrote: Hello all, Does anyone know how can I predict/decide what will be the source ip for sending trap using snmptrap (when sent from multiple IPs machines)? I had a similar problem, but I was generating informs from a subagent on a machine with multiple interfaces where I needed to ensure informs were coming from a specific interface. See the thread starting here: http://thread.gmane.org/gmane.network.net-snmp.user/25707/focus=25707 I haven't tried it, but I think if you add '--clientaddr=source_ip' to your snmptrap command line it will get you the result you want. -- Glenn McAllister [EMAIL PROTECTED] +1 416 348 1594 SOMA Networks, Inc. http://www.somanetworks.com/ +1 416 977 1414 -- Message: 4 Date: Tue, 11 Nov 2008 14:16:15 -0600 From: Allen, Bill [EMAIL PROTECTED] Subject: new to net-snmp, installing on HP-UX To: net-snmp-users@lists.sourceforge.net Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii I am new to net-snmp.I have an HP-UX 11.23 system that I am trying to monitor with our local monitoring software - SolarWinds. They say I need to install net-snmp on this HP-UX system for this purpose as the default snmp is not sufficient. So, I have downloaded the latest ixNet-SNMP for HP-UX 11.23 from the HP-UX iexpress software set. I did a swinstall on the depot and it appears that net-snmp installed without any errors. However
RE: snmptrap source ip
Hi Elad: I hope I'm not confusing matters for you, but it sounds like you're encountering the same situation we encountered a year or so ago, where we needed to have V1 traps sent with a specific chosen interface addr of the options available on a multihomed system--reason being that only one of the addresses on the agent would properly reverse-DNS map when looked up by our management station client that was running its own trap daemon and receiving the trap. Aside from the fact you're using informs, sound like you? OK, either way, it might be worth reading my original bug report with submitted patch to 5.4.1: http://sourceforge.net/mailarchive/message.php?msg_id=E1KL19H-0003hG-Ja%40b55xhf1.ch3.sourceforge.com There is some history here. A guy named Jan Safranek from Red Hat got me constructively motivated to actually submit this patch, but it was after he'd submitted his own, which as I recall was almost identical (certainly was functionally) to solve the same problem (my snmpd.conf param is agenttrapaddr, Jan's was something else. The discussion in this report discussed why I don't think clientaddr affects what you want to affect. Now, both Jan and I submitted our patches (Jan's came in much earlier because he's more on top of it it sounds like :), and net-snmp bug authorities were piecing out which or what kind of hybrid to use. I don't know if that was resolved for an official patch release or not. If so, use that. Either way, we've been running with this patch successfully for over a year now. Note that this *only* affects agent-initiated traps (from monitor directives in snmpd.conf). Also, I didn't test this with informs yet, but as I recall the code flow, both should be positively affected. I'll try to follow the digest better than usual if you have any followup questions here...hope this helps! Regards, Wayne Tackabury Mirror Image Internet -Original Message- -- Date: Tue, 11 Nov 2008 15:51:59 +0200 From: Elad Shavit [EMAIL PROTECTED] Subject: RE: snmptrap source ip Thank you Glenn. I have tried using the -Y clientaddr=ip:port flag but with no success. I also tried setting the clientaddr parameter in the snmp.conf file. The outcome is always the same - the outgoing port is the same (I have only one IP on my testing machine so I assume that if I could preset the port, the ip will be also set. Please mind I am working with 5.4.1 netsnmp version. Does snmptrap.exe (windows XP) suppose to be influenced from this parameter or is it only for snmpd and snmptrapd? If only for snmpd and snmptrapd, how can I set the source ip of outgoing traps if I am using the snmptrap.exe to send them? Thanks in advance, Elad Shavit GlassHouse Technologies Ltd. -Original Message- From: Glenn McAllister [mailto:[EMAIL PROTECTED] Sent: Monday, November 03, 2008 6:25 PM To: Elad Shavit Cc: net-snmp-users@lists.sourceforge.net Subject: Re: snmptrap source ip Elad Shavit wrote: Hello all, Does anyone know how can I predict/decide what will be the source ip for sending trap using snmptrap (when sent from multiple IPs machines)? I had a similar problem, but I was generating informs from a subagent on a machine with multiple interfaces where I needed to ensure informs were coming from a specific interface. See the thread starting here: http://thread.gmane.org/gmane.network.net-snmp.user/25707/focus=25707 I haven't tried it, but I think if you add '--clientaddr=source_ip' to your snmptrap command line it will get you the result you want. -- Glenn McAllister [EMAIL PROTECTED] +1 416 348 1594 SOMA Networks, Inc. http://www.somanetworks.com/ +1 416 977 1414 -- Message: 4 Date: Tue, 11 Nov 2008 14:16:15 -0600 From: Allen, Bill [EMAIL PROTECTED] Subject: new to net-snmp, installing on HP-UX To: net-snmp-users@lists.sourceforge.net Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii I am new to net-snmp.I have an HP-UX 11.23 system that I am trying to monitor with our local monitoring software - SolarWinds. They say I need to install net-snmp on this HP-UX system for this purpose as the default snmp is not sufficient. So, I have downloaded the latest ixNet-SNMP for HP-UX 11.23 from the HP-UX iexpress software set. I did a swinstall on the depot and it appears that net-snmp installed without any errors. However, it appears that the system is still configured to load the default HP-UX snmpd snmpdm as they are not linking out to the net-snmp installed versions. So, what do I need to do next? Do I need create snmpd snmpdm links out to net-snmp versions or what? What is SOP for HP-UX and this product. I have not read anything about modifying the rc .d scripts, so I assume that is not the way to go. I did read the README.hp file, but that sounded like what would need to be done if I wanted to compile from source. I should not need to do that since I
RE: snmptrap source ip
Thank you Glenn. I have tried using the -Y clientaddr=ip:port flag but with no success. I also tried setting the clientaddr parameter in the snmp.conf file. The outcome is always the same - the outgoing port is the same (I have only one IP on my testing machine so I assume that if I could preset the port, the ip will be also set. Please mind I am working with 5.4.1 netsnmp version. Does snmptrap.exe (windows XP) suppose to be influenced from this parameter or is it only for snmpd and snmptrapd? If only for snmpd and snmptrapd, how can I set the source ip of outgoing traps if I am using the snmptrap.exe to send them? Thanks in advance, Elad Shavit GlassHouse Technologies Ltd. -Original Message- From: Glenn McAllister [mailto:[EMAIL PROTECTED] Sent: Monday, November 03, 2008 6:25 PM To: Elad Shavit Cc: net-snmp-users@lists.sourceforge.net Subject: Re: snmptrap source ip Elad Shavit wrote: Hello all, Does anyone know how can I predict/decide what will be the source ip for sending trap using snmptrap (when sent from multiple IPs machines)? I had a similar problem, but I was generating informs from a subagent on a machine with multiple interfaces where I needed to ensure informs were coming from a specific interface. See the thread starting here: http://thread.gmane.org/gmane.network.net-snmp.user/25707/focus=25707 I haven't tried it, but I think if you add '--clientaddr=source_ip' to your snmptrap command line it will get you the result you want. -- Glenn McAllister [EMAIL PROTECTED] +1 416 348 1594 SOMA Networks, Inc. http://www.somanetworks.com/ +1 416 977 1414 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
Re: snmptrap source ip
Elad Shavit wrote: Hello all, Does anyone know how can I predict/decide what will be the source ip for sending trap using snmptrap (when sent from multiple IPs machines)? I had a similar problem, but I was generating informs from a subagent on a machine with multiple interfaces where I needed to ensure informs were coming from a specific interface. See the thread starting here: http://thread.gmane.org/gmane.network.net-snmp.user/25707/focus=25707 I haven't tried it, but I think if you add '--clientaddr=source_ip' to your snmptrap command line it will get you the result you want. -- Glenn McAllister [EMAIL PROTECTED] +1 416 348 1594 SOMA Networks, Inc. http://www.somanetworks.com/ +1 416 977 1414 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
