-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Protocol Updates #83
Protocol Updates #83
Conversation
Things to add/added
|
Co-Authored-By: twistedddx <bits@live.com>
Co-Authored-By: twistedddx <bits@live.com> Conflicts: dissector/baichuan.lua src/bc_protocol.rs src/bc_protocol/media_packet.rs
Co-Authored-By: twistedddx <bits@live.com>
Using u8 for channel id throughtout Using simpler map_err Co-Authored-By: twistedddx <bits@live.com>
Co-Authored-By: twistedddx <bits@live.com>
Now with added AES encryption protocol. See #149 |
Is this ready to go? I had been mostly ignoring it while it was marked draft. |
Yes it should be now. The only thing I might want to add is getting SD and HD streams together. Alot of checks are failing though need to see why |
Ahh we need openssl now in the docker images |
If you wouldn't mind separating out HD+SD, that would be appreciated. This is taking a minute to digest :) |
Want to grab a pure Rust AES implementation? I had tentatively selected |
644d888
to
30fad08
Compare
Yes that was it all is fine again.. Sigh that was embarassing |
Ok changes have been made but I want to try changing to pure rust AES. If you want to have a go at that please do else I'll work on it tomorrow |
Done changing to pure Rust. CI seems happy. See my branch. I checked performance on a lark and the debug build now uses a lot more CPU (10% of my 5-year-old i5). But the release build is < 1%, so it's fine. |
Ok so it looks good now and all the checks pass except clippy. In the case of clippy it is because of issues with the |
89fc52d
to
05cb032
Compare
Everything should now pass and I've even updated the tests. Please review when you can |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks for all the work.
Awesome. Next job is SD and HD in the same login. |
Any comments on subscribing on msg number over message id |
I am going to tackle getting a Windows service implemented. It is long
overdue.
…On Sat, Apr 17, 2021, 10:37 PM Andrew King ***@***.***> wrote:
Awesome. Next job is SD and HD in the same login.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#83 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA6E7ZKGTU37OO3HJ5A4AWDTJJHY3ANCNFSM4SROMDIA>
.
|
I had a little look into the service as part of #66. I came up with two solutions. Either Maybe tackle an MSI too so we can close #1 too. If you do want to tackle the MSI maybe have a look at #66 as that has a go at it. |
@twistedddx The current master version should now be able to handle unencrypted connections for the older cameras. Could you maybe try it when you get the chance? |
Neolink now works great with the older cams using unencrypted XML. |
Thanks for testing. I'm glad we can close this one. |
…ocol_updates Protocol Updates
This contains updates to the protocol and is set as a draft for now as I think it should be discussed. In the PR #80 we analysed the messagse in more detail and discovered that xmls of the form.
Always went after in the binary block offset
And that xmls of the form
Always went before the binary block offset.
I believe this means that we were serde'ing incorrectly. It only worked before because neolink only ever sent Extension xml where it correctly set binary_offset to the message length. We also only every received either
This applies appropriate changes so that extension xml is always before the binary_offset which is renamed to payload offset, and that body xml and binary payloads are after the payload_offset
This simplifies the serde so we don't need to keep in_bin_mode in context which was a nice bonus
This also include the changes requred to send command and control messages to neolink that was required for the MQTT PR #78
P.s. Also applied some things to the readme: formatting, fixed some of my spelling mistakes and closed an unclosed backtick.