Mike Stupalov

@etingof no any suggestions?

@etingof I know, this is simple way.. but I have contributed walks, which not possible for re-walk again.

This lines skipped when converting as: ``` # Skipping broken record : broken record ``` ``` # Skipping broken record : broken record ```

This is not fix, but in documentation for snmpwalk dump, better example is: ``` snmpwalk -v2c -c --hexOutputLength=0 -ObentxU .1 ``` > hexOutputLength integer > Specifies where to break up...

Just for self I'm written simple fixer script (that deletes new line char between multiline string). Need to run before datafile.py as: ``` snmpwalk_fix_multiline.py ``` Fixed snmpwalk will stored as...

Funny.. Of course "Killed" is a OS message, when memory ran out. I was able to convert the file, breaking it into 4 parts.. But I not think this is...

@Lostboi You can also merge #141 pull request. I'll be watching the development of your fork. I'm not sure what happened to Ilya (@etingof), since May this year he has...

Output in daemon console: ``` Using /home/mstupalov/snmpdata/dellsan4024.snmprec controller selected by candidate b'0f90dab4314ebe9922fb7aa000e93f17'; transport ID 1.3.6.1.6.1.1.0, source address 77.222.50.30, context name "b'0f90dab4314ebe9922fb7aa000e93f17'" SNMP EngineID 0x80004fb8056176617461722e636f6f736d2e6e65744cbbc908, transportDomain (1, 3, 6, 1, 6,...

Seems as this is again HEX trouble (with escaped strings). Originally this Oid fetched by snmpwalk as: ``` .1.3.6.1.3.94.1.6.1.1.32.128.0.192.255.240.92.111.0.0.0.0.0.0.0.0 = Hex-STRING: 20 80 00 C0 FF F0 5C 6F 00...

For self I recrete this dump without _escaped-strings_ option, and walking now ok, but issue for escaped string actual.