RE: snmpd and interface aliases

I had a similar problem with snmpd on Edgy, it would only respond on
localhost. I ended up using the "agentaddress" variable in snmpd.conf
and forced address.

#excerpt from man snmpd.conf

       agentaddress [<transport-specifier>:]<transport-address>[,...]
              Makes the agent list on the specified comma-separated
list of
              listening addresses instead of the default behaviour,
which is
              to listen on UDP port 161 on all IPv4 interfaces. See
the sec-
              tion LISTENING ADDRESSES in the snmpd(8) manual page for
more
              information about the format of listening addresses. For
exam-
              ple, specifying agentaddress 161,tcp:161,localhost:9161
will
              make the agent listen on UDP port 161 on all IPv4
interfaces,
              TCP port 161 on all IPv4 interfaces and UDP port 9161
only on
              the interface associated with the localhost address.

#/excerpt

Oh -- and are those two WAN IPs?

Chris Twa

Saskaweb IT Solutions

-----Original Message-----
From: owner-linux@slg.org [mailto:owner-linux@slg.org] On Behalf Of
Steven Kurylo
Sent: Monday, June 16, 2008 11:52 AM
To: SLG
Subject: snmpd and interface aliases

I have a server which now has two routable address:

eth0 inet addr:64.142.xx.xx
eth0:1 inet addr:76.191.xx.xx

I can ssh into either just fine. But snmpd is only responding on the
original interface. My queries to 76.191.xx.xx timeout.

It is listening on both IP addresses:

# netstat -lnutp|grep snmpd
tcp 0 0 0.0.0.0:199 0.0.0.0:*
LISTEN 6765/snmpd
udp 0 0 0.0.0.0:161 0.0.0.0:*
        6765/snmpd

Looking in /etc/default/snmpd and /etc/snmp/snmpd.conf I don't see any
options specifying the address to listen on.

I'm not sure what else to check. No firewalls, unless the ISP is
blocking 161 on the new address; nmap shows the same response for both
IPs, "161/udp open|filtered snmp"

Could snmpd not work with interface aliases?

Thanks.
Received on Mon Jun 16 12:10:19 2008