mryel00
commented
6 days ago That's some interesting bug. But as you already noticed, Crowsnest is basically doing nothing, that could create this problem. I recommend to get Nginx, Mainsail and Crowsnest out of the equation and test it only with ustreamer. So run the following command:
/home/tj/crowsnest/bin/ustreamer/ustreamer --host 0.0.0.0 -p 8080 -d /dev/v4l/by-id/usb-046d_HD_Pro_Webcam_C920_809E7D1F-video-index0 --device-timeout=2 --encoder=HW -r 1280x720 -f 10 --allow-origin=* --format=yuyvThen connect to http://<ip.of.your.pi>:8080/?action=stream and see if you can reproduce the issue like that.
zimmertr
rackrick
meteyou
What happened
I recently flashed my printer to run Klipper which is driven by a Raspberry Pi 5. The Pi is installed beneath the printer in it's electronics housing which results in poor wireless reception. So I purchased a USB wireless adapter with an antenna that sits outside of the printer. This works great, however, I've been chasing down a bug where the Pi would randomly disconnect from my network when I would interact with Mainsail, Fluidd, or KlipperScreen. I believe the ultimate catalyst if the bug in all of these cases is Crowsnest.
The Internal wireless chip is
wlan0and the USB wireless adapter iswlan1. I run Raspberry Pi OS Lite which uses NetworkManager. I've defined a connection profile forwlan1but notwlan0. So, on boot,wlan1comes up and gets an IP from my router through a static ip reservation.This all works great, and I can use Mainsail, KlipperScreen, etc just fine. But as soon as I try and load any UI element that loads the webcam, the
wlan1interface gets setDOWNand networking breaks. Locally on KlipperScreen, Klipper continues to function just fine. So it's not crashing or anything. The networking just breaks.I poked through the code and I'm not sure where this could be happening, but I suspect it has to do with how ustreamer binds to a NIC. I don't see any configuration options documented that allow this to be configurable.
It does eventually recover and wlan0 comes back up. I'll share some STDOUT from ping showing this in the Additional information section below. But it takes minutes.
Here is a screen recording demos the bug occurring around 1:40: https://www.youtube.com/watch?v=WBQlUoP5Dfc
What did you expect to happen
Crowsnest to support multiple network interfaces, not default to the first one, and to work with any of them
How to reproduce
Run Klipper, Mainsail, Crowsnest on a device with multiple wireless NICs and a USB Webcam. Have the first NIC
DOWNand the second NICUP. Load the webcam and observe the second NIC be set toDOWN.Additional information
Crownest Config
Network Manager Connection Config
ip addr
Crowsnest Debug Log
STDOUT from Ping During Failure and Eventual Recovery