I use Host networking as opposed to Bridge networking, so I didn't need to set up any forwards. Due to shortcomings of my UDM Pro's OS, I had to hook up the second LAN to another switchport to sit on the same VLAN as my TV for DLNA traffic (no IGMP Proxy in Unifi OS). On my DS918+ I deployed the Soerentsch Serviio image. Second issue: How to make the service to attach itself to the network ot create, so that in case of restart everything will boot properly without the need of any manual intervention?ĭo you have multiple docker containers set up from testing or prior migration? Are you using Host or Bridge network? So if anyone can help me a bit with the following to make the setup self-sufficient it would be nice:įirst issue: How to make the macvlan network ot get an IP from the router's DHCP with DNS? When attaching the service to the MacLan (the created macvlan network) i can see in the Serviio console > Network Settings that on eth0 i have the proper local IP assigned to the container ( in my case 192.168.1.149).Īfter setting the proper adapter (eth0) with the proper IP now Serviio advertizes itself properly in the network and all network devices (TV, Android phones, even Windows Media Player on my desktop) see the Serviio server and also can access it as any other DLNA server. If you don't specify a DNS then the movies/tv series is not being fetched from whereever it needs to fetch those. The other small change in the composer file is specifying the DNS, beause with this macvlan network the container is requesting an IP from the router, and it's not waiting for one to be asigned with DHCP, which means there is no DNS assigned also. Here it will be quite nice to have some help on how to automatically join the container/service to the network, because i haven't tested what will happen on restart. Now that i have the network i have to manually add the network to the created service, beause for some reason it does not attach on creation, even though it's set in the compose. This video was extremely helpful, because it's a little strange how to work with macvlan ( ) - first i have created the following config:Īfter that i have created the following network to be attached to the service: The MacLan network is newly created macvlan network, to expose the container to the lan network. Config/serviio/plugins:/opt/serviio/plugins Config/serviio/library:/opt/serviio/library It's not the ideal solution yet, because it requires some manual work on restart, but it's something. ![]() The service is only available inside the docker. Started experimenting with macvlan configuration, but so far haven't had any success. I have tried almost everything i saw with different network modes (bridge, host, etc.). The current setup is OMV5 (OpenMediaVault -> Debian) and serviio running in docker container. I have tried selecting each of those - no luck. Now i have the issue where i can not actually select my static ip, delegated by the router. When selectig the proper one - everything was fine. When i was having issues with this on my PC it was because i have selected the wrong ethernet device for serviio to use. The UDP port is mapped and used only by serviio - made sure of that. The issue is that they are not seeing the server. ![]() ![]() ![]() I am even seeing clients -> LG TV, windows media player from the other pc, VLC from android device etc. The library is up and running, detecting new files etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |