On Thu, Dec 4, 2008 at 7:24 AM, Rodney Myers <[EMAIL PROTECTED]> wrote: > Debian stable, and neorunner > > I have a semi-functioning Neo right now, thanks to the Hackable:1 folkes > (http://www.hackable1.org/) > > I have changed all instances, that I find, from 192.168.0.* to 192.168.1.*, > for my lan. > > I've followed this wiki page for networking debian; > > http://wiki.openmoko.org/wiki/USB_Networking#Debian.2C_Ubuntu_and_others > > also changing the 192.168.0.* address'. >
Hello Rodney, I really hesitate to say anything, being overcome with admiration of anyone who can follow that wiki page that you quote. It looks far too complex for normal humans and far too automated for someone who is just starting. If you dont agree with that then best to ignore what I have to say. I have tried many images. One of the first things that becomes obvious is that attempts to change the mind of the Neo to use other than the network 192.168.0 will lead to serious frustration. So I accept that. My home network is equally determined to be 192.168.2 When I want to comunicate from my PC to the Neo via the USB, I join them with the USB cable and on the PC run this little script ( as root) #!/bin/sh /sbin/ifconfig usb0 192.168.0.200 netmask 255.255.255.0 /sbin/route add -host 192.168.0.202/32 dev usb0 Then I run this one #!/bin/sh /bin/echo 1 > /proc/sys/net/ipv4/ip_forward iptables -F iptables -A INPUT -s 192.168.0.202 -i usb0 -d 192.168.0.200 -j ACCEPT iptables -A INPUT -s 192.168.0.200 -i eth+ -d 192.168.0.202 -j ACCEPT iptables -A INPUT -s 192.168.2.0/24 -i eth+ -d 192.168.0.202 -j ACCEPT iptables -A INPUT -s 192.168.2.0/24 -i eth+ -d 192.168.2.0/24 -j ACCEPT iptables -A FORWARD -s 192.168.0.202 -i usb0 -d 192.168.2.0/24 -o eth+ -j ACCEPT iptables -A FORWARD -s 192.168.2.0/24 -i eth+ -d 192.168.0.202 -o usb0 -j ACCEPT iptables -A OUTPUT -d 192.168.2.0/24 -o eth+ -j ACCEPT iptables -A OUTPUT -d 192.168.0.202 -o usb0 -j ACCEPT iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 At this stage I can do ssh [EMAIL PROTECTED] Normally it will argue and I have to edit the file ~/.ssh/known hosts by removing the line it is objecting to. It will then agree to the ssh. Most people automate that process to avoid the editing etc but that is a matter of taste only. Once you have things going without trouble you can automate a lot of things. good luck, clare _______________________________________________ Openmoko community mailing list [email protected] http://lists.openmoko.org/mailman/listinfo/community
