Video Doorbells/IOT Devices

Started by Rockyuk, September 16, 2024, 03:33:09 PM

Previous topic - Next topic
Hello Everyone,
Has anyone updated to 24.7.4_1? Since I have updated I cannot see any live video views (doorbell and indoor CCTV) via my WIFI MESH, before the updates it was working perfectly. I'm not sure what could have changed that via the update is anyone else having similar issues?

Thanks

Rockyuk

I run IoT devices in separate VLAN. And no such issue.

Are you sure your IoT devices are connected to the WiFi?
Try to ping them.

Regard,
S.
Networking is love. You may hate it, but in the end, you always come back to it.

OPNSense HW
APU2D2 - deceased
N5105 - i226-V | Patriot 2x8G 3200 DDR4 | L 790 512G - VM HA(SOON)
N100   - i226-V | Crucial 16G  4800 DDR5 | S 980 500G - PROD

I can ping and connect to the devices fine the only issue is they will not play live video anymore. Just randomly stopped after the update.

If you created a snapshot before upgrading you can rollback and test if it works on previous release.

Regards,
S.
Networking is love. You may hate it, but in the end, you always come back to it.

OPNSense HW
APU2D2 - deceased
N5105 - i226-V | Patriot 2x8G 3200 DDR4 | L 790 512G - VM HA(SOON)
N100   - i226-V | Crucial 16G  4800 DDR5 | S 980 500G - PROD

Nope, I don't think I did, so I am assuming there is not much else I can do in terms of rolling back?

There is a way revert command for going back in a release but it shouldn't be used for cases like these.

So sadly the answer is no.


You can try to inspect the live log, what is happening during the when you watch the video.
Or do a PCAP and try to analyze the stream.

Regards,
S.
Networking is love. You may hate it, but in the end, you always come back to it.

OPNSense HW
APU2D2 - deceased
N5105 - i226-V | Patriot 2x8G 3200 DDR4 | L 790 512G - VM HA(SOON)
N100   - i226-V | Crucial 16G  4800 DDR5 | S 980 500G - PROD

Ok, after digging a little deeper I did a packet capture on the Apps on my Android phone RTP & STUN are being blocked and some DNS queries on port 53.


Well then do you have proper rules?
Does the RTP & STUN session happen between your device and the IoT?

Regards,
S.
Networking is love. You may hate it, but in the end, you always come back to it.

OPNSense HW
APU2D2 - deceased
N5105 - i226-V | Patriot 2x8G 3200 DDR4 | L 790 512G - VM HA(SOON)
N100   - i226-V | Crucial 16G  4800 DDR5 | S 980 500G - PROD

Quote from: Rockyuk on September 16, 2024, 06:18:01 PM
Ok, after digging a little deeper I did a packet capture on the Apps on my Android phone RTP & STUN are being blocked and some DNS queries on port 53.
I experienced a problem with RTP failing due to packet size on releases newer than 24.7, something to do with how fragmentation is now being processed.  As a workaround I had to edit the VoIP phone and remove enough codecs from its configuration to allow packets to go through.  Perhaps your problem is related?

Hey Rockyuk,

Yeah, I've seen a few people mention similar issues after the update. It seems like something in the new version may have affected how the video streams are handled over certain network configurations, especially with mesh setups.

You could try a couple of things:

Clear your browser or app cache if you're viewing through a web interface or mobile app.

Check if the mesh system has any recent firmware updates — sometimes compatibility issues arise after system updates.

If possible, test direct connection (bypassing the mesh) to confirm whether it's definitely related to the network layer.

If none of that helps, it might be worth rolling back temporarily or reporting the bug on the project's issue tracker so the devs can address it in the next patch.
Recently, I came across an insightful article on how technology improves accessibility for people with disabilities — highly recommend checking it out here: https://www.cogniteq.com/blog/iot-people-disabilities-how-technology-makes-their-lives-better.
.