Talk:USB Networking - Revision history

Factor4: /* Driver options in kernel config */

2010-01-06T00:52:14Z

‎Driver options in kernel config

Matzehuber: /* Using network-manager on systems using udev */

2009-07-16T12:09:16Z

‎Using network-manager on systems using udev

Dareus at 13:24, 14 July 2009

2009-07-14T13:24:50Z

Ockham: Deletion Proposal about Ubuntu 9.04 section, question

2009-07-05T18:55:46Z

Deletion Proposal about Ubuntu 9.04 section, question

Frank: /* no inet in interfaces */

2009-06-17T14:55:07Z

‎no inet in interfaces

Frank: /* no inet in interfaces */

2009-06-17T14:53:44Z

‎no inet in interfaces

Frank: /* no inet in interfaces */

2009-06-17T14:51:17Z

‎no inet in interfaces

Frank: /* no inet in interfaces */

2009-06-17T14:50:34Z

‎no inet in interfaces

Pander at 08:49, 16 June 2009

2009-06-16T08:49:53Z

Jensk: /* Script */

2009-05-09T13:23:35Z

‎Script

← Older revision		Revision as of 00:52, 6 January 2010
Line 1:		Line 1:
		+	= Yet another suggestion for USB Networking =
		+	Hi. I suggest using:
		+	* /etc/udev/rules.d/70-persistent-net.rules to rename eth* to usb0 (afterwards restarting udev), e.g. on recent Ubuntus:
		+	# USB device 0x1457:0x5122 (usb)
		+	SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?", ATTR{address}=="00:1f:11:01:3b:93" ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth", NAME="usb0"
		+	* Then use e.g. the network-manager in user space to configure the device "usb0" as proposed by others, e.g. 192.168.0.200 with 192.168.0.192/26, or similarly, or with a different IP, if you want.
		+	* Then make a link /etc/network/if-up.d/freerunner to /usr/local/bin/freerunner.sh and similarly from /etc/network/if-up.d/freerunner with content of the script:
		+	#!/bin/sh
		+	MY_IFACE="usb0"
		+	MY_NETWORK="192.168.0.0/24"
		+
		+	if [ "$IFACE" != "$MY_IFACE" ]; then
		+	exit 0
		+	fi
		+
		+	IPNET=$MY_NETWORK
		+	# alternatively:
		+	#ret1(){ echo $1;}
		+	#IPNET=`ret1${IP4_ADDRESS_0}`
		+
		+	case "$MODE" in
		+	start)
		+	/sbin/iptables -A POSTROUTING -t nat -j MASQUERADE -s $IPNET
		+	/sbin/sysctl -w net.ipv4.ip_forward=1
		+	[ $VERBOSITY -gt 0 ] && logger "added freerunner routing"
		+	;;
		+	stop)
		+	/sbin/iptables -D POSTROUTING -t nat -j MASQUERADE -s $IPNET
		+	/sbin/sysctl -w net.ipv4.ip_forward=0
		+	[ $VERBOSITY -gt 0 ] && logger "removed freerunner routing"
		+	;;
		+	*) exit 0
		+	esac
		+	* This will set up the masquerading, as others proposed it, and will remove it on usb-network down events.
		+
		+	What do you think? --[[User:Factor4\|Factor4]] 00:52, 6 January 2010 (UTC)
		+
	= Driver options in kernel config =		= Driver options in kernel config =
	Hi, I didn't want to change it in case I was wrong, but I believe that the options to configure your		Hi, I didn't want to change it in case I was wrong, but I believe that the options to configure your

← Older revision		Revision as of 12:09, 16 July 2009
Line 154:		Line 154:

	--[[User:Dareus\|Dareus]] 15:24, 14 July 2009 (CET)		--[[User:Dareus\|Dareus]] 15:24, 14 July 2009 (CET)
		+
		+
		+	==Experience on SHR in Version 209-05-02 / OpenSuse 11.1==
		+	my route before hacking was without router:
		+
		+	(route add default dev usb0)
		+
		+	Destination Gateway Genmask Flags Metric Ref Use Iface
		+	192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 usb0
		+	0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 usb0
		+	... and (in my oppinion) should work, but did'nt route anything further than to my host 10.0.0.1
		+
		+	(which is on a router(10.0.0.254) to outside in an Class A Network 10.0.0.0/8)
		+
		+	i changed that to:
		+
		+	(route add default gw 192.168.0.200 dev usb0)
		+
		+	and got the working variant:
		+
		+	Destination Gateway Genmask Flags Metric Ref Use Iface
		+	192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 usb0
		+	0.0.0.0 192.168.0.200 0.0.0.0 UG 0 0 0 usb0
		+	So maybe, the order in which /etc/network/interfaces configures usb0 seems to be the problem:
		+
		+	i changed it to:
		+
		+	auto usb0
		+	iface usb0 inet static
		+	address 192.168.0.202
		+	network 192.168.0.0
		+	netmask 255.255.255.0
		+	gateway 192.168.0.200
		+
		+	this works fine here on SHR [[without any firewall/nat/masquerade/routing]] etc.

← Older revision		Revision as of 13:24, 14 July 2009
Line 145:		Line 145:

	I find the 8.10 instructions clearer and more to the point than the 9.04 ones. Moreover, the 9.04 ones don't feature actual routing, so I'd suggest deleting the 9.04 section, and adding a note to the 8.10 sections that with Qi, it's eth1 and not usb0. Also, one question: does anyone know if the routing given by the iptables commands in the 8.10 section can also be achieved just by using the System > Administration > Network > eth1 > IPv4 Settings > Routes dialog? --[[User:Ockham\|Ockham]] 18:55, 5 July 2009 (UTC)		I find the 8.10 instructions clearer and more to the point than the 9.04 ones. Moreover, the 9.04 ones don't feature actual routing, so I'd suggest deleting the 9.04 section, and adding a note to the 8.10 sections that with Qi, it's eth1 and not usb0. Also, one question: does anyone know if the routing given by the iptables commands in the 8.10 section can also be achieved just by using the System > Administration > Network > eth1 > IPv4 Settings > Routes dialog? --[[User:Ockham\|Ockham]] 18:55, 5 July 2009 (UTC)
		+
		+	==Using network-manager on systems using udev==
		+	following these steps i found that iptables is not set correctly (cannot reach the web from FR) i tried manually executing
		+	sudo /usr/local/sbin/freerunner-usb-add.sh
		+	and everything i got was
		+	Cannot find device "00:00:22:55:bb:00"
		+	what's wrong?
		+
		+	--[[User:Dareus\|Dareus]] 15:24, 14 July 2009 (CET)

← Older revision		Revision as of 18:55, 5 July 2009
Line 141:		Line 141:

	Carig Philippines --[[User:Frank\|frank]] 14:50, 17 June 2009 (UTC)		Carig Philippines --[[User:Frank\|frank]] 14:50, 17 June 2009 (UTC)
		+
		+	= Ubuntu Instructions =
		+
		+	I find the 8.10 instructions clearer and more to the point than the 9.04 ones. Moreover, the 9.04 ones don't feature actual routing, so I'd suggest deleting the 9.04 section, and adding a note to the 8.10 sections that with Qi, it's eth1 and not usb0. Also, one question: does anyone know if the routing given by the iptables commands in the 8.10 section can also be achieved just by using the System > Administration > Network > eth1 > IPv4 Settings > Routes dialog? --[[User:Ockham\|Ockham]] 18:55, 5 July 2009 (UTC)

@@ Line 136: / Line 136: @@
 I think the inet label in interfaces for eth1 (when openmoko is on eth1 like Ubuntu 9.04) causes the host (laptop) to try to make a connection to the internet via the openmoko device. This could be just the opposite of what you want. I'm not an expert on this but removing inet in interfaces for the openmoko devices fixed my problem. Any comments on this? [[User:Pander|Pander]] 08:49, 16 June 2009 (UTC)
-I merely checked on /etc/udev/rules.d which interface would be used ( eth1 ) Then went to System/Administration/Network and there gave the address netmask and the default gateway for eth1 -- simple and no problem. The default GW is the gateway of the system. On laptop like you did. Did not check yet if i can go to the internet from the Freerunner  via eth1, wlan is OK
+I merely checked on /etc/udev/rules.d which interface would be used ( eth1 ) Then went to System/Administration/Network and there gave the address netmask and the default gateway for eth1 -- simple and no problem. The default GW is the gateway of the system. On laptop like you did. All works well Internet for laptop and contact with Freerunner.
 Carig Philippines --[[User:Frank|frank]] 14:50, 17 June 2009 (UTC)

← Older revision		Revision as of 14:50, 17 June 2009
Line 134:		Line 134:

	== no inet in interfaces ==		== no inet in interfaces ==
−	I think the inet label in interfaces for eth1 (when openmoko is on eth1 like ~~Ubuintu~~ 9.04) causes the host (laptop) to try to make a connection to the internet via the openmoko device. This could be just the opposite of what you want. I'm not an expert on this but removing inet in interfaces for the openmoko devices fixed my problem. Any comments on this? [[User:Pander\|Pander]] 08:49, 16 June 2009 (UTC)	+	I think the inet label in interfaces for eth1 (when openmoko is on eth1 like Ubuntu 9.04) causes the host (laptop) to try to make a connection to the internet via the openmoko device. This could be just the opposite of what you want. I'm not an expert on this but removing inet in interfaces for the openmoko devices fixed my problem. Any comments on this? [[User:Pander\|Pander]] 08:49, 16 June 2009 (UTC)
		+
		+	I merely checked on /etc/udev/rules.d which interface would be used ( eth1 ) Then went to System/Administration/Network
		+	and there gave the address netmask and the default gateway for eth1 -- simple and no problem. The default GW is the gateway of the system. On laptop (grrr) and looks good: did not check yet if i can go to the internet from the Freerunner via eth1, wlan is OK
		+
		+	Carig Philippines --[[User:Frank\|frank]] 14:50, 17 June 2009 (UTC)

← Older revision		Revision as of 08:49, 16 June 2009
Line 132:		Line 132:
	sudo iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24<br>		sudo iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24<br>
	sudo echo 1 > /proc/sys/net/ipv4/ip_forward<br>		sudo echo 1 > /proc/sys/net/ipv4/ip_forward<br>
		+
		+	== no inet in interfaces ==
		+	I think the inet label in interfaces for eth1 (when openmoko is on eth1 like Ubuintu 9.04) causes the host (laptop) to try to make a connection to the internet via the openmoko device. This could be just the opposite of what you want. I'm not an expert on this but removing inet in interfaces for the openmoko devices fixed my problem. Any comments on this? [[User:Pander\|Pander]] 08:49, 16 June 2009 (UTC)

@@ Line 125: / Line 125: @@
 ==Script==
-sudo iptables -F
+sudo iptables -F <br>
-sudo ifconfig usb0 192.168.0.200 netmask 255.255.255.0
+sudo ifconfig usb0 192.168.0.200 netmask 255.255.255.0<br>
-sudo route add 192.168.0.202 usb0
+sudo route add 192.168.0.202 usb0<br>
-sudo iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
+sudo iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT<br>
-sudo iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
+sudo iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT<br>
-sudo iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
+sudo iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24<br>
-sudo echo 1 > /proc/sys/net/ipv4/ip_forward
+sudo echo 1 > /proc/sys/net/ipv4/ip_forward<br>