Network Setup - Revision history

Mcefan at 11:35, 8 October 2012

2012-10-08T11:35:31Z

←Older revision		Revision as of 11:35, 8 October 2012
Line 1:		Line 1:
	{{versioninfo}}		{{versioninfo}}
	[[Category:Networking\|*Setup]]		[[Category:Networking\|* Setup]]
	[[Category:Tutorials]]		[[Category:Tutorials]]
	[[Category:Networking Setups]]		[[Category:Networking Setups]]

Mcefan at 11:32, 8 October 2012

2012-10-08T11:32:52Z

←Older revision		Revision as of 11:32, 8 October 2012
Line 1:		Line 1:
	{{versioninfo}}		{{versioninfo}}
	[[Category:Networking]]		[[Category:Networking\|*Setup]]
	[[Category:Tutorials]]		[[Category:Tutorials]]
	[[Category:Networking Setups]]		[[Category:Networking Setups]]

Wierdbeard65 at 08:46, 5 May 2010

2010-05-05T08:46:32Z

←Older revision		Revision as of 08:46, 5 May 2010
Line 1:		Line 1:
			{{versioninfo}}
	[[Category:Networking]]		[[Category:Networking]]
	[[Category:Tutorials]]		[[Category:Tutorials]]

Chris Caven: /* Fully Configured Smart Home Solution */

2010-04-21T18:11:51Z

Fully Configured Smart Home Solution

←Older revision		Revision as of 18:11, 21 April 2010
Line 30:		Line 30:
	[[Image:Complete.PNG]]		[[Image:Complete.PNG]]

	In the above diagram you can see the same LinuxMCE enabled network after it has matured - the owner has gone nuts, adding stuff! You may only wish to use LinuxMCE for media playback, in which case you will be more interested in the "MD"s in the diagram. However, you can continue expanding it at will into its designed functionality by ~~added~~ telephones, security systems, home automation networks (lights, environmental controls, irrigation systems, etc)		In the above diagram, you can see the same LinuxMCE-enabled network after it has matured - the owner has gone nuts, adding stuff! You may only wish to use LinuxMCE for media playback, in which case you will be more interested in the "MD"s in the diagram. However, you can continue expanding it at will into its designed functionality by adding telephones, security systems, home automation networks (lights, environmental controls, irrigation systems, etc).

	It should be understood that this article is attempting to show that in the simplest implementation, LinuxMCE does not require large, wholesale changes to your existing home network - in fact, in many cases it requires no change at all, just an extra Cat5e/6 patch cable. This does not mean that this is the only, recommended or best network design. It is a minimal implementation that satisfies all of the requirements, and is here to show how simple LinuxMCE can actually be. There are many other designs that are extensions of this one, or completely different that also work and may be chosen based on more sophisticated requirements you may have, but this is a starting point.		It should be understood that this article is attempting to show that in the simplest implementation, LinuxMCE does not require large, wholesale changes to your existing home network - in fact, in many cases it requires no change at all, just an extra Cat5e/6 patch cable. This does not mean that this is the only, recommended or best network design. It is a minimal implementation that satisfies all of the requirements and is here to show how simple LinuxMCE can actually be. There are many other designs that are extensions of this one, or completely different, that also work and may be chosen based on more sophisticated requirements you may have, but this is a starting point.

Chris Caven at 13:05, 21 April 2010

2010-04-21T13:05:06Z

←Older revision		Revision as of 13:05, 21 April 2010
Line 22:		Line 22:
	In this network, your broadband router can continue providing dynamic IP addresses to the "External" NIC of the core - however, there is nothing stopping you fixing this IP address if you prefer. In which case your broadband router's DHCP server is no longer needed. For the Internal or LinuxMCE network, the Core now provides DHCP services to all devices. IMPORTANT: LinuxMCE needs to be the (only) DHCP server for the Internal network because it provides much more than just IP addresses to these devices. So it is important that you allow it to do this, and leave all your internal devices set to acquire their IP address via DHCP so that LinuxMCE works correctly. This is the only supported configuration - however, as you can see, the impact is either negligible or non-existent.		In this network, your broadband router can continue providing dynamic IP addresses to the "External" NIC of the core - however, there is nothing stopping you fixing this IP address if you prefer. In which case your broadband router's DHCP server is no longer needed. For the Internal or LinuxMCE network, the Core now provides DHCP services to all devices. IMPORTANT: LinuxMCE needs to be the (only) DHCP server for the Internal network because it provides much more than just IP addresses to these devices. So it is important that you allow it to do this, and leave all your internal devices set to acquire their IP address via DHCP so that LinuxMCE works correctly. This is the only supported configuration - however, as you can see, the impact is either negligible or non-existent.

	It is also well worth noting that your PCs will be detected as "file servers" by ~~LMCE~~, and when the DHCP server assigns an IP address this is effectively permanent/static. You do not need to worry about the IP address changing all the time, it doesn't! This information will be of particular interest to those who want to NAT or port forward services from the Internet to specific PCs, such as Remote Desktop sessions and Bit Torrent clients.		It is also well worth noting that your PCs will be detected as "file servers" by LinuxMCE, and when the DHCP server assigns an IP address this is effectively permanent/static. You do not need to worry about the IP address changing all the time, it doesn't! This information will be of particular interest to those who want to NAT or port forward services from the Internet to specific PCs, such as Remote Desktop sessions and Bit Torrent clients.

	In this page, a reference to the "Core server" can either be a dedicated Core or a Hybrid - a core, plus Media Director functionality - either way, it doesn't effect the network topology or any other details described here. The important point is that a "Core server" at the least contains the LinuxMCE core services, and this is the functionality that needs to be the gateway between the Internal network and the External network.		In this page, a reference to the "Core server" can either be a dedicated Core or a Hybrid - a core, plus Media Director functionality - either way, it doesn't effect the network topology or any other details described here. The important point is that a "Core server" at the least contains the LinuxMCE core services, and this is the functionality that needs to be the gateway between the Internal network and the External network.
Line 32:		Line 32:
	In the above diagram you can see the same LinuxMCE enabled network after it has matured - the owner has gone nuts, adding stuff! You may only wish to use LinuxMCE for media playback, in which case you will be more interested in the "MD"s in the diagram. However, you can continue expanding it at will into its designed functionality by added telephones, security systems, home automation networks (lights, environmental controls, irrigation systems, etc)		In the above diagram you can see the same LinuxMCE enabled network after it has matured - the owner has gone nuts, adding stuff! You may only wish to use LinuxMCE for media playback, in which case you will be more interested in the "MD"s in the diagram. However, you can continue expanding it at will into its designed functionality by added telephones, security systems, home automation networks (lights, environmental controls, irrigation systems, etc)

	It should be understood that this article is attempting to show that in the simplest implementation, LinuxMCE does not require large, wholesale changes to your existing home network - in fact, in many cases it requires no change at all, just an extra Cat5e/6 patch cable. This does not mean that this is the only, recommended or best network design. It is a minimal implementation that satisfies all of the requirements, and is here to show how simple ~~LMCE~~ can actually be. There are many other designs that are extensions of this one, or completely different that also work and may be chosen based on more sophisticated requirements you may have, but this is a starting point.		It should be understood that this article is attempting to show that in the simplest implementation, LinuxMCE does not require large, wholesale changes to your existing home network - in fact, in many cases it requires no change at all, just an extra Cat5e/6 patch cable. This does not mean that this is the only, recommended or best network design. It is a minimal implementation that satisfies all of the requirements, and is here to show how simple LinuxMCE can actually be. There are many other designs that are extensions of this one, or completely different that also work and may be chosen based on more sophisticated requirements you may have, but this is a starting point.

Ray N at 03:07, 11 August 2009

2009-08-11T03:07:57Z

←Older revision		Revision as of 03:07, 11 August 2009
Line 1:		Line 1:
	~~[[Category:Hardware]]~~
	[[Category:Networking]]		[[Category:Networking]]
	[[Category:Tutorials]]		[[Category:Tutorials]]

Colinjones: /* Network After LinuxMCE is Installed */ static IP info

2009-03-05T21:29:55Z

Network After LinuxMCE is Installed: static IP info

←Older revision		Revision as of 21:29, 5 March 2009
Line 22:		Line 22:

	In this network, your broadband router can continue providing dynamic IP addresses to the "External" NIC of the core - however, there is nothing stopping you fixing this IP address if you prefer. In which case your broadband router's DHCP server is no longer needed. For the Internal or LinuxMCE network, the Core now provides DHCP services to all devices. IMPORTANT: LinuxMCE needs to be the (only) DHCP server for the Internal network because it provides much more than just IP addresses to these devices. So it is important that you allow it to do this, and leave all your internal devices set to acquire their IP address via DHCP so that LinuxMCE works correctly. This is the only supported configuration - however, as you can see, the impact is either negligible or non-existent.		In this network, your broadband router can continue providing dynamic IP addresses to the "External" NIC of the core - however, there is nothing stopping you fixing this IP address if you prefer. In which case your broadband router's DHCP server is no longer needed. For the Internal or LinuxMCE network, the Core now provides DHCP services to all devices. IMPORTANT: LinuxMCE needs to be the (only) DHCP server for the Internal network because it provides much more than just IP addresses to these devices. So it is important that you allow it to do this, and leave all your internal devices set to acquire their IP address via DHCP so that LinuxMCE works correctly. This is the only supported configuration - however, as you can see, the impact is either negligible or non-existent.

			It is also well worth noting that your PCs will be detected as "file servers" by LMCE, and when the DHCP server assigns an IP address this is effectively permanent/static. You do not need to worry about the IP address changing all the time, it doesn't! This information will be of particular interest to those who want to NAT or port forward services from the Internet to specific PCs, such as Remote Desktop sessions and Bit Torrent clients.

	In this page, a reference to the "Core server" can either be a dedicated Core or a Hybrid - a core, plus Media Director functionality - either way, it doesn't effect the network topology or any other details described here. The important point is that a "Core server" at the least contains the LinuxMCE core services, and this is the functionality that needs to be the gateway between the Internal network and the External network.		In this page, a reference to the "Core server" can either be a dedicated Core or a Hybrid - a core, plus Media Director functionality - either way, it doesn't effect the network topology or any other details described here. The important point is that a "Core server" at the least contains the LinuxMCE core services, and this is the functionality that needs to be the gateway between the Internal network and the External network.

Langstonius at 21:02, 27 February 2009

2009-02-27T21:02:44Z

←Older revision		Revision as of 21:02, 27 February 2009
Line 2:		Line 2:
	[[Category:Networking]]		[[Category:Networking]]
	[[Category:Tutorials]]		[[Category:Tutorials]]
			[[Category:Networking Setups]]
	=Overview=		=Overview=

Colinjones: /* Fully Configured Smart Home Solution */

2009-02-25T22:03:02Z

Fully Configured Smart Home Solution

←Older revision		Revision as of 22:03, 25 February 2009
Line 30:		Line 30:

	In the above diagram you can see the same LinuxMCE enabled network after it has matured - the owner has gone nuts, adding stuff! You may only wish to use LinuxMCE for media playback, in which case you will be more interested in the "MD"s in the diagram. However, you can continue expanding it at will into its designed functionality by added telephones, security systems, home automation networks (lights, environmental controls, irrigation systems, etc)		In the above diagram you can see the same LinuxMCE enabled network after it has matured - the owner has gone nuts, adding stuff! You may only wish to use LinuxMCE for media playback, in which case you will be more interested in the "MD"s in the diagram. However, you can continue expanding it at will into its designed functionality by added telephones, security systems, home automation networks (lights, environmental controls, irrigation systems, etc)

			It should be understood that this article is attempting to show that in the simplest implementation, LinuxMCE does not require large, wholesale changes to your existing home network - in fact, in many cases it requires no change at all, just an extra Cat5e/6 patch cable. This does not mean that this is the only, recommended or best network design. It is a minimal implementation that satisfies all of the requirements, and is here to show how simple LMCE can actually be. There are many other designs that are extensions of this one, or completely different that also work and may be chosen based on more sophisticated requirements you may have, but this is a starting point.

Colinjones: /* Network After LinuxMCE is Installed */

2009-02-25T06:56:20Z

Network After LinuxMCE is Installed

←Older revision		Revision as of 06:56, 25 February 2009
Line 23:		Line 23:
	In this network, your broadband router can continue providing dynamic IP addresses to the "External" NIC of the core - however, there is nothing stopping you fixing this IP address if you prefer. In which case your broadband router's DHCP server is no longer needed. For the Internal or LinuxMCE network, the Core now provides DHCP services to all devices. IMPORTANT: LinuxMCE needs to be the (only) DHCP server for the Internal network because it provides much more than just IP addresses to these devices. So it is important that you allow it to do this, and leave all your internal devices set to acquire their IP address via DHCP so that LinuxMCE works correctly. This is the only supported configuration - however, as you can see, the impact is either negligible or non-existent.		In this network, your broadband router can continue providing dynamic IP addresses to the "External" NIC of the core - however, there is nothing stopping you fixing this IP address if you prefer. In which case your broadband router's DHCP server is no longer needed. For the Internal or LinuxMCE network, the Core now provides DHCP services to all devices. IMPORTANT: LinuxMCE needs to be the (only) DHCP server for the Internal network because it provides much more than just IP addresses to these devices. So it is important that you allow it to do this, and leave all your internal devices set to acquire their IP address via DHCP so that LinuxMCE works correctly. This is the only supported configuration - however, as you can see, the impact is either negligible or non-existent.

			In this page, a reference to the "Core server" can either be a dedicated Core or a Hybrid - a core, plus Media Director functionality - either way, it doesn't effect the network topology or any other details described here. The important point is that a "Core server" at the least contains the LinuxMCE core services, and this is the functionality that needs to be the gateway between the Internal network and the External network.

	=Fully Configured Smart Home Solution=		=Fully Configured Smart Home Solution=