Internet On Your Neo FreeRunner (USB Networking) - Revision history

Admin at 12:03, 13 June 2011

2011-06-13T12:03:14Z

← Older revision		Revision as of 12:03, 13 June 2011
Line 1:		Line 1:
	[[File:Internet-on-your-neo-1.png\|thumb\|400px\|Internet on FreeRunner via USB]]		[[File:Internet-on-your-neo-1.png\|thumb\|400px\|Internet on FreeRunner via USB]]
-	It is always simpler to have a direct internet access from your Neo FreeRunner when you want to install or develop something on your phone. We will take advantage of the internet connection of the PC and the [[USB connection between the PC and the Neo FreeRunner]].	+	It is always simpler to have a direct internet access from your Neo FreeRunner when you want to install or develop something on your phone. We will take advantage of the internet connection of the PC and the USB connection between the PC and the Neo FreeRunner.

	For this example, we are working with Ubuntu 10.10 on a laptop.		For this example, we are working with Ubuntu 10.10 on a laptop.

Admin at 12:00, 13 June 2011

2011-06-13T12:00:25Z

← Older revision		Revision as of 12:00, 13 June 2011
Line 1:		Line 1:
	[[File:Internet-on-your-neo-1.png\|thumb\|400px\|Internet on FreeRunner via USB]]		[[File:Internet-on-your-neo-1.png\|thumb\|400px\|Internet on FreeRunner via USB]]
-	It is always simpler to have a direct internet access from your Neo FreeRunner when you want to install or develop something on your phone. We will take advantage of the internet connection of the PC and the USB connection between the PC and the Neo.	+	It is always simpler to have a direct internet access from your Neo FreeRunner when you want to install or develop something on your phone. We will take advantage of the internet connection of the PC and the [[USB connection between the PC and the Neo FreeRunner]].

	For this example, we are working with Ubuntu 10.10 on a laptop.		For this example, we are working with Ubuntu 10.10 on a laptop.

91.180.253.215: /* With the network manager */

2011-03-12T22:26:35Z

With the network manager

← Older revision		Revision as of 22:26, 12 March 2011
Line 13:		Line 13:

	=== With the network manager ===		=== With the network manager ===
-	The easiest way to set up the connection with the Openmoko is to create a new connection (called Openmoko here) for the wired networks. For this connection, you choose a static (manual) IP address '''192.168.0.~~201~~'''.	+	The easiest way to set up the connection with the Openmoko is to create a new connection (called Openmoko here) for the wired networks. For this connection, you choose a static (manual) IP address '''192.168.0.200'''.

	[[File:Screenshot-Editing Openmoko.png\|350px]]		[[File:Screenshot-Editing Openmoko.png\|350px]]

91.180.253.215: /* Connect the Openmoko */

2011-03-12T22:26:28Z

Connect the Openmoko

← Older revision		Revision as of 22:26, 12 March 2011
Line 28:		Line 28:
	* Now, you can connect to the openmoko as root via ssh:		* Now, you can connect to the openmoko as root via ssh:
	$ ssh root@openmoko		$ ssh root@openmoko
-	root@om-gta02 ~ #	+	root@om-gta02 ~ #

	== Configuration IP tables ==		== Configuration IP tables ==

91.180.253.215: /* With the network manager */

2011-03-12T22:26:07Z

With the network manager

← Older revision		Revision as of 22:26, 12 March 2011
Line 13:		Line 13:

	=== With the network manager ===		=== With the network manager ===
-	The easiest way to set up the connection with the Openmoko is to create a new connection (called Openmoko here) for the wired networks. For this connection, you choose a static (manual) IP address '''192.168.0.~~200~~'''.	+	The easiest way to set up the connection with the Openmoko is to create a new connection (called Openmoko here) for the wired networks. For this connection, you choose a static (manual) IP address '''192.168.0.201'''.

	[[File:Screenshot-Editing Openmoko.png\|350px]]		[[File:Screenshot-Editing Openmoko.png\|350px]]

Admin at 17:20, 11 March 2011

2011-03-11T17:20:25Z

← Older revision		Revision as of 17:20, 11 March 2011
Line 44:		Line 44:
	* Fifth step: add these lines:		* Fifth step: add these lines:
	/sbin/iptables -P FORWARD ACCEPT		/sbin/iptables -P FORWARD ACCEPT
-	/sbin/iptables --table nat -A POSTROUTING -s 192.168.0.202/32 -o ~~wlan0~~ -j MASQUERADE	+	/sbin/iptables --table nat -A POSTROUTING -s 192.168.0.202/32 -o iface -j MASQUERADE
-	where iface corresponds to the interface connected to the internet (wlan0, eth0, eth1, ...). These changes also take effect only after a reboot. To make them effective directly, type the same command in a terminal by replacing '''/sbin/''' by '''sudo'''.	+	where '''iface''' corresponds to the interface connected to the internet (wlan0, eth0, eth1, ...). These changes also take effect only after a reboot. To make them effective directly, type the same command in a terminal by replacing '''/sbin/''' by '''sudo'''.

	== Sources ==		== Sources ==
	* http://wiki.openmoko.org/wiki/USB_Networking		* http://wiki.openmoko.org/wiki/USB_Networking
	* http://ubuntuforums.org/showthread.php?t=713874		* http://ubuntuforums.org/showthread.php?t=713874

Admin at 17:19, 11 March 2011

2011-03-11T17:19:30Z

← Older revision		Revision as of 17:19, 11 March 2011
Line 28:		Line 28:
	* Now, you can connect to the openmoko as root via ssh:		* Now, you can connect to the openmoko as root via ssh:
	$ ssh root@openmoko		$ ssh root@openmoko
		+	root@om-gta02 ~ #

	== Configuration IP tables ==		== Configuration IP tables ==

Admin at 17:18, 11 March 2011

2011-03-11T17:18:54Z

← Older revision		Revision as of 17:18, 11 March 2011
Line 44:		Line 44:
	/sbin/iptables -P FORWARD ACCEPT		/sbin/iptables -P FORWARD ACCEPT
	/sbin/iptables --table nat -A POSTROUTING -s 192.168.0.202/32 -o wlan0 -j MASQUERADE		/sbin/iptables --table nat -A POSTROUTING -s 192.168.0.202/32 -o wlan0 -j MASQUERADE
-	where iface corresponds to the interface connected to the internet (wlan0, eth0, eth1, ...). These changes also take effect only after a reboot. To make them effective directly, type the same command in a terminal by replacing '''/sbin/''' by '''sudo'''	+	where iface corresponds to the interface connected to the internet (wlan0, eth0, eth1, ...). These changes also take effect only after a reboot. To make them effective directly, type the same command in a terminal by replacing '''/sbin/''' by '''sudo'''.

	== Sources ==		== Sources ==
	* http://wiki.openmoko.org/wiki/USB_Networking		* http://wiki.openmoko.org/wiki/USB_Networking
	* http://ubuntuforums.org/showthread.php?t=713874		* http://ubuntuforums.org/showthread.php?t=713874

Admin at 17:18, 11 March 2011

2011-03-11T17:18:37Z

← Older revision		Revision as of 17:18, 11 March 2011
Line 24:		Line 24:
	address 192.168.0.200		address 192.168.0.200
	netmask 255.255.255.0		netmask 255.255.255.0
-	* ~~Reboot~~ the network service by running the following command:	+	* Restart the network service by running the following command:
-	/etc/init.d/networking restart	+	$ /etc/init.d/networking restart
		+	* Now, you can connect to the openmoko as root via ssh:
		+	$ ssh root@openmoko

	== Configuration IP tables ==		== Configuration IP tables ==
		+
		+	In order to make the computer connected to the openmoko forward packets comming from the interface eth1, it is necessary to enable IP forwarding which is deactivated by default in Ubuntu. It is therefore requiered to issue the following commands with administrator (sudo) priviledges :
		+	* First step:
		+	$ gedit /etc/sysctl.conf
		+	* Second step: look for the following line in this file:
		+	#net.ipv4.conf.default.forwarding=1
		+	and uncomment it (remove the # caracter if not already done).
		+	* Third step: This change will be effective at the next reboot, or use the following command to make it effective directly:
		+	sudo sysctl -w net.ipv4.conf.default.forwarding = 1
		+	* Fourth step: it is now time to configure the iptables in order to let the packets go through the gateway (computer connected to the Openmoko):
		+	$ gedit /etc/rc.local
		+	* Fifth step: add these lines:
		+	/sbin/iptables -P FORWARD ACCEPT
		+	/sbin/iptables --table nat -A POSTROUTING -s 192.168.0.202/32 -o wlan0 -j MASQUERADE
		+	where iface corresponds to the interface connected to the internet (wlan0, eth0, eth1, ...). These changes also take effect only after a reboot. To make them effective directly, type the same command in a terminal by replacing '''/sbin/''' by '''sudo'''

	== Sources ==		== Sources ==
	* http://wiki.openmoko.org/wiki/USB_Networking		* http://wiki.openmoko.org/wiki/USB_Networking
	* http://ubuntuforums.org/showthread.php?t=713874		* http://ubuntuforums.org/showthread.php?t=713874

Admin at 17:11, 11 March 2011

2011-03-11T17:11:53Z

← Older revision		Revision as of 17:11, 11 March 2011
Line 5:		Line 5:

	== Connect the Openmoko ==		== Connect the Openmoko ==
-	~~=== With the network manager ===~~	+	The first thing to do is to create an alias for the IP address of the Neo FreeRunner.
-	The ~~easiest way~~ to ~~set up the connection with the Openmoko~~ is to create ~~a new connection (called Openmoko here)~~ for the ~~wired networks. For this connection, you choose a static (manual)~~ IP address ~~'''~~192.168.0.~~200'''~~.	+	* Edit the file /etc/hosts by adding the line:
		+	192.168.0.202 openmoko
		+	Note : The alias "openmoko" can be replaced by any other name at the will of the user.

-	~~[[File:Screenshot-Editing Openmoko~~.~~png\|100px]]~~	+	Then, we must set up the connection.

		+	=== With the network manager ===
		+	The easiest way to set up the connection with the Openmoko is to create a new connection (called Openmoko here) for the wired networks. For this connection, you choose a static (manual) IP address '''192.168.0.200'''.

		+	[[File:Screenshot-Editing Openmoko.png\|350px]]

	=== Without the network manager ===		=== Without the network manager ===
		+	* Edit the file '''/etc/network/interfaces''' by adding the following lines:
		+	# The Openmoko network interface
		+	auto eth1
		+	iface eth1 inet static
		+	address 192.168.0.200
		+	netmask 255.255.255.0
		+	* Reboot the network service by running the following command:
		+	/etc/init.d/networking restart

	== Configuration IP tables ==		== Configuration IP tables ==