Closed tomaspre closed 9 months ago
Can you capture the connection data with the official client. Will compare it to what we do
Recently I've seen some cameras not report valid registration details from Reolink. It's possible that the official client has changed the protocol a little bit and I'll need to adjust how we do it
I captured the data. Can I send you a private message somewhere? I'm a bit too paranoid to post a dump from my network publicly.
Grab my email from GitHub I suppose.
You could also install the our wireshark dissector then filter on baichan packets
I sent you an email with the captured data. Let me know if there is anything else I can help with.
I solved the issue. It had no connection to neolink whatsoever. My Proxmox host decided not to let one particular LXC use DNS (an identical container with neolink worked while the one with the errors above would not). I'm sorry I wasted your time and thanks so much for the amazing software!!
Happens with my docker sometimes to, spent ages trying to resolve an error only to find out that it was the DNS calls
Describe the bug When I try to launch Neolink with a cellular camera config, I keep getting Registration with reolink servers failed.
Config
Log
To Reproduce Steps to reproduce the behavior:
Versions NVR software: None, just trying to get an image. The same thing happens when launching with RTSP. Neolink software: 0.6.2 Reolink camera model and firmware: Go PT Ultra, FW: 3.0.0.2329_23061311 (most recent)
Details