Reply With QuoteNever write "latest", always specify full version info!Originally Posted by viktike
Anyway, if firmware still alive and net-snmp dies only, it is a problem of net-snmp itself.
btw, firmware itself contains old ucd-snmp 3.6.2
Junior Member
I'm trying to use net-snmp. When I locally try to walk through my community, It alway times out and dies after the kernelcmd. Did anyone experienced this?
Any idea of solution?
I'm running: 1.9.2.7-d-r1445, latest net-snmp. I did tried previous firmwares.
Forum Guru
Never write "latest", always specify full version info!
Anyway, if firmware still alive and net-snmp dies only, it is a problem of net-snmp itself.
btw, firmware itself contains old ucd-snmp 3.6.2
Junior Member
Sorry for the incorrect version. It's 5.4.2.1.
I tried the bulitin ucd-snmp. But it's not accessable from the WAN port. I tried to forward 161 udp, but it's not working. I also tried to get agentaddress variable in the configuration with 0.0.0.0, but it didn't helped.
Then I decided to use the package. I checked the /opt/var/log/snmpd.log:
ipSystemStatsTable node ipSystemStatsOutFragOKs not implemented: skipping
And here it dies completly. Only killall -9 snmpd helps.
All ideas are welcome.
Forum Guru
I apologize, that my idea is not good for non-developers...
net-snmp 5.x seems to be not fully compatible with our ancient kernel 2.4.37 & uClibc and has to be patched.
Junior Member
Thanks for the informqationBut, alright, it won't work with snmpwalk, but I tried to access the information with catci, and it works... Even when I ask for HOST MIBs data. So it's good news.
Anyway, how is this patch process works? I mean I know, the C source files should be modified, but who does it? Or what for? Who selects the packages to be updated? Just courius.
Thanks
Forum Guru
Ask google, maybe someone done this job. Otherwise, you have to locate & fix bug yourself.
Posting Permissions