<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<div style="color: black;">
<p style="margin: 0 0 1em 0; color: black; font-family: sans-serif;">On 13 August 2017 1:23:09 am Monkey Pet <monkeypet@gmail.com> wrote:</p>
<p style="margin: 0 0 1em 0; color: black; font-family: sans-serif;">> Trying to setup mythtv-backend in a docker container. However, running<br>
> into issues trying to get the networking setup correctly with the hdhomerun<br>
> tuner card. Anyone got this to work? Basically, i can't seem to get the<br>
> bridge working correctly, so my hdhomerun network tuner doesn't work. I<br>
> don't know enough about docker's internal networking scheme to figure it<br>
> out...<br>
><br>
><br>
> <a href="https://github.com/jgoerzen/docker-mythtv">https://github.com/jgoerzen/docker-mythtv</a><br>
><br>
> Author noted this:<br>
> (pasted from his site above)<br>
><br>
> Also, if you use a capture device like the HDHomeRun which communicates<br>
> back to MythTV via random UDP ports, it can be just about impossible to<br>
> make things work with the standard docker port forwarding.<br>
><br>
> However, there are some workarounds.<br>
><br>
> You can:<br>
><br>
> - Use NAT reflection on your firewall to forward packets back in to your<br>
> network.<br>
> - Bridge your Docker containers to the network<br>
> <<a href="https://developer.ibm.com/recipes/tutorials/bridge-the-docker-containers-to-external-network/">https://developer.ibm.com/recipes/tutorials/bridge-the-docker-containers-to-external-network/</a>><br>
> - An example: docker network create --driver=bridge --ip-range=<br>
> 192.168.0.192/29 --subnet=192.168.0.0/24 --aux-address<br>
> "DefaultGatewayIPv4=192.168.0.1" -o<br>
> "com.docker.network.bridge.name=brlan1"<br>
> brlan1<br>
> - After that, you can add network=brlan1 --ip=192.168.0.193 do<br>
> your docker<br>
> run, and you do not need any -pbecause it will be directly accessible<br>
> on the new IP.<br>
> - Add egress iptables rules to your frontends<br>
> - You can set the BackendServerIP and MasterServerIP to the "visible" IP<br>
> of the backend (will probably have to do this via mysql). mythbackend will<br>
> fail to bind to a visible IP, but a userland redirector like redir may<br>
> do the trick.<br>
><br>
> I tried adding -O BackendServerIP=blah -O MasterServerIP=blah to my<br>
> mythfrontend command line. That let it boot, but wasn't sufficient for<br>
> streaming.<br>
><br>
><br>
><br>
> ----------<br>
> _______________________________________________<br>
</p>
<p style="margin: 0 0 1em 0; color: black;">In my mind a bridge network would be the best place to start. (as others have said be aware of what that means for your network security etc).
</p>
<p style="margin: 0 0 1em 0; color: black;">How are you starting your container currently?
</p>
</div>
</body>
</html>