Re: how to specify source IP address / interface when sending traps (with Solaris IP multipathing )

This is really crazy.  I just started looking into this problem and this 
thread happens to be fresh.  I have the same problem, except I need to be 
able to specify SNMP Trap UDP source addresses on systems acting as IPSec 
VPN gateways.

It's hard to belive that no one has asked for this feature in the years 
that Net-SNMP has been around.

In order for my agent to send traps to an NMS on the other side of the 
IPSec tunnel, the source address must be that of the ethernet interface 
(because OpenBSD IPSec does not allow multiple subnets to match an 
interesting traffic list, like Cisco IOS).

Speaking of IOS, Cisco has had an "snmp source-interface" or 
"source-address" statement for the last 10 years >:}

"snmp-server trap-source

To specify the interface (and hence the corresponding IP address) that an 
Simple Network Management Protocol trap should originate from, use the 
snmp-server trap-source global configuration command. Use the no form of 
the command to remove the source designation.

 	"snmp-server trap-source interface"

 	Release		Modification
 	10.0 		This command was introduced. "

What sucks even more is that the OpenBSD 3.7 package binary distribution
of Net-SNMP is rev 5.1.2p1 and per the remark below, the 'clientaddr' 
feature was backported to 5.1.3.

~BAS

On Mon, 15 Aug 2005, Robert Story wrote:

> On Sat, 13 Aug 2005 14:10:22 +1000 Russell wrote:
> RB> What we've ended up doing is changing get_myaddr() in snmplib/system.c
> RB> which works; the primary IP address (the address returned by
> RB> gethostbyname) is sent in the SNMP pdu.  [Rob, I've sent you the changed
> RB> system.c]
> RB> [...]
> RB> While the new get_myaddr() works, I don't know for sure if it's
> RB> correct/safe for all platforms.  It would be best if someone involved in
> RB> net-snmp development could have a look, so we can get a robust fix
> RB> incorporated in the development source base.
>
> The version you sent looks exactly like the current code in 5.1.3 and 5.2.x...
>
> -- 
> NOTE: messages sent directly to me, instead of the lists, will be deleted
>      unless they are requests for paid consulting services.
>
> Robert Story; NET-SNMP Junkie
> Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp>
> Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-users>
>
> You are lost in a twisty maze of little standards, all different.
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Net-snmp-users mailing list
> [email protected]
> Please see the following page to unsubscribe or change other options:
> https://lists.sourceforge.net/lists/listinfo/net-snmp-users
>

l8*
 	-lava

x.25 - minix - bitnet - plan9 - 110 bps - ASR 33 - base8


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users