garbage filters in "DisplayString"

gentelmen,

could somebody please explain the following curiosities i am experiencing with net-snmp (i'm converting oid's to ascii representation, but can not achieve same result as snmp-agend does)

below is a correct output of snmp-agent:
JUNIPER-FIREWALL-MIB::jnxFWCounterPacketCount. 
 "Balticum_in"."Balticum_in".counter = Counter64: 5708439665
 
 JUNIPER-FIREWALL-MIB::jnxFWCounterPacketCount. 
 "Balticum_in"."Balticum_in-input".policer = Counter64: 27
 
 JUNIPER-FIREWALL-MIB::jnxFWCounterPacketCount. 
 "microlink_peer_in"."microlink_peer_in".counter = Counter64: 105103046552

but, oid values (representing decimaly indexed ascii symbols) seems to have some aditional info (marked red):
.1.3.6.1.4.1.2636.3.5.2.1.4.
11.66.97.108.116.105.99.117.109.95.105.110.11.66.97.108.116.105.99.117.109.95.105.110.2 = Counter64: 5708439665

.1.3.6.1.4.1.2636.3.5.2.1.4.
11.66.97.108.116.105.99.117.109.95.105.110.17.66.97.108.116.105.99.117.109.95.105.110.45.105.110.112.117.116.3 = Counter64: 27

.1.3.6.1.4.1.2636.3.5.2.1.4.
17.109.105.99.114.111.108.105.110.107.95.112.101.101.114.95.105.110.17.109.105.99.114.111.108.105.110.107.95.112.101.101.114.95.105.110.2 = Counter64: 105103046552

Acording to (http://net-snmp.sourceforge.net/docs/mibs/ucdDlmodMIB.html#textconventions) - graphics characters (32-126) are interpreted as US ASCII, 0-31 have speciall meaning.

Here's the whole table of aditional indexes i've found. (symbols in double quotes "" arre allready converted to ascii)
11 11 2
11 17 3
12 21 2
12 25 2
12 30 3
12 "&" 3
17 17 2
17 29 3
18 18 2
18 30 3
18 18 2
18 30 3
19 19 2
19 " " 3
22 22 2
22 "&" 3
23 23 2
23 "(" 3
23 23 3
25 21 3
26 26 2
26 " " 3
27 "$" 2
27 "("  2
27 "("  2
27 "-"  3
27 5 3
27 20 3
29 29 2
29 " " 3
30 30 2
30 """ 3
31 31 31 
31 "#" 3
31 31 2
31 """ 3
"#" "#" 2
"$" 1 3
"'" "'" 2
"'" "7" 3
"(" "(" 2
"(" "9" 3
 
As you can see - i have a garbage in output [ symbols like &,$,#,",),(,7,9 ]
So, instead of "Balticum_in"."Balticum_in" i have "Balticum_in9Balticum_out" etc...

Is this a faulty mib issue? How does the snmp agent manages to  show correct results?
I've taken a look at sources, but was unable to find an explanation of this misbehaviour.

any thoughts are welcome...

thank you

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users