No...you don't have to place your PC inside the LinuxMCE network and I most definitely wouldn't. I don't claim to know what I'm talking about all that well, but in my mind what you need to do is establish a static route for the information to go through. To do this, your outside and inside networks should ideally be on separate subnets and address spaces. For examples sake, lets make the external network use IPs in the 192.168.1.X range and be on the 255.255.255.0 subnet and lets mate the LinuxMCE internal network be on he 192.168.0.X address space and be on the 255.255.249.0 address space. Here's where it gets tricky and I have had problems in the past between various distros/devices/OS. You need to set up a static route that directs all traffic headed to ("destination") 192.168.1.0 through the external interface ("gateway") Try one of the three options:
- Use the IP address assigned to the Core's external NIC as the gateway
- Use 0.0.0.0 as the gateway
- Use "default" as the gateway
Make sure to set the subnet (or netmask) to 255.255.255.0 and select the correct interface. This tip comes from my experience with Linux in general and not just LinuxMCE although it should be equally applicable.
If there is no GUI to do this, try entering the following (adjust the address/device for your setup) into a console:
ip route add to 192.168.1.0 dev eth0 (might be 192.168.1.0/24)
Keep in mind that the preceding command will be erased when the system is rebooted. To make this permanent, you must edit the /etc/network/interfaces file and add:
post-up ip route add to 192.168.1.0 dev eth0 (might be 192.168.1.0/24)
Edit: Upon further research into the topic, it appears you may keep the subnet masks the same without any problems and it may be beneficial to do so as there are some weird calculations performed in binary to determine certain address information. Experiment with it and see what works.