[mythtv-users] MythTV needs to listen on 2 ports

[Raymond Wagner]

On 10/30/2014 9:06 AM, John Moore (Compucom Systems Inc) wrote:
>
> Morning,
>
> I am a new user to the is group.  And ran into a brick wall trying to 
> understand an use MythTV the way its intended in my network.  Which I 
> will admit is a bit complex.
>
> I am running a MythBuntu server (ver 14.04.1) running MythTV 0.27.  
> This server has 2 network cards on 2 different networks with static 
> IPs set...
>
> 192.168.2.0/26 (Parents Network)
>
> 192.168.3.0/26 (Kids Network)
>
> What I am trying to find out is if it's possible for the MythTV 
> backend service to listen on more than 1 port.  Depending on which 
> network I have it configured to listen too, will depend on which 
> clients can connect.  Not just the SQL DB.  But the service which uses 
> ports 6544 & 6543 that the clients connect to.
>

MythTV listens on multiple ports for various services, but it only 
listens on one address (plus 127.0.0.1).  The way MythTV's networking 
has always been set up, it stores a single IP address for the database, 
queries the database for the backend's single address, and then connects 
to that single address.

MythTV previously listened on all interfaces, however during the 
addition of support for IPv6, stock network settings on certain distros 
meant that listening on all interfaces meant only listening on IPv6 
addresses on all interfaces.  The various listen sockets were changed to 
only listen on discrete addresses, and because of the aforementioned way 
backend discovery happens, this did not change behavior of the frontend 
connecting to the backend (although there were some issues with other 
non-MythTV interfaces).  There are plans to move backend discovery 
independent of the database, and allow the user to select or the backend 
to auto-select multiple addresses to listen on, but this has not yet 
been implemented.

That said, I don't see why this is a problem in your specific 
situation.  If you're trying to access a machine outside your local 
subnet, you look in your routing table for your default gateway or your 
custom gateway defined for that address or range, route your packets 
through that gateway, and let that gateway take care of getting your 
packets to their final destination.  It sounds like your issues will be 
solved merely by implementing sensible routing between the two subnets, 
and then optionally putting in some firewall rules on that gateway to 
limit traffic to MythTV data only.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20141031/7fe1d81e/attachment.html>