SNMP trouble

I was attempting to mess with the snmp daemon of my router. So I did a UDP port scan to be sure it was actually running:
161/udp open snmp

Ok, so I telnet (23/TCP) into my router and do a 'cat snmpd.cnf' and this is that config file's content:

Code:

---

sysDescr  "SANTIS 50 ADSL Router"

sysObjectID  1.3.6.1.4.1.3646.100.30

sysLocation  -

sysContact  -

sysName  -

snmpEnableAuthenTraps  0

community  private 0.0.0.0 write 1
community  public 0.0.0.0 read 0

trap  public 192.168.1.1

---

192.168.1.1 is my router's internal IP address.
I must not really understand this part:
community private 0.0.0.0 write 1
community public 0.0.0.0 read 0

trap public 192.168.1.1

I have downloaded a program to query snmp stuff (windows). As far as I know it should be possible to query the above things, no? sysDescr and sysObjectID?

I don't understand what is meant by 'trap'.
Upon querying using a Get request from my computer (192.168.1.3) this is returned: return code=10004 (Timed out)
I used public as the community string.

Can somebody explain what I should change in my router's config so that it does accept requests from all computers (inside lan).

a snmp trap is a subdaemon you enable or set within the snmp-daemon. And on that trap you define if its ro (readonly) or rw (read/write) , as well as the hosts that may ro or rw that trap.

I believe your trap is now only accessible by or via 192.168.1.1. try changing that to 192.168.1.0/24 or 192.168.1.0 255.255.255.0.

Hope this helps,

If you haven't already read it, appendix E of Perl for System Administrators is a good intro to SNMP.

20 minute SNMP tutorial


Also try the demo version of Solarwinds MIB Walk

HTH

Quote:

---

Originally posted here by .: Shrekkie :.
a snmp trap is a subdaemon you enable or set within the snmp-daemon. And on that trap you define if its ro (readonly) or rw (read/write) , as well as the hosts that may ro or rw that trap.

---

:confused:

An SNMP trap is send to a host if some preset level is reached.
You can for example set a trap when the cpu usage is above 80%. The trap will be send to the defined host, running some management software (Openview i.e.), which in turn can alert an administrator (by email, SMS, pager etc.).

Thanks, Shrekkie's post made me confused too (no offense)....lol
So it's conceptually very similar to an os trap...

Did you try this?

community public 192.168.1.3 read 0