Re: USB Networking troubles

2008-08-09 Thread Olivier Berger
"michael cole" <[EMAIL PROTECTED]> writes: > > Perhaps someone with editing rights to the networking page can add a couple > of lines to make clear the need for distinct networks in specifying the > setup. Why not change that yourself... it's a wiki. You too can get these edit rights (unless regi

Re: USB Networking troubles

2008-08-09 Thread michael cole
I put a line in yesterday pointing out that the networks need to be > distinctly different, but it seems to have gone again :-) > > Ah, the joys of community editing. A pointer to this thread (specifically your description of the larger network picture and what the USB setup needs to accomplish) wo

Re: USB Networking troubles

2008-08-09 Thread Zack Mollusc
michael cole wrote: > Andrew, > > I'll make the netmask changes you suggest. > > Further to my comments above re: the USB networking page @ openmoko. > My issue could have been avoided if the networking page made clear > that the Freerunner--Desktop connection is on a different network than > the L

Re: USB Networking troubles

2008-08-08 Thread michael cole
Andrew, I'll make the netmask changes you suggest. Further to my comments above re: the USB networking page @ openmoko. My issue could have been avoided if the networking page made clear that the Freerunner--Desktop connection is on a different network than the LAN the desktop uses to access the

Re: USB Networking troubles

2008-08-08 Thread Andrew C. Dingman
On Fri, 2008-08-08 at 06:32 -0400, michael cole wrote: > First thanks to all for replying. > > These changes worked. Glad it helped. I hope the IP routing mini-lecture made clear *why* :) > So on my Freerunner /etc/network/interfaces includes: > > # Ethernet/RNDIS gadget (g_ether) > # ... or on

Re: USB Networking troubles

2008-08-08 Thread michael cole
Hi Andrew, First thanks to all for replying. These changes worked. The essence of the change is rather simple -- move the Freerunner to a different network from the LAN's netwrok 1) (in my case from 192.168.1.202 to 192.168.2.202) 2) allow the desktop machine to talk to 192.168.2.202 3) do the

Re: USB Networking troubles

2008-08-07 Thread Andrew C. Dingman
> This is posted with the hope someone can look at the current state of > my Freerunner connection to the desktop and just see something that is > not right. I am sure the answer is simple and am reluctant to ask the > community for non-FR help but perhaps others are struggling with > similar netwo

Re: USB Networking troubles

2008-08-07 Thread michael cole
Hi Timo: Here is the output from print-net-settings (run on desktop): = print-net-settings output # ./print-net-settings + LC_ALL=C + date Thu Aug 7 22:26:53 UTC 2008 + hostname armstrong + for i in /proc/sys/net/ipv4/ip_forward '/proc/sys/net/ipv4/conf/*/proxy_arp' '/proc/sys/n

Re: USB Networking troubles

2008-08-07 Thread arne anka
debian/unstable amd64, 2.6.26. my /etc/network/interfaces says for usb networking allow-hotplug usb0 iface usb0 inet static address 192.168.0.200 netmask 255.255.255.0 network 192.168.0.0 post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24

Re: USB Networking troubles

2008-08-07 Thread phillip tribble
On Thu, Aug 7, 2008 at 2:54 PM, Timo Juhani Lindfors <[EMAIL PROTECTED]>wrote: > "michael cole" <[EMAIL PROTECTED]> writes: > > This is not a Freerunner issue -- I am able to ssh into FR using UBS > > networking but I simply cannot get the Freerunner to ping anything > > other than the desktop it

Re: USB Networking troubles

2008-08-07 Thread Timo Juhani Lindfors
"michael cole" <[EMAIL PROTECTED]> writes: > This is not a Freerunner issue -- I am able to ssh into FR using UBS > networking but I simply cannot get the Freerunner to ping anything > other than the desktop it is connected to. The issue almost certainly > has something to do with the iptables/nat

USB Networking troubles

2008-08-07 Thread michael cole
This is not a Freerunner issue -- I am able to ssh into FR using UBS networking but I simply cannot get the Freerunner to ping anything other than the desktop it is connected to. The issue almost certainly has something to do with the iptables/nat setup on the desktop computer. I've followed the