[mythtv-users] Multiple boxes on different networks

[Chris Isip]

It shouldn't be an issue running mythfrontends and mythbackends in different
networks as long as these boxes can see each other.

My setup is different from yours though. I have a mythbackend server that is
also a router (three network interfaces).  One (eth1) connects to the
internet with dhcp assigned by ISP, one (eth0) connects to
192.168.1.0/24network and the other (eth2) connects to
192.168.0.0/24 network.   I dont have to do any port forwarding at all.

On 11/5/06, Jawaad Ahmad <jawaad.ahmad at gmail.com> wrote:
>
> Hi,
>
> I haven't found too much information on running a frontend on a different
> box from a backend, let alone having the two run on different networks.
>
> Before I post details on my current setup, I was wondering if anyone could
> point me toward resources describing how to set up frontends and backends
> on
> different boxes, where the boxes are on different networks.
>
> I currently have a stand-alone box running Ubuntu's Breezy Badger with a
> Hauppauge PVR-150 tuner, and MythTV 0.20. This box works well since I
> installed 0.20 a couple weeks ago.
>
> In the past, I have tried running mythfrontend and mythbackend on a
> similarly-configured box and had them able to communicate with one
> another.
> They could share tuners and all when I set the IP addresses properly under
> mythtv-setup's General page.
>
> The difference now is that the two boxes are on a separate network. For
> example, in the past, one box might have had an IP address of 192.168.0.2
> while the other might have an IP address of 192.168.0.3, both connected by
> a
> router with IP address 192.168.0.1.
>
>             [ ] 192.168.0.1
>              |
>     +--------+---------+
>     |                  |
>    [ ] 192.168.0.2    [ ] 192.168.0.3
>
> Now, I still have the 192.168.0.1 router with the 192.168.0.2 PC. The
> 192.168.0.1 router is now connected to a 192.168.1.1 router, and the other
> PC has an IP address of 192.168.1.2.
>
>             [ ] 192.168.1.1
>              |
>     +--------+---------+
>     |                  |  192.168.1.3
>    [ ] 192.168.1.2    [ ] 192.168.0.1
>                        |
>               +--------+---------+
>               |                  |
>              [ ]                [ ] 192.168.0.2
>
> I have already forwarded the MySQL port and the mythbackend ports (3306,
> 6543, and 6544) on the router [192.168.0.1] to forward to 192.168.0.2. At
> no
> point should there be any communication past router [192.168.1.1].
>
> In addition, I ran mythtv-setup on 192.168.0.2 and set both IP addresses
> (host IP and master backend IP) to 192.168.1.3. If I did not do this, host
> 192.168.1.2 would try to access 192.168.0.2 using the "192.168.0.2" IP
> address, which caused problems. Changing these IP addresses did not seem
> to
> break anything on 192.168.0.2.
>
> As I stated before, right now, I'm only looking for
> pointers/advice/gotchas
> that someone knows about. If anyone is familiar with this and is
> interested
> in more information, I can try to provide detailed messages.
>
> Thanks in advance for any help you can offer.
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20061105/d079e5ae/attachment-0001.htm