You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, encrypting this xml file back to a .bin file, it doesn't work properly. This was my command:
python3 tpconf_bin_xml.py -l original.xml original.bin
> OK: XML file - compressing, hashing and encrypting…
> Done.
Here's an image of the hex side by side, with the bin output from the tpconf tool on the left and the original bin from the router on the right:
As you can see, the first 4 hex bytes are different, and I don't know why. Everything else is the same. The router moans when I try to upload it. Any ideas as to why this would be happening?
Funnily enough, when using the tool to decrypt the already encrypted file (original.bin), it comes out as expected. My hypothesis is that there's some sort of encoding issue, but I'm not sure :)
The text was updated successfully, but these errors were encountered:
Try using the -s / --skiphits option required for some Archer models. (see -h / --help) python3 tpconf_bin_xml.py -l -s conf.xml newconf.bin
It's automatically applied to older Archer C2x v1 models, but not to newer version like your (v5); C2 v5 apparently doesn't use it, but perhaps C20 v5 does? It was difficult to get a clear picture of exactly which models/versions use the older compression.
When using the tool to decrypt the file, it works well. My command was as follows:
Here are the first few lines of the decrypted XML:
However, encrypting this xml file back to a .bin file, it doesn't work properly. This was my command:
Here's an image of the hex side by side, with the bin output from the tpconf tool on the left and the original bin from the router on the right:
As you can see, the first 4 hex bytes are different, and I don't know why. Everything else is the same. The router moans when I try to upload it. Any ideas as to why this would be happening?
Funnily enough, when using the tool to decrypt the already encrypted file (original.bin), it comes out as expected. My hypothesis is that there's some sort of encoding issue, but I'm not sure :)
The text was updated successfully, but these errors were encountered: