VOXL2 VOXL-STREAMER
-
Hi,
I just reflashed a VOXL2 with the 1.5.5 firmware. So far everything is running as it should however, for some reason VOXL-STREAMER will only bind to the Loopback adapter and not WLAN0. So the RTSP address is 127.0.0.1 which won't answer because its not included in the routing table. My route table looks like this:
voxl2:/etc/modalai$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.12.1 0.0.0.0 UG 0 0 0 wlan0 0.0.0.0 192.168.12.1 0.0.0.0 UG 310 0 0 wlan0 192.168.12.0 0.0.0.0 255.255.255.0 U 310 0 0 wlan0I also have no idea how it got this way... I just used the voxl-wifi station command to setup wlan0. Either way, the correct address for voxl-streamer to listen on would be 192.168.12.106, however I see no location where to set the IP for voxl-streamer, only the port.
Thanks,
Jason
-
Hi,
I just reflashed a VOXL2 with the 1.5.5 firmware. So far everything is running as it should however, for some reason VOXL-STREAMER will only bind to the Loopback adapter and not WLAN0. So the RTSP address is 127.0.0.1 which won't answer because its not included in the routing table. My route table looks like this:
voxl2:/etc/modalai$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.12.1 0.0.0.0 UG 0 0 0 wlan0 0.0.0.0 192.168.12.1 0.0.0.0 UG 310 0 0 wlan0 192.168.12.0 0.0.0.0 255.255.255.0 U 310 0 0 wlan0I also have no idea how it got this way... I just used the voxl-wifi station command to setup wlan0. Either way, the correct address for voxl-streamer to listen on would be 192.168.12.106, however I see no location where to set the IP for voxl-streamer, only the port.
Thanks,
Jason
@Mastermind Did you try connecting to 192.168.12.106? It should work.
-
@Mastermind Did you try connecting to 192.168.12.106? It should work.
@Eric-Katzfey Thanks yes I did, however I get no response
In the previous firmware, voxl-streamer would output to rtsp://192.168.12.106:8900/live and not the loopback interface. I am...confuddled. It should work... but it doesn't.
-
@Eric-Katzfey Thanks yes I did, however I get no response
In the previous firmware, voxl-streamer would output to rtsp://192.168.12.106:8900/live and not the loopback interface. I am...confuddled. It should work... but it doesn't.
@Mastermind Did you first verify connectivity to that address with ping, etc.? If you start voxl-streamer from the command line instead of systemd do you see any error messages or connection attempts?
-
@Mastermind Did you first verify connectivity to that address with ping, etc.? If you start voxl-streamer from the command line instead of systemd do you see any error messages or connection attempts?
@Eric-Katzfey Yep, checked all the networking. Routing works, everything seems ok from what I can tell, its a vanilla firmware. Only been running a week since I flashed it. Let me try that manual run right now and post the results here...
voxl2:~$ sudo systemctl status voxl-streamer ● voxl-streamer.service - voxl-streamer Loaded: loaded (/usr/bin/voxl-streamer; enabled; vendor preset: enabled) Active: inactive (dead) since Wed 2023-07-12 01:43:58 UTC; 19s ago Process: 1791 ExecStart=/usr/bin/voxl-streamer (code=exited, status=0/SUCCESS) Main PID: 1791 (code=exited, status=0/SUCCESS) Jul 11 16:31:19 m0054 systemd[1]: Starting voxl-streamer... Jul 11 16:31:24 m0054 systemd[1]: Started voxl-streamer. Jul 11 16:31:25 m0054 voxl-streamer[1791]: Camera server Connected Jul 11 16:31:25 m0054 voxl-streamer[1791]: Stream available at rtsp://127.0.0.1:8900/live Jul 12 01:43:57 m0054 voxl-streamer[1791]: received SIGTERM Jul 12 01:43:57 m0054 systemd[1]: Stopping voxl-streamer... Jul 12 01:43:58 m0054 voxl-streamer[1791]: Trying to stop loop Jul 12 01:43:58 m0054 voxl-streamer[1791]: Exited Cleanly Jul 12 01:43:58 m0054 systemd[1]: Stopped voxl-streamer.And how the manual run:
voxl2:~$ voxl-streamer
Camera server Connected
Stream available at rtsp://127.0.0.1:8900/liveStill wants to go to the loopback adapter and not wlan0. This is the first time I have experienced this, all my previous uses of voxl-streamer, it has always used the active connection (wwan0 or wlan0) whichever was active, which was kinda nice. We did write a small script to watch when we switch networks and then restart voxl-streamer to ensure it was running on the right IP.
Netstat -a produces this:
tcp 0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8900 0.0.0.0:* LISTENIronically, this is correct and the server is listening on anything at port 8900... but I tried 3 different media players and none of them can connect, they just get an error 503. Two connection were over a VPN, and one was on the same lan segment as the VOXL2. The only thing that is different here is that I do not have voxl-vision-px4 enabled... but I cannot see how that would matter.
The the record voxl-portal works fine and the video image works great.
Let me know if you have any thoughts.
-
@Eric-Katzfey Yep, checked all the networking. Routing works, everything seems ok from what I can tell, its a vanilla firmware. Only been running a week since I flashed it. Let me try that manual run right now and post the results here...
voxl2:~$ sudo systemctl status voxl-streamer ● voxl-streamer.service - voxl-streamer Loaded: loaded (/usr/bin/voxl-streamer; enabled; vendor preset: enabled) Active: inactive (dead) since Wed 2023-07-12 01:43:58 UTC; 19s ago Process: 1791 ExecStart=/usr/bin/voxl-streamer (code=exited, status=0/SUCCESS) Main PID: 1791 (code=exited, status=0/SUCCESS) Jul 11 16:31:19 m0054 systemd[1]: Starting voxl-streamer... Jul 11 16:31:24 m0054 systemd[1]: Started voxl-streamer. Jul 11 16:31:25 m0054 voxl-streamer[1791]: Camera server Connected Jul 11 16:31:25 m0054 voxl-streamer[1791]: Stream available at rtsp://127.0.0.1:8900/live Jul 12 01:43:57 m0054 voxl-streamer[1791]: received SIGTERM Jul 12 01:43:57 m0054 systemd[1]: Stopping voxl-streamer... Jul 12 01:43:58 m0054 voxl-streamer[1791]: Trying to stop loop Jul 12 01:43:58 m0054 voxl-streamer[1791]: Exited Cleanly Jul 12 01:43:58 m0054 systemd[1]: Stopped voxl-streamer.And how the manual run:
voxl2:~$ voxl-streamer
Camera server Connected
Stream available at rtsp://127.0.0.1:8900/liveStill wants to go to the loopback adapter and not wlan0. This is the first time I have experienced this, all my previous uses of voxl-streamer, it has always used the active connection (wwan0 or wlan0) whichever was active, which was kinda nice. We did write a small script to watch when we switch networks and then restart voxl-streamer to ensure it was running on the right IP.
Netstat -a produces this:
tcp 0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8900 0.0.0.0:* LISTENIronically, this is correct and the server is listening on anything at port 8900... but I tried 3 different media players and none of them can connect, they just get an error 503. Two connection were over a VPN, and one was on the same lan segment as the VOXL2. The only thing that is different here is that I do not have voxl-vision-px4 enabled... but I cannot see how that would matter.
The the record voxl-portal works fine and the video image works great.
Let me know if you have any thoughts.
@Mastermind SOLVED
Ok, I don't know WHY this solved the problem, but here is what I did:
Stopped voxl-camera-server
stopped voxl-streamer
Started voxl-camera-server
started voxl-vision-px4
started voxl-streamer (it still shows the 127.0.0.1 loopback interface)Started up VLC and boom... nice happy 30fps video. I will be doing a bunch of testing so if I can replicate this problem again I will let you know. Restarted the voxl about 20x today and tried everything else I could think of, but the above seems to have done something to make it work.
-
@Mastermind SOLVED
Ok, I don't know WHY this solved the problem, but here is what I did:
Stopped voxl-camera-server
stopped voxl-streamer
Started voxl-camera-server
started voxl-vision-px4
started voxl-streamer (it still shows the 127.0.0.1 loopback interface)Started up VLC and boom... nice happy 30fps video. I will be doing a bunch of testing so if I can replicate this problem again I will let you know. Restarted the voxl about 20x today and tried everything else I could think of, but the above seems to have done something to make it work.
@Mastermind Okay, interesting. Let us know if you figure out the root cause. Thanks!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login