Hmmm, sent this on thursday, but seems it never made it to the list, so i'm resending it, sorry if it arrives twice ;)
yoyo On Thu, Jun 16, 2011 at 12:48:51AM +0300, elmar bucher wrote: > Hi Yoyo, > > At least a step I cam further... > > > Why not connect it through the usb? It might be slower than wifi, but > > much more stable and predictable... It's on wiki: > > http://wiki.openmoko.org/wiki/USB_Networking > > I followed the USB Networking instruction. > elm@firebolt:~$ sudo ip address add 192.168.0.200/24 dev eth1 > elm@firebolt:~$ sudo ip link set dev eth1 up > elm@firebolt:~$ sudo route add -host 192.168.0.202 dev eth1 is the last line needed because neo uses the same subnet as your regular network? If so, i would try to move neo to some other subnet, just to be sure the prob. isn't there.... ie change 192.168.0.. to say 192.168.47... in /etc/network/interfaces and reboot/restart eth0 > > *** form the desktop ping and ssh to the phone works YEAH!*** > elm@firebolt:~$ ping 192.168.0.202 > PING 192.168.0.202 (192.168.0.202) 56(84) bytes of data. > 64 bytes from 192.168.0.202: icmp_seq=1 ttl=64 time=1.15 ms > 64 bytes from 192.168.0.202: icmp_seq=2 ttl=64 time=1.20 ms > 64 bytes from 192.168.0.202: icmp_seq=3 ttl=64 time=1.26 ms > 64 bytes from 192.168.0.202: icmp_seq=4 ttl=64 time=1.57 ms > 64 bytes from 192.168.0.202: icmp_seq=5 ttl=64 time=1.62 ms > > --- 192.168.0.202 ping statistics --- > 5 packets transmitted, 5 received, 0% packet loss, time 3997ms > rtt min/avg/max/mdev = 1.150/1.365/1.627/0.197 ms > > elm@firebolt:~$ ssh [email protected] > [email protected]'s password: > Last login: Tue Jan 4 12:33:47 2000 from 192.168.0.200 > root@om-gta02 ~ # > > > *** form the phone ping to the phone works too (even the time looks > freaking fast), but ssh to the desktop does not work, even I'm sure > the firewall is down *** > root@om-gta02 ~ # ping 192.168.0.200 > PING 192.168.0.200 (192.168.0.200): 56 data bytes > 64 bytes from 192.168.0.200: seq=0 ttl=64 time=0.000 ms > 64 bytes from 192.168.0.200: seq=1 ttl=64 time=0.000 ms > 64 bytes from 192.168.0.200: seq=2 ttl=64 time=0.000 ms > 64 bytes from 192.168.0.200: seq=3 ttl=64 time=0.000 ms > 64 bytes from 192.168.0.200: seq=4 ttl=64 time=0.000 ms > ^C > --- 192.168.0.200 ping statistics --- > 5 packets transmitted, 5 packets received, 0% packet loss > round-trip min/avg/max = 0.000/0.000/0.000 ms > root@om-gta02 ~ # thats really weird ;) root@om-gta02 ~ # ping 192.168.0.202 PING 192.168.0.202 (192.168.0.202): 56 data bytes 64 bytes from 192.168.0.202: seq=0 ttl=64 time=0.907 ms 64 bytes from 192.168.0.202: seq=1 ttl=64 time=0.538 ms 64 bytes from 192.168.0.202: seq=2 ttl=64 time=0.448 ms 64 bytes from 192.168.0.202: seq=3 ttl=64 time=0.448 ms event PCs aren't that fast (cca 0.040ms on mydesktop ;) > > root@om-gta02 ~ # ssh [email protected] > ssh: connect to host 192.168.0.200 port 22: Connection refused > hmm, i'd double check that your ssh is really running, that your firewall is correct ;) and that sshd is listenning on all addresses/interfaces (ie 0.0.0.0) and not only your interface/address you use for your local network... tabletka ~ # netstat -lpn | grep :22 tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2985/sshd tcp6 0 0 :::22 :::* LISTEN 2985/sshd it's pretty weird that desktop -> moko connection works and reverse not, as even for the first one, packets have to be routed from moko to desktop... unless there's some firewall stuff that allows only outgoing connections on the desktop or something like that... > > > >> > # ip addr > >> quite some output > >> 1: lo (loopback at inet 127.0.0.1/8) > >> 2: usb0 [...] inet 192.168.0.202/24 brd 192.168.0.255 > >> 3: eth0 [...] inet 192.168.0.42/24 brd 192.168.0.255 > > > > hmm, your wifi uses the same subnet as the usbconnection. > > surprisingly this have change: > root@om-gta02 ~ # ip addre > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > 2: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast > state UP qlen 1000 > link/ether 00:1f:11:01:a9:a5 brd ff:ff:ff:ff:ff:ff > inet 192.168.0.202/24 brd 192.168.0.255 scope global usb0 > inet6 fe80::21f:11ff:fe01:a9a5/64 scope link > valid_lft forever preferred_lft forever you didn't start wifi, so it isn't turned on and the interface isn't even there... > > > What does > > route -n > root@om-gta02 ~ # route -n > Kernel IP routing table > 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 8 0 0 usb0 > > > > but if you have working connection from desktop to neo, you just need to run > > iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -j MASQUERADE echo 1 > > >/proc/sys/net/ipv4/ip_forward > > > > on the desktop, shr should be by default set up for the usb connection, > > unless you start up some wifi connection app which would mess it up, > > however this is what it looks like here (on the moko, wifi turned off): > > Do I still have to run > iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -j MASQUERADE echo 1 > >/proc/sys/net/ipv4/ip_forward ? heh, some formatting issue, they should be 2 commands... but anyway... you need them to make your desktop act as gateway/NAT for the neo, ie to forward packets to the outside network and back.... but they are not needed for the simple neo <-> desktop connection > > Still wonder if the problem is in the shr installation. I just flashed > freerunner whit shr, to be able to install gentoo. I never properly > used it to phone or something. The pre-flashed os (om2008?) have not > even had a command line. But there the phone was working. That I > tested. i have a bit more than half a year old shr, never had a problem with the usb connection... bye yoyo > > Well, that's it for today. > Thanks! And good night. > > So long, Elmar >
