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

List:       net-snmp-coders
Subject:    Re: configure interface to send traps
From:       Pushpa Thimmaiah <pushpa.thimmaiah () gmail ! com>
Date:       2018-10-14 15:58:43
Message-ID: CAASqVJWUG2C4XiD0xUxzckUwatziJnjE7=RPEjfQcFjUa27BYw () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Thank you Bill Fenner.

On Sat, Oct 13, 2018 at 8:29 PM Bill Fenner <fenner@gmail.com> wrote:

> On Thu, Oct 4, 2018 at 1:19 AM Pushpa Thimmaiah <
> pushpa.thimmaiah@gmail.com> wrote:
>
>> Hi All,
>>
>> I have understood that option 'clientAddr'  to provide source-IP address
>> for outgoing traps.  There is no option to provide source-interface to send
>> traps.
>> Kindly let me know reason for this restriction.
>>
>
> The source IP address is all that the UNIX socket interface allows
> net-snmp to control.  (There's an exception for the case that the trap
> receiver is directly connected on the given interface, but when that is
> true, it almost always works the way you want anyway.)
>
> Eg: I have one physical interface 'eth1' and vlans 'eth1.101', 'eth1.102'.
>> Traps sent out via eth1 by default . How can configure 'snmptrap' tool to
>> use eth1.101 to send traps.
>>
>
> Configure your routing table so that packets towards the trap destination
> go out eth1.101.
>
>   Bill
>
>

[Attachment #5 (text/html)]

<div dir="ltr">Thank you Bill Fenner.<br></div><br><div class="gmail_quote"><div \
dir="ltr">On Sat, Oct 13, 2018 at 8:29 PM Bill Fenner &lt;<a \
href="mailto:fenner@gmail.com">fenner@gmail.com</a>&gt; wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr">On \
Thu, Oct 4, 2018 at 1:19 AM Pushpa Thimmaiah &lt;<a \
href="mailto:pushpa.thimmaiah@gmail.com" \
target="_blank">pushpa.thimmaiah@gmail.com</a>&gt; wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div>Hi \
All,<br><br></div>I have understood that option &#39;clientAddr&#39;   to provide \
source-IP address for outgoing traps.   There is no option to provide \
source-interface to send traps.<br></div>Kindly let me know reason for this \
restriction.    <br></div></div></div></div></div></blockquote><div><br></div><div>The \
source IP address is all that the UNIX socket interface allows net-snmp to control.   \
(There&#39;s an exception for the case that the trap receiver is directly connected \
on the given interface, but when that is true, it almost always works the way you \
want anyway.)</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Eg: I \
have one physical interface &#39;eth1&#39; and vlans &#39;eth1.101&#39;, \
&#39;eth1.102&#39;.<br></div>Traps sent out via eth1 by default . How can configure \
&#39;snmptrap&#39; tool to use eth1.101 to send \
traps.<br></div></div></div></blockquote><div><br></div><div>Configure your routing \
table so that packets towards the trap destination go out \
eth1.101.</div><div><br></div><div>   Bill</div><div><br></div></div></div> \
</blockquote></div>





_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders


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