<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 10/30/2014 9:06 AM, John Moore
(Compucom Systems Inc) wrote:<br>
</div>
<blockquote
cite="mid:a5d0330bcf38457d848012d8176a8235@BN1PR03MB186.namprd03.prod.outlook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:#0563C1;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:#954F72;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Morning,<o:p></o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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…<o:p></o:p></p>
<p class="MsoNormal">192.168.2.0/26 (Parents Network)<o:p></o:p></p>
<p class="MsoNormal">192.168.3.0/26 (Kids Network)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.</p>
</div>
</blockquote>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
</body>
</html>