agentjdh

@stephb9959 I'd come to the exact same numbers effectively from using xxd to take a hex dump of a working binary. So this part looks correct. The actual Docsis tool,...

[mta_WORKING_999999.bin.gz](https://github.com/rlaager/docsis/files/3728451/mta_WORKING_999999.bin.gz) [mta_NOT_WORKING.bin.gz](https://github.com/rlaager/docsis/files/3728459/mta_NOT_WORKING.bin.gz)

@stephb9959 I've replaced docsis.c with the one you provided and re-compiled. Looks like something is going wrong - generating a binary using ./docsis -dialplan -spechash -p mta_WORKING.txt mta_WORKING.bin SnmpMibObject pktcMtaDevProvConfigHash.0...

I don't know how that code section got in above, ignore it.

@stephb9959 I am not getting those errors now, but the generated file is still +1 byte, and is rejected by the modem. [files.tar.gz](https://github.com/rlaager/docsis/files/3738058/files.tar.gz) I've attached the files, here is what...

@stephb9959 What you did there is exactly what I was doing - decoding a working binary to text + dialplan, deleting the hash line from the text file, then rebuilding...

@stephb9959 I've done exactly that, with the same results. The bizarre thing is, once I have encoded the binary that is +1 byte ("wrong"), if I then decode this to...

Debian please

@stephb9959 Thanks Stéphane, it looks like the file created is the same size (8481 bytes) as before. So I guess it is not the binary then. Which pretty much leaves...

Turns out it was the decoding to text file that was using the "wrong" OID for pktcMtaDevEnabled The particular modem I was using required the 1.3.6.1.2.1 OID from PKTC-IETF-MTA-MIB It...