@Zachary-Lowell-0 I'm on Docker 24.0.2
So I was reading through the kernel build guide, and I saw an example that enabled smsc95xx by modifying the m005x.cfg file (CONFIG_USB_NET_SMSC95XX=y).
From what I can tell by reading through the IPVLAN docs, it's much the same steps to enable it (CONFIG_IPVLAN=y or CONFIG_IPVLAN=m). So it looks like it should be safe? Is this still something you would advise against? Also, would there be any issues with running all of the build stuff on MacOS?
Hello,
I'm trying to set up a Docker network with an ipvlan driver. The network starts without issue, but when creating the container, I'm getting the following error:
Error response from daemon: failed to create the ipvlan port: operation not supported
Unfortunately, I haven't been able to find much about this error, so currently the only lead I have has to do with the Linux kernel version. The Docker docs says:
Kernel requirements:
IPvlan Linux kernel v4.2+ (support for earlier kernels exists but is buggy). To check your current kernel version, use uname -r
I see that my current version is 4.19.125. Is there a way to upgrade? I'm fairly new to Linux so reading through the VOXL2 Kernel Build Guide hasn't been very helpful to me.
Thanks!
Update: running
voxl2:/$ ip link add link eth0 name ipvlan-test type ipvlan
RTNETLINK answers: Operation not supported
It looks like I might be missing a module? Not sure there
@Eric-Katzfey There might be something about networking that I'm not understanding here.
voxl-streamer by default streams RTSP to <IP>:8900, so for me I can see the stream by going to rtsp://192.168.1.222:8900/live
Just changing the port to 9976 doesn't equate to udp @ 127.0.0.1:9976, does it?
@Moderator Am I able to specify the IP and port that the stream from voxl-streamer is sent to? Since the third-party software encodes and writes to UDP:127.0.0.1:9976, I'm wondering if it's possible to direct voxl-streamer straight there instead
Hello, I'm somewhat new to video streaming, networking, and Linux development. I'm working on a VOXL2 running voxl-suite 1.3.4~beta3. In addition, I have an M0173 breakout connected with two M0166 tracking and two M0161 Hires cameras. My current project will only use one of the Hires cameras. I've been able to successfully stream the Hires cam over RTSP using voxl-streamer as a sanity check.
However, my project involves third-party (whom I'm able to contact) software onboard that uses ffmpeg to encode and compress video from /dev/video0 and write it to UDP:127.0.0.1:9976. Is it possible for me to direct the Hires camera to video0 for the software to use? From what I've read, the camera can't be accessed directly via video0 (hence the use of voxl-camera-server). Are there any workarounds here?