Re: listening address format

On 19 January 2011 18:32, Barry Leggett <[email protected]> wrote:
> I'm required to make sure any request to the snmp daemon is on a particular
> Ip address/port combination for security.
> eg 192.168.0.20:1032, 192.168.0.30:1046 etc as we previously had.
> The documentation and comments in snmpd.conf imply that this can
> be done through agentaddress-

I've just check, and yes - this can be done using the "agentaddress" directive.

However, some of the comments in the snmpd.conf file are slightly misleading
(i.e. wrong!)


> #    Multiple definitions of this token
> #   are concatenated together (using ':'s).

Multiple addresses should be separated using commas, not colons
(Or else have several "agentaddress" lines - one per address)


> #   arguments: [transport:]port[@interface/address],...

The syntax for listening addresses is the same as when specified
on the command-line, i.e.

     transport:address:port

So an snmpd.conf file containing

    agentaddress   192.168.0.20:1032,192.168.0.30:1046
           (note, no space)

or

    agentaddress    192.168.0.20:1032
    agentaddress    192.168.0.30:1046

should do what you require

Dave

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
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