<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div lang="EN-US" link="#0563C1" vlink="#954F72"><div><br>
<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.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></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…<u></u><u></u></p>
<p class="MsoNormal"><a href="http://192.168.2.0/26" target="_blank">192.168.2.0/26</a> (Parents Network)<u></u><u></u></p>
<p class="MsoNormal"><a href="http://192.168.3.0/26" target="_blank">192.168.3.0/26</a> (Kids Network)<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></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.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">After using grep to look thru the entire file structure to locate where the backend setting was, I decided to install MySQL Workbench an found the backend setting in the SETTING Table in Mythconverg DB. And it appears that since there
is no Primary Key, MySQL Workbench can only open the DB in Read-Only. Meaning I cannot make changes to it.</p></div></div></blockquote><div><br>I think your over complicating this by trying to multi-home the server.<br><br>You have a layer 3 switch (which is basically a router)... just create a new network for the server and assign the server an IP in the new subnet. Then the clients would route to it like any other machine outside their subnet. If your worried about throughput using a single 100mb connection to the server, then use bond your nics using LACP (assuming your switch supports it) or whatever proprietary link aggregation protocol your switch supports.<br><br>If your server must retain it's IP's in the existing subnets, your could possibly VLAN trunk the port(s) and assign the IP's from each subnet as well. Then the server would have 3 IP's assigned to one NIC (or bonded pair), one in each subnet, and one in a separate network dedicated to just the server(s). Mythtv would use the new IP, but other services could listen on one of the other IP's... for example you have a webserver that should only be accessible by the 192.168.2.0 subnet.<br><br>There are a ton of ways to accomplish what you want... but the above is probably the ideal solution. You couldn't do it with a lesser switch, but since you have a layer 3 switch, you may as well use it!</div></div></div></div>