RPi Setting up a static IP in Debian - Revision history

Spyder at 06:27, 15 March 2013

2013-03-15T06:27:17Z

2013-03-15T06:21:06Z

note regarding failure to restart network "Running /etc/init.d/networking restart is deprecated because it may not re-enable some interfaces"

2012-06-18T18:47:42Z

2012-05-15T19:13:39Z

debian6-19-04-2012 buid has location /etc/network/interfaces changed to reflect this

2012-05-03T09:41:58Z

2012-05-02T13:37:36Z

2012-05-02T10:49:16Z

2012-05-02T10:47:28Z

2012-05-02T10:46:53Z

2012-05-02T10:46:07Z

@@ Line 54: / Line 54: @@
 "Running /etc/init.d/networking restart is deprecated because it may not re-enable some interfaces"
 Solution if you experience this, connect keyboard and "sudo reboot", or do it the hard way.
 [[Category:RaspberryPi]]

← Older revision		Revision as of 06:21, 15 March 2013
Line 50:		Line 50:

	You may now be disconnected from your RPi if you are working through the network. Connect again to the RPi using the static IP you chose and you should now be fine.		You may now be disconnected from your RPi if you are working through the network. Connect again to the RPi using the static IP you chose and you should now be fine.
		+
		+	You may receive the following error upon executing this command, and no longer have network access even though the network indicators are active.
		+	"Running /etc/init.d/networking restart is deprecated because it may not re-enable some interfaces"
		+	Solution if you experience this, connect keyboard and "sudo reboot", or do it the hard way.

	[[Category:RaspberryPi]]		[[Category:RaspberryPi]]

← Older revision		Revision as of 18:47, 18 June 2012
Line 50:		Line 50:

	You may now be disconnected from your RPi if you are working through the network. Connect again to the RPi using the static IP you chose and you should now be fine.		You may now be disconnected from your RPi if you are working through the network. Connect again to the RPi using the static IP you chose and you should now be fine.
		+
		+	[[Category:RaspberryPi]]

@@ Line 3: / Line 3: @@
 To achieve this there are a few quick steps to be followed.
-You only need to modify the file /etc/networking/interfaces
+You only need to modify the file /etc/network/interfaces
 Before you do, backup the current version of the interfaces file, if there is already one present:
-   pi@raspberry:sudo cp /etc/networking/interfaces /etc/networking/interfaces.sav
+   pi@raspberry:sudo cp /etc/network/interfaces /etc/network/interfaces.sav
 You can edit the file with any text editor such as vi or vim.
 We need root privileges, so we use sudo:
-   pi@raspberry:sudo vi /etc/networking/interfaces
+   pi@raspberry:sudo vi /etc/network/interfaces
 In the interfaces file look for a line such as:

@@ Line 40: / Line 40: @@
 If for example your LAN is configured to have IP adresses in the range x.x.x.1 to x.x.x.255, you will put x.x.x.0 in the network line.
-"address" is the IP you want the RPi will assume (in the proper range, as described above). pay attention not to use an IP already used by another device in your LAN or that can be assigned to a device by your router by DHCP (set the DHCP range of the router wisely).
+"address" is the IP you want the RPi will assume (in the proper range, as described above). pay attention not to use an IP already used by another device in your LAN or that can be assigned to a device by your router by DHCP (set the DHCP range of the router wisely in order to avoid potential overlaps).
 "netmask" will "always" be 255.255.255.0

@@ Line 36: / Line 36: @@
    broadcast 192.168.1.255
-Only the address and netmask data are required.
+Only the address and netmask data are strictly required.
 If for example your LAN is configured to have IP adresses in the range x.x.x.1 to x.x.x.255, you will put x.x.x.0 in the network line.

@@ Line 21: / Line 21: @@
    #iface eth0 inet dhcp
-In the file you must put the following content:
+In the file you must insert the following lines:
    # The loopback interface
    auto lo