Single to Double NIC - Revision history

Mcefan at 05:00, 9 October 2012

2012-10-09T05:00:32Z

←Older revision		Revision as of 05:00, 9 October 2012
Line 1:		Line 1:
	{{versioninfo}}		{{versioninfo}}
	[[Category: Tutorials]]		[[Category: Tutorials\| NIC]]
	[[Category: Networking]]		[[Category: Networking]]
	[[Category:Network Adapters\|*]]		[[Category:Network Adapters\|*]]

Mcefan at 11:37, 8 October 2012

2012-10-08T11:37:43Z

←Older revision		Revision as of 11:37, 8 October 2012
Line 1:		Line 1:
	{{versioninfo}}		{{versioninfo}}
	[[Category: Tutorials]]		[[Category: Tutorials]]
	[[Category: Networking\|~~Network Setup, nic~~]]		[[Category: Networking]]
			[[Category:Network Adapters\|*]]

	When switching from a Single NIC setup to using dual NICs, Changes need to be made in several places. Order of these operations is important.		When switching from a Single NIC setup to using dual NICs, Changes need to be made in several places. Order of these operations is important.

Mcefan at 11:28, 8 October 2012

2012-10-08T11:28:39Z

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

	When switching from a Single NIC setup to using dual NICs, Changes need to be made in several places. Order of these operations is important.		When switching from a Single NIC setup to using dual NICs, Changes need to be made in several places. Order of these operations is important.

Wierdbeard65 at 08:46, 5 May 2010

2010-05-05T08:46:51Z

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

Zaerc: should of been "Diskless_ExportsNFS.sh" not "Diskless_Setup.sh" :^P

2008-03-05T17:13:53Z

should of been "Diskless_ExportsNFS.sh" not "Diskless_Setup.sh" :^P

←Older revision		Revision as of 17:13, 5 March 2008
Line 101:		Line 101:
	## END : DisklessMDRoots		## END : DisklessMDRoots

	If you had to make these changes you might also like to modify ''/usr/pluto/bin/~~Diskless_Setup~~.sh'' accordingly as well since that seems to be the template from which ''/etc/exports'' is generated.		If you had to make these changes you might also like to modify ''/usr/pluto/bin/Diskless_ExportsNFS.sh'' accordingly as well since that seems to be the template from which ''/etc/exports'' is generated.

Zaerc: added remark on editing /usr/pluto/bin/Diskless_Setup.sh

2008-03-03T20:22:25Z

added remark on editing /usr/pluto/bin/Diskless_Setup.sh

←Older revision		Revision as of 20:22, 3 March 2008
Line 100:		Line 100:
	/usr/pluto/diskless/108 '''192.168.80.0'''/255.255.255.0(rw,no_root_squash,no_all_squash,sync,no_subtree_check)		/usr/pluto/diskless/108 '''192.168.80.0'''/255.255.255.0(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
	## END : DisklessMDRoots		## END : DisklessMDRoots

			If you had to make these changes you might also like to modify ''/usr/pluto/bin/Diskless_Setup.sh'' accordingly as well since that seems to be the template from which ''/etc/exports'' is generated.

Matthew: DHCPd interface = eth1

2007-12-20T06:54:53Z

DHCPd interface = eth1

←Older revision		Revision as of 06:54, 20 December 2007
Line 29:		Line 29:
	netmask 255.255.255.0		netmask 255.255.255.0

	* Ensure /etc/default/dhcp3-server contains (only) INTERFACES="~~eth0~~"		* Ensure /etc/default/dhcp3-server contains (only) INTERFACES="eth1" for the internal network.
	* You may need to edit ''/etc/iftab'' as well and add a line similar to the eth0 one for your new eth1 with it's own unique MAC address. See '''man iftab''' for more details on this file.		* You may need to edit ''/etc/iftab'' as well and add a line similar to the eth0 one for your new eth1 with it's own unique MAC address. See '''man iftab''' for more details on this file.
	* Web Admin: Advanced menu > Network > Network Settings (more or less optional)		* Web Admin: Advanced menu > Network > Network Settings (more or less optional)

Matthew: DHCPd interface = eth0

2007-12-20T06:53:38Z

DHCPd interface = eth0

←Older revision		Revision as of 06:53, 20 December 2007
Line 29:		Line 29:
	netmask 255.255.255.0		netmask 255.255.255.0

			* Ensure /etc/default/dhcp3-server contains (only) INTERFACES="eth0"
	* You may need to edit ''/etc/iftab'' as well and add a line similar to the eth0 one for your new eth1 with it's own unique MAC address. See '''man iftab''' for more details on this file.		* You may need to edit ''/etc/iftab'' as well and add a line similar to the eth0 one for your new eth1 with it's own unique MAC address. See '''man iftab''' for more details on this file.
	* Web Admin: Advanced menu > Network > Network Settings (more or less optional)		* Web Admin: Advanced menu > Network > Network Settings (more or less optional)

Matthew: Revise operations order to tested sequence

2007-12-20T06:44:28Z

Revise operations order to tested sequence

←Older revision		Revision as of 06:44, 20 December 2007
Line 2:		Line 2:
	[[Category: Networking]]		[[Category: Networking]]

	When switching from a Single NIC setup to using dual NICs, Changes need to be made in several places.		When switching from a Single NIC setup to using dual NICs, Changes need to be made in several places. Order of these operations is important.

	* Web Admin: Show devices tree/My Devices/CORE > Device data/Network Interfaces		* Web Admin: Show devices tree/My Devices/CORE > Device data/Network Interfaces

Matthew: Revise operations order to tested sequence

2007-12-20T06:43:46Z

Revise operations order to tested sequence

←Older revision		Revision as of 06:43, 20 December 2007
Line 4:		Line 4:
	When switching from a Single NIC setup to using dual NICs, Changes need to be made in several places.		When switching from a Single NIC setup to using dual NICs, Changes need to be made in several places.

	* Web Admin: Advanced menu > Network > Network Settings (more or less optional)
	* Web Admin: Show devices tree/My Devices/CORE > Device data/Network Interfaces		* Web Admin: Show devices tree/My Devices/CORE > Device data/Network Interfaces
	** Change: ''eth0,dhcp\|'''eth0:0''',192.168.80.1,255.255.255.0'' to: ''eth0,dhcp\|'''eth1''',192.168.80.1,255.255.255.0''		** Change: ''eth0,dhcp\|'''eth0:0''',192.168.80.1,255.255.255.0'' to: ''eth0,dhcp\|'''eth1''',192.168.80.1,255.255.255.0''
Line 13:		Line 12:
	address 127.0.0.1		address 127.0.0.1
	netmask 255.0.0.0		netmask 255.0.0.0
			#
			#
	iface eth0 inet dhcp		# Set eth0 to use DHCP to connect to cable/DSL/etc automatically.
			auto eth0
			iface eth0 inet dhcp
			#
	#auto eth0:0		#auto eth0:0
	#iface eth0:0 inet static		#iface eth0:0 inet static
	# address 192.168.80.1		# address 192.168.80.1
	# netmask 255.255.255.0		# netmask 255.255.255.0
	/ This sets eth0 to use DHCP to connect to cable/DSL/etc. automatically /		#
	~~iface eth1 inet static~~		# Set eth1 to use the internal network.
	~~address 192.168.80.1~~
	~~netmask 255.255.255.0~~
	/ This sets eth1 to use the internal network /
	auto eth1		auto eth1
			iface eth1 inet static
	~~auto eth0~~		address 192.168.80.1
			netmask 255.255.255.0

	* You may need to edit ''/etc/iftab'' as well and add a line similar to the eth0 one for your new eth1 with it's own unique MAC address. See '''man iftab''' for more details on this file.		* You may need to edit ''/etc/iftab'' as well and add a line similar to the eth0 one for your new eth1 with it's own unique MAC address. See '''man iftab''' for more details on this file.
			* Web Admin: Advanced menu > Network > Network Settings (more or less optional)
	* Check the /etc/exports file, if it looks like this (Please note that these are just examples, your file will likely be somewhat different):		* Check the /etc/exports file, if it looks like this (Please note that these are just examples, your file will likely be somewhat different):

	# /etc/exports: the access control list for filesystems which may be exported		# /etc/exports: the access control list for filesystems which may be exported
	# to NFS clients. See exports(5).		# to NFS clients. See exports(5).