# snmpd and pass-persist

**URL:** <https://forums.digi.com/t/snmpd-and-pass-persist/6173>\
**Category:** Linux\
**Created:** [July 9, 2012, 4:05pm UTC](https://forums.digi.com/t/snmpd-and-pass-persist/6173 "2012-07-09T16:05:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![DJEE](https://avatars.discourse-cdn.com/v4/letter/d/eada6e/32.png) [@DJEE](https://forums.digi.com/u/DJEE)\
**Post date:** [July 9, 2012, 4:05pm UTC](https://forums.digi.com/t/snmpd-and-pass-persist/6173/1 "2012-07-09T16:05:40Z")

</div>

Hello,

Has anybody experience recompiling the snmpd daemon in the Digi EL toolchain, enabling the pass-persist option (–with-mib-modules “ucd-snmp-extensible ucd-snmp-pass ucd-snmp-pass\_persist”)?

We did this but unfortunately when requiring an OID within the pass-persist subtree, our external program receives the PING, replies a PONG and then nothing…

Our target is a Digi Me 9210.

Thank you.

---

<div class="post-metadata">

**Author:** ![elisa.scandellari](https://avatars.discourse-cdn.com/v4/letter/e/e47774/32.png) [@elisa.scandellari](https://forums.digi.com/u/elisa.scandellari)\
**Post date:** [August 9, 2012, 4:31pm UTC](https://forums.digi.com/t/snmpd-and-pass-persist/6173/2 "2012-08-09T16:31:42Z")

</div>

Hi,  
I’m having a similar issue… did you manage to find a way to rebuild the snmpd daemon?

Elisa

---

<div class="post-metadata">

**Author:** ![f.kerkhoff](https://avatars.discourse-cdn.com/v4/letter/f/5e9695/32.png) [@f.kerkhoff](https://forums.digi.com/u/f.kerkhoff)\
**Post date:** [August 14, 2012, 7:36am UTC](https://forums.digi.com/t/snmpd-and-pass-persist/6173/3 "2012-08-14T07:36:53Z")

</div>

Hello!

basically, there are two options to use individually compiled tools and libraries in your project:

- Make the setup (e.g. ‘make menuconfig’) completely independent from your project and just add the relevant files using add\_files.sh (/configs/add\_files.sh in yout rootfs-project)
- The “Digi-way”: You can (re-) configure and compile a component of the toolchain and then integrate it in the template for any further rootfs (using ‘make install-del’).

There are two KB articles describing both ways:  
[http://www.digi.com/support/kbase/kbaseresultdetl?id=3281](http://www.digi.com/support/kbase/kbaseresultdetl?id=3281)  
[http://www.digi.com/support/kbase/kbaseresultdetl?id=3161](http://www.digi.com/support/kbase/kbaseresultdetl?id=3161)

I’m currently using a DigiEL-5.2-environment with many manually compiled components and can give further information about cross-compiling and add\_files.sh.

F. Kerkhoff

---

<div class="post-metadata">

**Author:** ![elisa.scandellari](https://avatars.discourse-cdn.com/v4/letter/e/e47774/32.png) [@elisa.scandellari](https://forums.digi.com/u/elisa.scandellari)\
**Post date:** [September 17, 2012, 2:37pm UTC](https://forums.digi.com/t/snmpd-and-pass-persist/6173/4 "2012-09-17T14:37:55Z")

</div>

Hi,

try with this (obviously change the other options to what you need):

./configure   
CC=/usr/local/DigiEL-5.2/usr/bin/arm-linux-gcc   
CXX=/usr/local/DigiEL-5.2/usr/bin/arm-linux-g++   
host\_alias=arm-linux   
–with-endianness=little   
–prefix=/usr/local/DigiEL-5.2/usr   
–sysconfdir=/etc   
–target=arm-linux   
–host=arm-linux   
–build=i486-linux-gnu   
–disable-perl   
–disable-embedded-perl   
–disable-perl-cc-checks   
–without-perl-modules   
–enable-as-needed   
–with-default-snmp-version=2   
–with-logfile=/var/log/snmpd.log   
[--with-sys-contact=root@ntcip.com](mailto:--with-sys-contact=root@ntcip.com)   
–with-sys-location=Unknown   
–with-persistent-directory=/var/net-snmp   
–with-mib-modules="“ucd-snmp-extensible ucd-snmp-pass ucd-snmp-pass\_persist”   
–with-ar=/usr/local/DigiEL-5.2/usr/bin/arm-linux-ar   
–with-ld=/usr/local/DigiEL-5.2/usr/bin/arm-linux-ld   
–without-dmalloc   
–without-efence   
–without-kmem-usage   
–without-rpm   
–without-rsaref

(the last five are options enabled in the original daemon of the digi module)  
Elisa