USB Networking - Revision history

Glenn: /* Openmoko Networking Setup */ update

2012-02-12T08:20:54Z

‎Openmoko Networking Setup: update

Ericehlers: /* Changing the Neo IP address */ clarify network restart command

2012-01-05T20:51:13Z

‎Changing the Neo IP address: clarify network restart command

Nschle85: /* Openmoko Networking Setup */

2011-12-19T21:56:47Z

‎Openmoko Networking Setup

Nschle85: /* My distro */

2011-12-19T21:56:05Z

‎My distro

Quix0r: Also a search on the target site didn't bring anything up

2011-10-29T09:21:04Z

Also a search on the target site didn't bring anything up

Quix0r: This link is also broken

2011-10-29T09:17:51Z

This link is also broken

Quix0r: Also this link is no longer working (more will come)

2011-10-29T09:15:45Z

Also this link is no longer working (more will come)

Quix0r: Broken link cleaned up

2011-10-29T09:13:56Z

Broken link cleaned up

Lozsui: /* My distro */

2011-10-28T22:58:07Z

‎My distro

Airon90: /* The more advanced way */

2011-09-18T22:31:53Z

‎The more advanced way

@@ Line 12: / Line 12: @@
 In order to communicate via TCP/IP to your FreeRunner, a basic understanding of the networking expectations is required.  Each end of the USB connection forms a LAN (local area network) segment, with the FreeRunner's USB networking device at one end (default 192.168.0.202) and your laptop or desktop at the other end (192.168.0.200 in this guide).
-{{Note|IP adresses are changed in new SHR-CORE images, phone 192.168.7.2 host: 192.168.7.1}}
+{{Note|IP adresses are changed in new SHR-CORE images after 110822, phone 192.168.7.2 host: 192.168.7.1}}
 Normally, your desktop machine will know how to reach the Internet, having had its gateway (the IP address of the machine or device which knows how to send packets to machines beyond your subnet) configured via DHCP or statically (probably via a router).  For the FreeRunner to reach the Internet, your desktop will have to be configured to route and masquerade (NAT) packets from it.

@@ Line 135: / Line 135: @@
 Like mentioned above, if the default Neo subnet 192.168.0.X is already used, it might be necessary to change the
 Neo [http://en.wikipedia.org/wiki/IP_address IP adress] and subnet.
-To achieve this, edit /etc/network/interfaces on the Neo (and reboot /etc/init.d/networking).
+To achieve this, edit /etc/network/interfaces on the Neo (and do "/etc/init.d/networking restart").
 In the following example the Neo will use the IP address 192.168.100.1 (instead of the default 192.168.0.202)
 within the network 192.168.100.X (instead of 192.168.0.X),

← Older revision		Revision as of 21:56, 19 December 2011
Line 11:		Line 11:

	In order to communicate via TCP/IP to your FreeRunner, a basic understanding of the networking expectations is required. Each end of the USB connection forms a LAN (local area network) segment, with the FreeRunner's USB networking device at one end (default 192.168.0.202) and your laptop or desktop at the other end (192.168.0.200 in this guide).		In order to communicate via TCP/IP to your FreeRunner, a basic understanding of the networking expectations is required. Each end of the USB connection forms a LAN (local area network) segment, with the FreeRunner's USB networking device at one end (default 192.168.0.202) and your laptop or desktop at the other end (192.168.0.200 in this guide).
		+
		+	{{Note\|IP adresses are changed in new SHR-CORE images, phone 192.168.7.2 host: 192.168.7.1}}

	Normally, your desktop machine will know how to reach the Internet, having had its gateway (the IP address of the machine or device which knows how to send packets to machines beyond your subnet) configured via DHCP or statically (probably via a router). For the FreeRunner to reach the Internet, your desktop will have to be configured to route and masquerade (NAT) packets from it.		Normally, your desktop machine will know how to reach the Internet, having had its gateway (the IP address of the machine or device which knows how to send packets to machines beyond your subnet) configured via DHCP or statically (probably via a router). For the FreeRunner to reach the Internet, your desktop will have to be configured to route and masquerade (NAT) packets from it.

← Older revision		Revision as of 21:56, 19 December 2011
Line 39:		Line 39:

	If all your approaches fail, you might want to consider using [http://knopper.net/knoppix/index-en.html Knoppix] (6.3 WorkedForMe(tm)) or another [http://distrowatch.com/dwres.php?resource=cd live distribution].		If all your approaches fail, you might want to consider using [http://knopper.net/knoppix/index-en.html Knoppix] (6.3 WorkedForMe(tm)) or another [http://distrowatch.com/dwres.php?resource=cd live distribution].
		+
		+	{{Note\|IP adresses are changed in new SHR-CORE images, phone 192.168.7.2 host: 192.168.7.1 so use theses adresses if you use the manual}}

	= Simple Manual Linux Configuration =		= Simple Manual Linux Configuration =

@@ Line 263: / Line 263: @@
 === Proxying with a UDP forwarder ===
-Another easy setup is using a UDP forwarder like the one from http://www.tapor.com/udpf/ - use it with the command"
+Another easy setup is using a UDP forwarder like the one from ('''BROKEN LINK REMOVED''') - use it with the command"
 <pre>udpf-elf -p=53-f=`awk '$1 == "nameserver"{print $2; exit(0);}' /etc/resolv.conf`:53</pre>

@@ Line 319: / Line 319: @@
 = OS or Distro Specific & Automatic Configuration =
-Based on [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] by Marcin 'Hrw' Juszkiewicz.
+Based on Hotplugging usbnet ('''BROKEN LINK REMOVED''') by Marcin 'Hrw' Juszkiewicz.
 These instructions should keep you from having to run the Simple Manual Linux Configuration every time you plug in and want to connect to an Openmoko device.  One run and then you're done!

@@ Line 622: / Line 622: @@
 Note: After reflashing the Neo you have to copy the "MAC Address" from "Auto usb0" into your new connection.
-Then, based on [http://sebastian-bergmann.de/index.php?url=archives/801-OpenMoko-Freerunner-and-Ubuntu.html#feedback these instructions], you should be able to setup masquerading by running the following commands on your Ubuntu PC:
+Then, based on these instructions ('''BROKEN LINK REMOVED'''), you should be able to setup masquerading by running the following commands on your Ubuntu PC:
 <pre>sudo iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT

@@ Line 963: / Line 963: @@
 == Slackware (tested with 12.1) ==
-Following is based on [http://www.enricozini.org/2008/tips/autodock-freerunner.html Enrico Zini's solution].
+Following is based on Enrico Zini's solution ('''404 LINK REMOVED''').
 Create a new udev rules file <tt>/etc/udev/rules.d/91-openmoko.rules</tt>:

@@ Line 36: / Line 36: @@
 === My distro ===
-There are many differences between distributions, both on the phone and an the desktop. Also within a single distribution there can be big changes over time, so remember that solutions provided here might not always exactly match your situation.
+There are many differences between distributions, both on the phone and on the desktop. Also within a single distribution there can be big changes over time, so remember that solutions provided here might not always exactly match your situation.
 If all your approaches fail, you might want to consider using [http://knopper.net/knoppix/index-en.html Knoppix] (6.3 WorkedForMe(tm)) or another [http://distrowatch.com/dwres.php?resource=cd live distribution].

@@ Line 83: / Line 83: @@
 If the previously described simple approach does not work, you may try the more complex one.
-<pre>iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
+<pre>
-sysctl -w net.ipv4.ip_forward=1
+sudo iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
-ip addr add 192.168.0.200/24 dev usb0</pre>
+sudo sysctl -w net.ipv4.ip_forward=1
 If your Internet connection is also in the range 192.168.0.x then instead you might want to use only:
-<pre>ip addr add 192.168.0.200/28 dev usb0</pre>
+<pre>sudo ip addr add 192.168.0.200/28 dev usb0</pre>
 (This will just map the net from 192.168.0.192 to 192.168.0.207 onto usb0. If you get the error 'Cannot find device "usb0"', double-check that your FreeRunner is turned on and connected by USB. Ensure also that the uhci_hcd module is loaded on your PC. If that doesn't work, try unplugging and replugging the USB cable.)
@@ Line 95: / Line 97: @@
 And in this case you should enable ARP proxy on internet facing interface INSTEAD of using iptables:
-<pre>sysctl net.ipv4.conf.eth2.proxy_arp=1</pre>
+<pre>sudo sysctl net.ipv4.conf.eth2.proxy_arp=1</pre>
 This assuming that eth2 is connected to ISP.
 Then
-<pre>ip link set usb0 up</pre>
+<pre>sudo ip link set usb0 up</pre>
 or (deprecated)
-<pre>ifconfig usb0 up</pre>
+<pre>sudo ifconfig usb0 up</pre>
 Then (ideally, not as root):