Naming networkinterfaces using udev - Revision history

Jca: /* Further information */

2012-01-19T16:04:13Z

Further information

← Older revision		Revision as of 18:04, 19 January 2012
Line 22:		Line 22:
	udevinfo -a -p /sys/class/net/eth0		udevinfo -a -p /sys/class/net/eth0

	on newer systems use		on newer systems (ubuntu 11.10) use
	udevadm info -a -p /sys/class/net/eth0		udevadm info -a -p /sys/class/net/eth0

Jca: /* Further information */

2012-01-19T15:59:06Z

Further information

← Older revision		Revision as of 17:59, 19 January 2012
Line 21:		Line 21:
	To find the information available for the different networkinterfaces (and all other devices) use "udevinfo". For 'eth0' execute the following command:		To find the information available for the different networkinterfaces (and all other devices) use "udevinfo". For 'eth0' execute the following command:
	udevinfo -a -p /sys/class/net/eth0		udevinfo -a -p /sys/class/net/eth0

			on newer systems use
			udevadm info -a -p /sys/class/net/eth0

	All devices available on the system are found in the '/sys' file system, and can be listed using "udevinfo".		All devices available on the system are found in the '/sys' file system, and can be listed using "udevinfo".

Sh at 13:29, 17 April 2009

2009-04-17T13:29:54Z

← Older revision		Revision as of 15:29, 17 April 2009
Line 22:		Line 22:
	udevinfo -a -p /sys/class/net/eth0		udevinfo -a -p /sys/class/net/eth0

	All devices available on the system are found in the '/sys' file system, and can be listed using "udevinfo".		All devices available on the system are found in the '/sys' file system, and can be listed using "udevinfo".
			All udev rules are found in
			/etc/udev/rules.d
			The files in this directory are parsed in lexical order.

Sh at 13:26, 17 April 2009

2009-04-17T13:26:54Z

← Older revision		Revision as of 15:26, 17 April 2009
Line 1:		Line 1:
	== Naming networkinterfaces using udev ==		== Naming networkinterfaces using udev ==

	Usually the robots are configured to use DHCP at networkinterface 'eth0' and have a static IP (10.0.1.2) at interface 'eth1'. In order to get the wireless netcard to use DHCP we want to rename it to 'eth0'. This can be achieved by using the udev system.		Usually the robots are configured to use DHCP at networkinterface 'eth0' and have a static IP (10.0.1.2) at interface 'eth1'. In order to get the wireless PCMCIA netcard to use DHCP we want to rename it to 'eth0'. This can be achieved by using the udev system.
	Changes are done in the file		Changes are done in the file
	/etc/udev/rules.d/75-network-devices.rules		/etc/udev/rules.d/75-network-devices.rules

Sh at 13:23, 17 April 2009

2009-04-17T13:23:17Z

← Older revision		Revision as of 15:23, 17 April 2009
Line 17:		Line 17:
	SUBSYSTEMS=="pci", DRIVERS=="r8168", NAME="eth1"		SUBSYSTEMS=="pci", DRIVERS=="r8168", NAME="eth1"
	to achieve the same on the Jetway motherboards.		to achieve the same on the Jetway motherboards.

			=== Further information ===
			To find the information available for the different networkinterfaces (and all other devices) use "udevinfo". For 'eth0' execute the following command:
			udevinfo -a -p /sys/class/net/eth0

			All devices available on the system are found in the '/sys' file system, and can be listed using "udevinfo".

Sh at 13:12, 17 April 2009

2009-04-17T13:12:58Z

← Older revision		Revision as of 15:12, 17 April 2009
Line 1:		Line 1:
	== Naming networkinterfaces using udev ==		== Naming networkinterfaces using udev ==

	Usually the ~~SMR's~~ are configured to use DHCP at networkinterface 'eth0' and have a static IP (10.0.1.2) at interface 'eth1'. In order to get the wireless netcard to use DHCP we want to rename it to 'eth0'. This can be achieved by using the udev system.		Usually the robots are configured to use DHCP at networkinterface 'eth0' and have a static IP (10.0.1.2) at interface 'eth1'. In order to get the wireless netcard to use DHCP we want to rename it to 'eth0'. This can be achieved by using the udev system.
	Changes are done in the file		Changes are done in the file
	/etc/udev/rules.d/75-network-devices.rules		/etc/udev/rules.d/75-network-devices.rules
Line 9:		Line 9:
	SUBSYSTEMS=="pci", DRIVERS=="yenta_cardbus", NAME="eth0"		SUBSYSTEMS=="pci", DRIVERS=="yenta_cardbus", NAME="eth0"

	~~This~~ will work on the VIA motherboards. The "via-rhine" ~~should be change~~ to "r8168" on the Jetway ~~Atom boards since these are using a Realtek network controller~~.		Remove any conflicting lines.

			=== Jetway Atom boards ===
			The approach above will work on the VIA based motherboards used at the SMRs. The new Intel Atom based motherborads from Jetway uses a Realtek network controller. Therefore change the line
			SUBSYSTEMS=="pci", DRIVERS=="via-rhine", NAME="eth1"
			to
			SUBSYSTEMS=="pci", DRIVERS=="r8168", NAME="eth1"
			to achieve the same on the Jetway motherboards.

Sh: New page: == Naming networkinterfaces using udev == Usually the SMR's are configured to use DHCP at networkinterface 'eth0' and have a static IP (10.0.1.2) at interface 'eth1'. In order to get the ...

2009-04-17T13:06:52Z

New page: == Naming networkinterfaces using udev == Usually the SMR's are configured to use DHCP at networkinterface 'eth0' and have a static IP (10.0.1.2) at interface 'eth1'. In order to get the ...

New page

== Naming networkinterfaces using udev ==

Usually the SMR's are configured to use DHCP at networkinterface 'eth0' and have a static IP (10.0.1.2) at interface 'eth1'. In order to get the wireless netcard to use DHCP we want to rename it to 'eth0'. This can be achieved by using the udev system.
Changes are done in the file
/etc/udev/rules.d/75-network-devices.rules
Add the following two lines:

SUBSYSTEMS=="pci", DRIVERS=="via-rhine", NAME="eth1"
SUBSYSTEMS=="pci", DRIVERS=="yenta_cardbus", NAME="eth0"

This will work on the VIA motherboards. The "via-rhine" should be change to "r8168" on the Jetway Atom boards since these are using a Realtek network controller.