SNMP daemon not active on port 161 (or anywhere); daemon loaded.

SNMP daemon not active on port 161 (or anywhere); daemon loaded.

Post by Brian Fahrlande » Thu, 18 Jun 1998 04:00:00

I'm running RedHat 5.0+ (Updates to 5.0, but not a 5.1 fileset) and
I've loaded cmu-snmp.  I've edited /etc/snmpd.conf, though it's supposed
to work without changes, and I'm not getting any responses (even error
messages) from port localhost:161.

    Some issues:

    1. I'm using strobe to check ALL ports that might be listening.
This works for lpr, www, and all the better known protocols, but
wouldn't it show up if snmpd was set up properly?  (Otherwise I can't
really check it's operation.)

    2. Is there any authentication that I might be overlooking, simply
to look at the public MIBs?  I know there's authentication for writing
(anywhere) and reading private ones.

    All I want is enough of SNMP to work so that I can build my
understanding of it.  I've tried scotty; it worked even less than CMU.
I spent two hours last night trying to get their browser (tkined) as a
seperate package to no avail.  At least with  CMU I have parts the
ostensibly work without my learning SNMP AND Tcl/TK all at the same

    I just don't have enough 'parts' that work enough to tell if I can
even use the final result.  Usually this would be because I lacked a
certain library file that the tarball needs...but I'm installing by RPMs
here, RPMs that SHOULD have been packed by someone who knows when the an
implementation of SNMP is working.  (He'd know better than I).

    One more thing...did someone forget the first word of the SNMP
acronym?  Simple?  There are tons of subsets for this technology.  There
are agents that can only send a value (and only one) after receiving a
single request....and there are superior agents that will answer
anyone's request no matter how many times it's asked. (Asynchronous
traps.)  The funny thing is, CMU uses synchronous traps, and IT'S
declared the standard.

    At what point does the 'simple' kick in?


Brian Fahrlander                       Problem Solver, Technomad, and
Evansville, IN
 Whitewater isn't over until the First Lady sings.


1. Port 161 SNMP (Simple Network Management Protocol)

: I installed PortSentry and within just a few hours it logged this:

: I looked up what port 161 is and it turns out to be SNMP (Simple Network
: Management Protocol) but I can't find any more information on this.  Does
: anyone know what can be done to my system if someone who knows what they're
: doing connects to this port?

try "snmpwalk <some host> public" somewhere you are allowed to.

Some systems give out a scary amount of information (Digital Unix, NT
for instance). Linux RedHat gives out virtually nothing by default. You
can set your name and location if you want, or let people monitor
your traffic on an internal network.

Normally, one can read "public" but not write. If set up, then yes,
someone can change things. Otherwise, it often gives out interesting
information like who you've been talking to recently and maybe even
who's logged on, what disks are mounted, etc.

Andrew Daviel
Deniable unless digitally signed.

2. source code for boot.bin on Solaris x86?

3. Port 161

4. How do I log in as 'root' from the CLI?

5. Linux not loading NFS daemons due to RPC failure

6. Halting diskless workstations before powering down

7. UDP Hits on port 161

8. BOOT Sequence

9. "UDP port 161" concern??

10. Can't bind port 161

11. NFS Daemon Failed to load: nfssvc not Implemented

12. Is there any daemon-auditing daemon utility?

13. cgi program which is a daemon/starting daemon from cgi