working SIM install, network problems
rdmyers at mtpalomar.net
Thu Dec 4 16:19:17 CET 2008
On Dec 4, 2008, at 3:57 AM, clare johnstone wrote:
> On Thu, Dec 4, 2008 at 7:24 AM, Rodney Myers <rdmyers at mtpalomar.net>
>> Debian stable, and neorunner
>> I have a semi-functioning Neo right now, thanks to the Hackable:1
>> I have changed all instances, that I find, from 192.168.0.* to
>> for my lan.
>> I've followed this wiki page for networking debian;
>> 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
> 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)
> /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/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
> iptables -A INPUT -s 192.168.0.200 -i eth+ -d 192.168.0.202 -j
> iptables -A INPUT -s 192.168.2.0/24 -i eth+ -d 192.168.0.202 -j
> iptables -A INPUT -s 192.168.2.0/24 -i eth+ -d 192.168.2.0/24 -j
> 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 root at 192.168.0.202
> 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
> 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,
Thanks for the tip(s). The wiki is ponderous, but gleaned what i
hoped was a working set of instructions.
I have the above printed out, and may re-install the image(s) to get a
default install and try again.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 194 bytes
Desc: This is a digitally signed message part
Url : http://lists.openmoko.org/pipermail/community/attachments/20081204/06747b74/attachment.pgp
More information about the community