DHCP Plug and Play - Revision history

Mcefan at 21:56, 19 October 2012

2012-10-19T21:56:16Z

←Older revision		Revision as of 21:56, 19 October 2012
Line 1:		Line 1:
	[[category: ~~tutorials~~]]		[[category:Networking]]


	<p>LinuxMCE allows a user to plug in any type of device and automatically configures it and lets the user start using it right away without doing anything. The way this is accomplished is with an extension to the DHCP server. When a new device is plugged into the network and requests an IP address, this program connects to a central database to do a lookup of the device's unique MAC address to see what type of device it is. The database defines all the configuration data the device needs to run, and references the software drivers needed. This program then downloads and installs any needed software, adds configuration pages for the device to the user's [[LinuxMCE Admin Website]], and adds the device in the user's local database.</p>		<p>LinuxMCE allows a user to plug in any type of device and automatically configures it and lets the user start using it right away without doing anything. The way this is accomplished is with an extension to the DHCP server. When a new device is plugged into the network and requests an IP address, this program connects to a central database to do a lookup of the device's unique MAC address to see what type of device it is. The database defines all the configuration data the device needs to run, and references the software drivers needed. This program then downloads and installs any needed software, adds configuration pages for the device to the user's [[LinuxMCE Admin Website]], and adds the device in the user's local database.</p>

Zaerc: cleaned up the mess

2008-08-28T23:12:09Z

cleaned up the mess

←Older revision		Revision as of 23:12, 28 August 2008
Line 5:		Line 5:
	LinuxMCE recommends its core server have 2 ethernet ports, connecting one to an existing LAN (that routes to the Internet), and the other to a LAN segment on which sit all devices that LMCE will serve. That recommended setup runs a DHCP server (DHCPd) on LMCE to assign IP numbers and other network configs to devices on the "inside" LAN served by LMCE. LMCE runs a DHCP client on its "outside" LAN interface to get its IP# (and any other configs the existing LAN might assign) on that outside LAN. LMCE than routes inside LAN traffic to the outside LAN, including to any router/gateway on the outside LAN, while running a firewall that protects devices on the inside from activity on the outside.		LinuxMCE recommends its core server have 2 ethernet ports, connecting one to an existing LAN (that routes to the Internet), and the other to a LAN segment on which sit all devices that LMCE will serve. That recommended setup runs a DHCP server (DHCPd) on LMCE to assign IP numbers and other network configs to devices on the "inside" LAN served by LMCE. LMCE runs a DHCP client on its "outside" LAN interface to get its IP# (and any other configs the existing LAN might assign) on that outside LAN. LMCE than routes inside LAN traffic to the outside LAN, including to any router/gateway on the outside LAN, while running a firewall that protects devices on the inside from activity on the outside.

	However, it is possible to run LMCE on a host with a single ethernet port. There is some complexity in the configuration, the solution is not as fully automated and robust as is the recommended 2 ethernet version~~, and the omission of the LMCE firewall reduces the overall security of the installation~~. However, it is possible to do. These are instructions, including switching the LAN from an existing DHCP server to using the LMCE DHCPd instead~~. AFAICT, this technique doesn't leave any wrong configurations anywhere inside either LMCE's complex interdependencies or the remnants of the previously existing DHCP system~~.		However, it is possible to run LMCE on a host with a single ethernet port. There is some complexity in the configuration, the solution is not as fully automated and robust as is the recommended 2 ethernet version. However, it is possible to do. These are instructions, including switching the LAN from an existing DHCP server to using the LMCE DHCPd instead.

	#In existing router/gateway		*In existing router/gateway
	##Disable DHCPd		#Disable DHCPd
	##Assign LAN IP# on desired subnet (eg 192.168.0.1 )		#Assign LAN IP# on desired subnet (eg 192.168.0.1)
	##Ensure router/gateway is configured to route properly between the newly specified subnet and the other network		#Ensure router/gateway is configured to route properly between the newly specified subnet and the other network
	~~# In LMCE Admin site:~~
	~~##Homepage -> Advanced -> Network -> Network Settings~~
	~~##Change all 192.168.80.x IP#s to desired subnet (eg. 192.168.0.x )~~
	~~##Set both NICs to the same IP# (and proper subnet info)~~
	~~##Reload DCERouter~~
	~~##Check Homepage -> Advanced -> Network -> Network Settings to be sure settings were properly retained~~
	~~#/etc/dhcp3/dhcpd.conf :~~
	~~##Ensure "option routers" parameter(s) is the correct IP#(s) of the existing router(s)~~
	~~##Exclude router/gateway IP# from allocatable ranges~~
	~~##Change "host px[1,2]" lines from 192.168.80.x IP#s to desired subnet IP#s (eg. 192.168.0.253 )~~
	~~##/etc/init.d/dhcp3-server restart~~
	~~##Force a LAN host to reset its network configs by DHCP, then test pinging across the router~~
	~~# Force each host on the LAN to reread its network configs by DHCP (eg. run its DHCP client or reboot if its DHCP client runs at startup).~~

	~~Note that the dhcpd.conf file regenerated by the~~ LMCE Admin site's Network Settings ~~form has a bug which doesn't change all~~ the IP#~~s properly. There might be other bugs, so check~~ the ~~whole file~~ to be ~~sure it's correct~~.		*In LMCE Admin site:
			#Homepage -> Advanced -> Network -> Network Settings
			#Make sure "Enable DHCP server" is checked, leave the ranges at their defaults, or at least in the 192.168.80.X range.
			#Configure the "External network card" staticly to be on the same subnet as the router (eg 192.168.0.X).
			#Leave the "Internal network card" setting at their defaults (eg 192.168.80.1).
			#Reoload the router

	~~==Caveat==~~		*Everything else on the network
	~~This technique leaves a problem in that any configs of your original router/gateway DHCPd are not available to the LMCE DHCPd~~, ~~unless you manually recreate them in the LMCE~~'s ~~dhcpd.conf file. Also, the router/gateway LAN~~ IP~~# must be~~ manually ~~discovered/set, and then the LMCE LAN subnet must be manually configured to accommodate~~ it. There is no way to fix that problem, unless the router/gateway allows its LAN IP# to be set by DHCP (ie. a DHCP client running on the router/gateway that is set by the LMCE DHCPd). Conversely, there is no way for LMCE to insert into the router/gateway DHCPd configs the configs that LMCE needs clients for its own services (like IP phones) to automatically get from a DHCPd when they're plugged into a network. The only way to make DHCP fully automatic for LMCE is to use the recommended network architecture of a pair of ethernet ports on the LMCE server (or use a router/gateway DHCPd that can be remotely configured by the LMCE, and a script to glue them together).		#If it uses DHCP, either refresh it's IP-number manually or simply reboot it.

	=Switching From Single NIC to Double NIC=		=Switching From Single NIC to Double NIC=

Langstonius at 02:54, 21 June 2008

2008-06-21T02:54:21Z

←Older revision		Revision as of 02:54, 21 June 2008
Line 1:		Line 1:
			[[category: tutorials]]
	<p>LinuxMCE allows a user to plug in any type of device and automatically configures it and lets the user start using it right away without doing anything. The way this is accomplished is with an extension to the DHCP server. When a new device is plugged into the network and requests an IP address, this program connects to a central database to do a lookup of the device's unique MAC address to see what type of device it is. The database defines all the configuration data the device needs to run, and references the software drivers needed. This program then downloads and installs any needed software, adds configuration pages for the device to the user's [[LinuxMCE Admin Website]], and adds the device in the user's local database.</p>		<p>LinuxMCE allows a user to plug in any type of device and automatically configures it and lets the user start using it right away without doing anything. The way this is accomplished is with an extension to the DHCP server. When a new device is plugged into the network and requests an IP address, this program connects to a central database to do a lookup of the device's unique MAC address to see what type of device it is. The database defines all the configuration data the device needs to run, and references the software drivers needed. This program then downloads and installs any needed software, adds configuration pages for the device to the user's [[LinuxMCE Admin Website]], and adds the device in the user's local database.</p>

Royw: /* See also */

2008-02-04T02:45:19Z

Mog at 22:42, 10 January 2008

2008-01-10T22:42:46Z

←Older revision		Revision as of 22:42, 10 January 2008
Line 31:		Line 31:
	=Switching From Single NIC to Double NIC=		=Switching From Single NIC to Double NIC=
	There are instructions for switching from [[Single to Double NIC]].		There are instructions for switching from [[Single to Double NIC]].

			==See also==
			* [[Network Settings]]

Matthew: Link to Single to Double NIC

2007-12-18T01:00:30Z

Link to Single to Double NIC

←Older revision		Revision as of 01:00, 18 December 2007
Line 28:		Line 28:
	==Caveat==		==Caveat==
	This technique leaves a problem in that any configs of your original router/gateway DHCPd are not available to the LMCE DHCPd, unless you manually recreate them in the LMCE's dhcpd.conf file. Also, the router/gateway LAN IP# must be manually discovered/set, and then the LMCE LAN subnet must be manually configured to accommodate it. There is no way to fix that problem, unless the router/gateway allows its LAN IP# to be set by DHCP (ie. a DHCP client running on the router/gateway that is set by the LMCE DHCPd). Conversely, there is no way for LMCE to insert into the router/gateway DHCPd configs the configs that LMCE needs clients for its own services (like IP phones) to automatically get from a DHCPd when they're plugged into a network. The only way to make DHCP fully automatic for LMCE is to use the recommended network architecture of a pair of ethernet ports on the LMCE server (or use a router/gateway DHCPd that can be remotely configured by the LMCE, and a script to glue them together).		This technique leaves a problem in that any configs of your original router/gateway DHCPd are not available to the LMCE DHCPd, unless you manually recreate them in the LMCE's dhcpd.conf file. Also, the router/gateway LAN IP# must be manually discovered/set, and then the LMCE LAN subnet must be manually configured to accommodate it. There is no way to fix that problem, unless the router/gateway allows its LAN IP# to be set by DHCP (ie. a DHCP client running on the router/gateway that is set by the LMCE DHCPd). Conversely, there is no way for LMCE to insert into the router/gateway DHCPd configs the configs that LMCE needs clients for its own services (like IP phones) to automatically get from a DHCPd when they're plugged into a network. The only way to make DHCP fully automatic for LMCE is to use the recommended network architecture of a pair of ethernet ports on the LMCE server (or use a router/gateway DHCPd that can be remotely configured by the LMCE, and a script to glue them together).

			=Switching From Single NIC to Double NIC=
			There are instructions for switching from [[Single to Double NIC]].

Matthew: Shifted section degrees down to start at 1

2007-12-11T18:34:53Z

Shifted section degrees down to start at 1

←Older revision		Revision as of 18:34, 11 December 2007
Line 1:		Line 1:
	<p>LinuxMCE allows a user to plug in any type of device and automatically configures it and lets the user start using it right away without doing anything. The way this is accomplished is with an extension to the DHCP server. When a new device is plugged into the network and requests an IP address, this program connects to a central database to do a lookup of the device's unique MAC address to see what type of device it is. The database defines all the configuration data the device needs to run, and references the software drivers needed. This program then downloads and installs any needed software, adds configuration pages for the device to the user's [[LinuxMCE Admin Website]], and adds the device in the user's local database.</p>		<p>LinuxMCE allows a user to plug in any type of device and automatically configures it and lets the user start using it right away without doing anything. The way this is accomplished is with an extension to the DHCP server. When a new device is plugged into the network and requests an IP address, this program connects to a central database to do a lookup of the device's unique MAC address to see what type of device it is. The database defines all the configuration data the device needs to run, and references the software drivers needed. This program then downloads and installs any needed software, adds configuration pages for the device to the user's [[LinuxMCE Admin Website]], and adds the device in the user's local database.</p>

	==Single NIC & Existing DHCPd==		=Single NIC & Existing DHCPd=
	LinuxMCE recommends its core server have 2 ethernet ports, connecting one to an existing LAN (that routes to the Internet), and the other to a LAN segment on which sit all devices that LMCE will serve. That recommended setup runs a DHCP server (DHCPd) on LMCE to assign IP numbers and other network configs to devices on the "inside" LAN served by LMCE. LMCE runs a DHCP client on its "outside" LAN interface to get its IP# (and any other configs the existing LAN might assign) on that outside LAN. LMCE than routes inside LAN traffic to the outside LAN, including to any router/gateway on the outside LAN, while running a firewall that protects devices on the inside from activity on the outside.		LinuxMCE recommends its core server have 2 ethernet ports, connecting one to an existing LAN (that routes to the Internet), and the other to a LAN segment on which sit all devices that LMCE will serve. That recommended setup runs a DHCP server (DHCPd) on LMCE to assign IP numbers and other network configs to devices on the "inside" LAN served by LMCE. LMCE runs a DHCP client on its "outside" LAN interface to get its IP# (and any other configs the existing LAN might assign) on that outside LAN. LMCE than routes inside LAN traffic to the outside LAN, including to any router/gateway on the outside LAN, while running a firewall that protects devices on the inside from activity on the outside.

Line 26:		Line 26:
	Note that the dhcpd.conf file regenerated by the LMCE Admin site's Network Settings form has a bug which doesn't change all the IP#s properly. There might be other bugs, so check the whole file to be sure it's correct.		Note that the dhcpd.conf file regenerated by the LMCE Admin site's Network Settings form has a bug which doesn't change all the IP#s properly. There might be other bugs, so check the whole file to be sure it's correct.

	===Caveat===		==Caveat==
	This technique leaves a problem in that any configs of your original router/gateway DHCPd are not available to the LMCE DHCPd, unless you manually recreate them in the LMCE's dhcpd.conf file. Also, the router/gateway LAN IP# must be manually discovered/set, and then the LMCE LAN subnet must be manually configured to accommodate it. There is no way to fix that problem, unless the router/gateway allows its LAN IP# to be set by DHCP (ie. a DHCP client running on the router/gateway that is set by the LMCE DHCPd). Conversely, there is no way for LMCE to insert into the router/gateway DHCPd configs the configs that LMCE needs clients for its own services (like IP phones) to automatically get from a DHCPd when they're plugged into a network. The only way to make DHCP fully automatic for LMCE is to use the recommended network architecture of a pair of ethernet ports on the LMCE server (or use a router/gateway DHCPd that can be remotely configured by the LMCE, and a script to glue them together).		This technique leaves a problem in that any configs of your original router/gateway DHCPd are not available to the LMCE DHCPd, unless you manually recreate them in the LMCE's dhcpd.conf file. Also, the router/gateway LAN IP# must be manually discovered/set, and then the LMCE LAN subnet must be manually configured to accommodate it. There is no way to fix that problem, unless the router/gateway allows its LAN IP# to be set by DHCP (ie. a DHCP client running on the router/gateway that is set by the LMCE DHCPd). Conversely, there is no way for LMCE to insert into the router/gateway DHCPd configs the configs that LMCE needs clients for its own services (like IP phones) to automatically get from a DHCPd when they're plugged into a network. The only way to make DHCP fully automatic for LMCE is to use the recommended network architecture of a pair of ethernet ports on the LMCE server (or use a router/gateway DHCPd that can be remotely configured by the LMCE, and a script to glue them together).

Matthew: /* Single NIC & Existing DHCPd */

2007-11-21T17:58:50Z

Single NIC & Existing DHCPd

←Older revision		Revision as of 17:58, 21 November 2007
Line 17:		Line 17:
	##Check Homepage -> Advanced -> Network -> Network Settings to be sure settings were properly retained		##Check Homepage -> Advanced -> Network -> Network Settings to be sure settings were properly retained
	#/etc/dhcp3/dhcpd.conf :		#/etc/dhcp3/dhcpd.conf :
	## Exclude router/gateway IP# from allocatable ranges		##Ensure "option routers" parameter(s) is the correct IP#(s) of the existing router(s)
			##Exclude router/gateway IP# from allocatable ranges
	##Change "host px[1,2]" lines from 192.168.80.x IP#s to desired subnet IP#s (eg. 192.168.0.253 )		##Change "host px[1,2]" lines from 192.168.80.x IP#s to desired subnet IP#s (eg. 192.168.0.253 )
	##/etc/init.d/dhcp3-server restart		##/etc/init.d/dhcp3-server restart

Matthew: Added Single NIC setup

2007-11-13T21:37:38Z

Added Single NIC setup

←Older revision		Revision as of 21:37, 13 November 2007
Line 1:		Line 1:
	<p>LinuxMCE allows a user to plug in any type of device and automatically configures it and lets the user start using it right away without doing anything. The way this is accomplished is with an extension to the DHCP server. When a new device is plugged into the network and requests an IP address, this program connects to a central database to do a lookup of the device's unique MAC address to see what type of device it is. The database defines all the configuration data the device needs to run, and references the software drivers needed. This program then downloads and installs any needed software, adds configuration pages for the device to the user's [[LinuxMCE Admin Website]], and adds the device in the user's local database.</p>		<p>LinuxMCE allows a user to plug in any type of device and automatically configures it and lets the user start using it right away without doing anything. The way this is accomplished is with an extension to the DHCP server. When a new device is plugged into the network and requests an IP address, this program connects to a central database to do a lookup of the device's unique MAC address to see what type of device it is. The database defines all the configuration data the device needs to run, and references the software drivers needed. This program then downloads and installs any needed software, adds configuration pages for the device to the user's [[LinuxMCE Admin Website]], and adds the device in the user's local database.</p>

			==Single NIC & Existing DHCPd==
			LinuxMCE recommends its core server have 2 ethernet ports, connecting one to an existing LAN (that routes to the Internet), and the other to a LAN segment on which sit all devices that LMCE will serve. That recommended setup runs a DHCP server (DHCPd) on LMCE to assign IP numbers and other network configs to devices on the "inside" LAN served by LMCE. LMCE runs a DHCP client on its "outside" LAN interface to get its IP# (and any other configs the existing LAN might assign) on that outside LAN. LMCE than routes inside LAN traffic to the outside LAN, including to any router/gateway on the outside LAN, while running a firewall that protects devices on the inside from activity on the outside.

			However, it is possible to run LMCE on a host with a single ethernet port. There is some complexity in the configuration, the solution is not as fully automated and robust as is the recommended 2 ethernet version, and the omission of the LMCE firewall reduces the overall security of the installation. However, it is possible to do. These are instructions, including switching the LAN from an existing DHCP server to using the LMCE DHCPd instead. AFAICT, this technique doesn't leave any wrong configurations anywhere inside either LMCE's complex interdependencies or the remnants of the previously existing DHCP system.

			#In existing router/gateway
			##Disable DHCPd
			##Assign LAN IP# on desired subnet (eg 192.168.0.1 )
			##Ensure router/gateway is configured to route properly between the newly specified subnet and the other network
			# In LMCE Admin site:
			##Homepage -> Advanced -> Network -> Network Settings
			##Change all 192.168.80.x IP#s to desired subnet (eg. 192.168.0.x )
			##Set both NICs to the same IP# (and proper subnet info)
			##Reload DCERouter
			##Check Homepage -> Advanced -> Network -> Network Settings to be sure settings were properly retained
			#/etc/dhcp3/dhcpd.conf :
			## Exclude router/gateway IP# from allocatable ranges
			##Change "host px[1,2]" lines from 192.168.80.x IP#s to desired subnet IP#s (eg. 192.168.0.253 )
			##/etc/init.d/dhcp3-server restart
			##Force a LAN host to reset its network configs by DHCP, then test pinging across the router
			# Force each host on the LAN to reread its network configs by DHCP (eg. run its DHCP client or reboot if its DHCP client runs at startup).

			Note that the dhcpd.conf file regenerated by the LMCE Admin site's Network Settings form has a bug which doesn't change all the IP#s properly. There might be other bugs, so check the whole file to be sure it's correct.

			===Caveat===
			This technique leaves a problem in that any configs of your original router/gateway DHCPd are not available to the LMCE DHCPd, unless you manually recreate them in the LMCE's dhcpd.conf file. Also, the router/gateway LAN IP# must be manually discovered/set, and then the LMCE LAN subnet must be manually configured to accommodate it. There is no way to fix that problem, unless the router/gateway allows its LAN IP# to be set by DHCP (ie. a DHCP client running on the router/gateway that is set by the LMCE DHCPd). Conversely, there is no way for LMCE to insert into the router/gateway DHCPd configs the configs that LMCE needs clients for its own services (like IP phones) to automatically get from a DHCPd when they're plugged into a network. The only way to make DHCP fully automatic for LMCE is to use the recommended network architecture of a pair of ethernet ports on the LMCE server (or use a router/gateway DHCPd that can be remotely configured by the LMCE, and a script to glue them together).

Juliet at 08:59, 19 March 2007

2007-03-19T08:59:48Z

←Older revision		Revision as of 08:59, 19 March 2007
Line 1:		Line 1:
	<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table><p>LinuxMCE allows a user to plug in any type of device and automatically configures it and lets the user start using it right away without doing anything. The way this is accomplished is with an extension to the DHCP server. When a new device is plugged into the network and requests an IP address, this program connects to a central database to do a lookup of the device's unique MAC address to see what type of device it is. The database defines all the configuration data the device needs to run, and references the software drivers needed. This program then downloads and installs any needed software, adds configuration pages for the device to the user's [[~~Pluto~~ Admin Website]], and adds the device in the user's local database.</p>		<p>LinuxMCE allows a user to plug in any type of device and automatically configures it and lets the user start using it right away without doing anything. The way this is accomplished is with an extension to the DHCP server. When a new device is plugged into the network and requests an IP address, this program connects to a central database to do a lookup of the device's unique MAC address to see what type of device it is. The database defines all the configuration data the device needs to run, and references the software drivers needed. This program then downloads and installs any needed software, adds configuration pages for the device to the user's [[LinuxMCE Admin Website]], and adds the device in the user's local database.</p>

←Older revision		Revision as of 02:45, 4 February 2008
Line 34:		Line 34:
	==See also==		==See also==
	* [[Network Settings]]		* [[Network Settings]]
			* [[How to setup Local Authoritative DNS]]