# Hardcoded IP in voxl-streamer

Source: https://forum.modalai.com/topic/3884/hardcoded-ip-in-voxl-streamer
Category: General Questions (https://forum.modalai.com/category/2/general-questions)
Posted: 2024-10-24 12:15:06 UTC by groupo
Replies: 7 · Views: 1119

## groupo · 2024-10-24 12:15:06 UTC

Was trying to debug some video streaming and noticed voxl-streamer providing the same output "stream available at rtsp://127.0.0.1" no matter what I set default_uri to, or with auto_ip true or false. I went to look at where that logic was in voxl-streamer and noticed it is [hardcoded](https://gitlab.com/voxl-public/voxl-sdk/services/voxl-streamer/-/blob/master/src/main.c?ref_type=heads#L695) Is there an easy way to change that and get a more accurate information? Or does ModalAI have to change, recompile, then push in a new SDK?

## Reply by Alex Kushleyev (ModalAI staff) · 2024-10-24 16:29:58 UTC

@groupo , you are correct, the printout is hardcoded, but the application will respond to the actual board ip, which you can get using `ifconfig` command.

I'll see if i can fix it so that `voxl-streamer` reports the actual ip instead of the `127.0.0.1` which is the address for the local (loopback) interface on the board (a virtual network for local networking within the board)

Alex

## Reply by groupo · 2024-10-24 17:31:47 UTC (in reply to Alex Kushleyev)

@Alex-Kushleyev The actual board may have many IPs, such as if wifi and modem are connected. It's my understanding it will use voxl-my-ip if auto_ip is True in mavcam-manager.conf, but if set to false it will select whatever default_uri is. I was trying to find a way to confirm that is in fact the the case. I did determine the issue was in VLC and solved it in another user's recent post. 

In that post I did ask how mavcam-manger and streamer are coupled. From the block diagram on the docs, they appeared to be decoupled but its clear streamer relies on things set in mavcam-manager

## Reply by tom (ModalAI staff) · 2024-10-24 19:03:15 UTC (in reply to groupo)

@groupo Yes you're correct

## Reply by groupo · 2024-10-25 12:20:14 UTC (in reply to tom)

@tom @Alex-Kushleyev thank you both. Hopefully there is a way to illustrate how mavcam manager, streamer, and camera server are all related. Maybe I am relying on the block diagram too heavily but it has been very confusing for me.

## Reply by groupo · 2024-10-25 12:26:42 UTC (in reply to groupo)

@Alex-Kushleyev or @tom 

What steps would I need to take if I wanted to make those changes instead of waiting for an SDK update? I don’t necessarily need the behavior now that I have confirmed everything is working. But there are a few things for my very specific use case that could eliminate some hoops I have to jump through on my system. As Tom and I have discussed before, we’ve had to muddle our way through a few issues that weren’t part of your majority of use cases. 

I assume this would involve building basically my own SDK (yours with very minor edits) then flashing it to the drone? Is that even possible?

## Reply by groupo · 2024-10-30 06:02:30 UTC (in reply to groupo)

@tom @Alex-Kushleyev ??

## Reply by Zachary Lowell 0 · 2024-10-30 14:43:21 UTC

@groupo yes all the code is open sourced for this exact purpose - if you wish to make updates, you can fork your own instance of the repository - make your edits, compile, flash the deb onto your voxl2 and then provided everythign works as expected you can make an MR on gitlab from your fork to the dev branch and one of us will review and test prior to adding into the next release.