Internal LAN setup

Some users choose to keep their LinuxMCE "internal" LAN separate from their "external" home LAN.

In such a configuration, the "external" home LAN has a router which provides connection to the Internet through a DSL/Cable/satellite modem or T1 connection. That router has DHCP functions, NAT firewall, and port forwarding for the external LAN.

The LinuxMCE Core server will connect to that router through one NIC card.

To the "external: home LAN, the entire LinuxMCE "internal" LAN will appear to be a single device. The LinuxMCE Core will be the bridge, and the external LAN will only see the Core. The Core will have an IP address that is consistent with the "external home LAN. If the external home LAN uses the IP range 192.168.0.1 to 192.168.0.200, for example, the Core will have a single IP address in that range, such as 192.168.0.50, for example.

But the LinuxMCE "internal" LAN will use a different IP range. If you have used the default setup options, that IP range will be 192.168.80.1 to 192.168.80.xxx. The Core server will be 192.168.0.1 on the second NIC card.

That second NIC card should be connected to a second wireless router. The configuration of this second wireless router is important.

• Connect wirelessly to the second wireless router, from a wireless laptop, for example. Choose the "View wireless networks" option, for example, and connect ot your new router. Open a browser and enter the web-based configuration page of your new router. Often this is http://192.168.0.1 or http://192.168.1.1 or http://192.168.2.1, depending on your brand of router.

See your manufacturer's instructions for the default id and password for the router administration web page.

• There ought to be a "Basic setup" section. On it there should be an "Internet Connection type." This is the way the router will get an IP address from the Core server. You can leave this as DHCP or you can specify a Static IP. If you choose a static IP, you must set all the values. The static IP must be in the range 192.168.80.xxx (or whatever the IP range for the LinuxMCE LAN is). The gateway must be the Core server (e.g. 192.168.80.1) as is the DNS server.

Usually you can just leave this as DHCP and you will be ok.

• The next step is critical, however. You must disable the DHCP server settings in a section called "Network Address Server settings (DHCP)", or something very similar. You don't want the router to perform DHCP services. The Core will do that.

• Now you connect any LinuxMCE LAN devices to this router, either wired or wirelessly. (Note, however, that Media Directors should be only connected in a wired fashion if you intend to netboot. Netboot doesn't work wirelessly for most people.)

All devices connected to this router will be part of the "internal" LinuxMCE LAN, not the external home LAN.

• You should name this "internal" router uniquely, such as "LinuxMCE_AP" or something like that. That way, when you "View Available Wireless Networks" you can distinguish the wireless router used for LinuxMCE from the wireless router used for your external home LAN.

• Don't forget to establish a security (WEP/WPA,etc.) password for the "internal" wireless router. Otherwise, anyone could connect to your LinuxMCE LAN wirelessly and control your home for you.

• If you wish to use a device as part of the external LAN and not part of the internal LinuxMCE LAN, simply change which wireless router the device (e.g. a laptop) connects to.