Jawaad wrote:<br><br>You described your setup as having a mythbackend server that also happens to<br>be your router. Does it communicate with other MythTV equipment on the<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://192.168.0.0/24" target="_blank">
192.168.0.0/24</a> interface, the <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://192.168.1.0/24" target="_blank">192.168.1.0/24</a> interface, or both? Is this the<br>master backend? the only backend?
<br><br><br>It does communicate with the other mythfrontends via the <a href="http://192.168.0.0/24">192.168.0.0/24</a> interface. I used to have a setup where it communicated to frontends in both the <a href="http://192.168.1.0/24">
192.168.1.0/24</a> and <a href="http://192.168.0.0/24">192.168.0.0/24</a> networks. The server has three "legs", one in each network and therefore has three names corresponding to each "leg". This is the only backend. I used to have a master and a slave setup though but I decided to consolidate everything in one. (One PC to rule them all! ). It runs 24/7. It does all server duties: Mysql, Squid, DNS caching, IP Masquerade, Asterisk VOIP, Hotwayd, NTP, HTTPD, VPN, Nagios, SSH, vncserver , MythTV, FFserver, Qmail, Dovecot, Squirrelmail, Cups... Well, I'm just bragging now. Sorry.
<br><br><br>