Re: [default] no route past ssh'd computer
On Dec 28, 2008, at 2:44 AM, arne anka wrote: only a few weeks ago was the recurrent thread about the issue, even regarding the living in the same subnet -- please check the archives before asking! And you don't think I have read the mail list/archives? Would I ask, if the suggested items would have helped? Which is exactly why I have not posted until now. Again, thank you for pointing out the obvious. PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[default] no route past ssh'd computer
Debian stable OM default w/updates. OM is not my daily phone, yet. My debian machine is 192.168.0.101, the default GW is 192.168.0.1 Was able to get the default install onto the net, and grab updates a few weeks ago. Right after I did the update, now I am not able to get back onto the net. my OM /etc/network/interfaces, options, ifconfig, netstat -er cat /etc/network/interfaces # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface auto lo iface lo inet loopback # Wireless interfaces iface wlan0 inet dhcp wireless_mode managed wireless_essid any iface atml0 inet dhcp # Wired or wireless interfaces iface eth0 inet dhcp iface eth1 inet dhcp # Ethernet/RNDIS gadget (g_ether) # ... or on host side, usbnet and random hwaddr auto usb0 iface usb0 inet static address 192.168.0.202 netmask 255.255.255.0 network 192.168.0.0 gateway 192.168.0.1 up echo nameserver 192.168.0.1 /etc/resolv.conf cat /etc/network/options ip_forward=no spoofprotect=yes syncookies=no ifconfig loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:29 errors:0 dropped:0 overruns:0 frame:0 TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3120 (3.0 KiB) TX bytes:3120 (3.0 KiB) usb0 Link encap:Ethernet HWaddr 4A:2B:DF:D4:5C:14 inet addr:192.168.0.202 Bcast:192.168.0.255 Mask: 255.255.255.0 inet6 addr: fe80::482b:dfff:fed4:5c14/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1201 errors:0 dropped:0 overruns:0 frame:0 TX packets:740 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:95353 (93.1 KiB) TX bytes:91729 (89.5 KiB) netstat -er Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 * 255.255.255.0 U 0 0 0 usb0 default 192.168.0.1 0.0.0.0 UG0 0 0 usb0 PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [default] no route past ssh'd computer
On Dec 27, 2008, at 4:29 PM, William Kenworthy wrote: I moved to the 192.168.0.* to get connected. I could not get it working the other way. Just configure the freerunner for a different IP and have the linux box nat it out onto the network. On my network, I subnet the 192.168.0 into 192.168.0.0/30 and 192.168.0.192/27 so they stay separate and I dont have to worry about the ADSL modem - more problematic than the FR to stay configured. Permanent fix is to move your network away from 192.168.0 altogether and curse the stupidity of whoever chose 192.168.0 in the first place :) BillK On Sat, 2008-12-27 at 16:08 -0800, Rodney Myers wrote: Debian stable OM default w/updates. OM is not my daily phone, yet. My debian machine is 192.168.0.101, the default GW is 192.168.0.1 Was able to get the default install onto the net, and grab updates a few weeks ago. Right after I did the update, now I am not able to get back onto the net. my OM /etc/network/interfaces, options, ifconfig, netstat -er cat /etc/network/interfaces # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface auto lo iface lo inet loopback # Wireless interfaces iface wlan0 inet dhcp wireless_mode managed wireless_essid any iface atml0 inet dhcp # Wired or wireless interfaces iface eth0 inet dhcp iface eth1 inet dhcp # Ethernet/RNDIS gadget (g_ether) # ... or on host side, usbnet and random hwaddr auto usb0 iface usb0 inet static address 192.168.0.202 netmask 255.255.255.0 network 192.168.0.0 gateway 192.168.0.1 up echo nameserver 192.168.0.1 /etc/resolv.conf cat /etc/network/options ip_forward=no spoofprotect=yes syncookies=no ifconfig loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:29 errors:0 dropped:0 overruns:0 frame:0 TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3120 (3.0 KiB) TX bytes:3120 (3.0 KiB) usb0 Link encap:Ethernet HWaddr 4A:2B:DF:D4:5C:14 inet addr:192.168.0.202 Bcast:192.168.0.255 Mask: 255.255.255.0 inet6 addr: fe80::482b:dfff:fed4:5c14/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1201 errors:0 dropped:0 overruns:0 frame:0 TX packets:740 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:95353 (93.1 KiB) TX bytes:91729 (89.5 KiB) netstat -er Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 * 255.255.255.0 U 0 0 0 usb0 default 192.168.0.1 0.0.0.0 UG0 0 0 usb0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- William Kenworthy bi...@iinet.net.au Home in Perth! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Wifi - wep or wpa enabled
Default install. Does the wifi work only with wpa? or does it also work with wep? My internal wifi is wep enabled only, and I cannot get the phone to recognize the key. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: working SIM install, network problems - FIXED
Finally have a phone that connects (or did connect before I updated it) to the internet. I actually renumbered my LAN to make the phone work. Since I ran the update on the phone, default install, connecting back to the internet has been broken. I did read in the list that there was a one line fix for it. many thanks to all that helped me out in this adventure. PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD boot, mounting phone
On Dec 10, 2008, at 11:28 AM, Marco Trevisan (Treviño) wrote: Rodney Myers wrote: On Dec 8, 2008, at 2:55 AM, arne anka wrote: doesn't your /etc/fstab contain an entry for /mnt/flash or so? from installing debian on sd i got /dev/mtdblock6 /mnt/flash jffs2 defaults,noatime,noauto 0 2 which mounts the internal flash -- not sure, though, how stable the device name is ... I think I did see something like that. I will look later, and see what is there. Yes the task can be done by using: mount -t jffs2 /dev/mtdblock6 /media/mount-point It was mounted, and I was able to edit the phone itself, back to as original as I could remember. I was able to ssh into the phone itself (finally), but have been unable to see anything (debian computer I am ssh'ing from, or the net). Thats my next project. Thanks for the tips. PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD boot, mounting phone
On Dec 8, 2008, at 2:29 AM, Andy Green wrote: Somebody in the thread at some point said: | This is not listed in the wiki. | | I can successfully boot from the SD card, using Hackable:1 (thanks | folkes), and ssh into the SD card (thanks Arne, clare, Christopher Joel). | | Now that all of this can happen, how do I mount the phone, so I can edit | the phone back to default? What do you mean by mount the phone? Which filesystem are you thinking about mounting and editing? If it is one on the SD card, then the best thing to do is pop the SD Card out and meddle with it on a PC via a card reader. - -Andy I'm booting from the SD card, attempting to unscrew the phone. If I can mount the phone, I can un-edit the /etc/network/interfaces file so I can ssh back into the phone, not the SD card. PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD boot, mounting phone
On Dec 8, 2008, at 2:55 AM, arne anka wrote: Now that all of this can happen, how do I mount the phone, so I can edit the phone back to default? doesn't your /etc/fstab contain an entry for /mnt/flash or so? from installing debian on sd i got /dev/mtdblock6 /mnt/flash jffs2 defaults,noatime,noauto 0 2 which mounts the internal flash -- not sure, though, how stable the device name is ... I think I did see something like that. I will look later, and see what is there. Thanks PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: working SIM install, network problems - update
On Dec 6, 2008, at 9:41 PM, Joel Newkirk wrote: On Sat, 6 Dec 2008 20:00:36 -0800, Rodney Myers [EMAIL PROTECTED] wrote: On Dec 4, 2008, at 3:57 AM, clare johnstone wrote: 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 Thank you for your scripts. I think I edited them to correlate them to my network; 192.168.1.0/24 I now can ssh into the OM, and set the time to my local America/ Los_Angeles. One step ahead. I can ping the debian machine, and everything on my lan, but nothing outside the lan. [snip] My interpretation of ths scripts; cat bin/OM-config #!/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 [EMAIL PROTECTED]:~$ cat bin/om-network #!/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.1.0/24 -i eth+ -d 192.168.0.202 -j ACCEPT iptables -A INPUT -s 192.168.1.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.1.0/24 -i eth+ -d 192.168.0.202 -o usb0 -j ACCEPT iptables -A OUTPUT -d 192.168.1.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 Is this the complete firewall script?? There's several things missing, and a couple possible errors. (since you only posted ifconfig info for usb0 on the host I can't tell if the 192.168.2.0/24 are typos, or correct with missing rules) Now, since you say you can ping everything on the LAN, and have only the two FORWARD rules listed, I'm going to assume a typo and that you have just 192.168.1.0/24 in play. No. I took what Clare had written, and was attempting to get working with my LAN. My lan is 192.168.1.*/24, not 192.168.2.* (probably a typo, but want to make sure) Correct, in pinging everything on my lan. Once I was ssh'd into the OM, I could ping ever computer on my lan, from the router, wireless access point, the 2 wireless computers, and the debian (wired) computer. A few points: You have rules to accept INPUT from 192.168.1.0/24 for destIP 192.168.0.202, but this should never be the case - INPUT is only packets with an IP on 'this' machine as destination, OUTPUT is packets from 'this' machine, FORWARD is packets from somewhere else TO somewhere else that are just being FORWARDed by 'this' machine. iptables -F flushes all rules from the 'filter' table's chains - INPUT, OUTPUT and FORWARD. But it doesn't touch the 'nat' table (PREROUTING, POSTROUTING, and OUTPUT chains) unless you separately invoke iptables -t nat -F, and it doesn't set/change the default chain policies. I'm not sure if this is really what you want to do anyway - doesn't the host already have a set of firewall rules in place? If so you're likely better off adding rules to permit the FR instead of flushing everything that's already in place. Presuming the host communicates fine to begin with, instead of ALL of the iptables commands above, try these (NOTE there's NOT an 'iptables - F' to flush the existing rules, we're just appending additional rules): iptables -A INPUT -i usb0 -s 192.168.0.202 -j ACCEPT iptables -A FORWARD -i usb0 -s 192.168.0.202 -j ACCEPT iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT iptables -A OUTPUT -o usb0 -j ACCEPT iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -j MASQUERADE The first rule lets the FR talk to the host, the second lets it talk /through/ the host to whatever else is reachable, the third lets the response to that traffic back through to the FR (we're invoking the connection-tracking state engine where replies, like web pages when you browse, are ESTABLISHED connections, while RELATED connections includes things like ICMP dest unreachable being 'related' to an attempted connection, FTP data being 'related' to FTP control port 21, RTP related to SIP for VOIP, etc), fourth lets the host talk to the FR, fifth NATs any packets from the FR that are going out on the LAN so that they appear to be from the host, and replies will route correctly back to the host. No firewall running on the debian machine. At this time. The OUTPUT rule should only be needed if your host has a REALLY tight firewall: often the OUTPUT chain is left in an 'allow all' state, with few or no rules and 'ACCEPT' policy. (iptables -p OUTPUT ACCEPT sets this, the policy is listed after
Re: working SIM install, network problems - update (2X)
On Dec 7, 2008, at 2:06 PM, Rodney Myers wrote: Thanks. I will experiment a bit more. This is what I got to work, many thanks cat bin/OM-config #!/bin/sh sudo /sbin/ifconfig usb0 192.168.0.200 netmask 255.255.255.0 sudo /sbin/route add -host 192.168.0.202/32 dev usb0 [EMAIL PROTECTED]:~$ cat bin/om-network-test #!/bin/sh sudo /bin/echo 1 /proc/sys/net/ipv4/ip_forward sudo iptables -A INPUT -i usb0 -s 192.168.0.202 -j ACCEPT sudo iptables -A FORWARD -i usb0 -s 192.168.0.202 -j ACCEPT sudo iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT sudo iptables -A OUTPUT -o usb0 -j ACCEPT sudo iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -j MASQUERADE I was able to get the debian updated. Yeah. PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: working SIM install, network problems
On Dec 4, 2008, at 2:04 AM, arne anka wrote: any help would be greatly appreciated. well, it would be _really_ helpful, if you could specify what your problem is and how it manifests itself. When I plug the OM into the debian machine, i know it gets connected. the output of dmesg says so. From both the Neo or the debian machine, pinging the other does not work, no packets returned. I can take SD card, mount it to the debian machine and edit all necessary files, then reinsert into the OM to get it to boot. PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: working SIM install, network problems
On Dec 4, 2008, at 3:57 AM, clare johnstone wrote: 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 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. PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: How to remove microSD card
On Dec 3, 2008, at 11:05 AM, Franky Van Liedekerke wrote: Ok, so I'm feeling totally moronic now ... I'm pretty sure I entered my microSD card some 3 months ago, but I can't seem to figure out how to remove it again ... some howto for a gta02? I can't seem to find any lever or pressure thingie to get it to pop open there and the info mentioned on http://wiki.openmoko.org/wiki/Getting_Started_with_your_Neo1973 (gently sliding) doesn't apply, nothing slides ... Franky There is a space at the top of the SD card. put your finger nail in there and pull up gently. I just figured this out as well. PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
working SIM install, network problems
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'. even though I have the Neo debian machines configured. not sure what log files would be helpful, but it the output from the debian /var/log/syslog; Dec 3 14:00:34 riverside kernel: usb 2-2: new full speed USB device using uhci_hcd and address 13 Dec 3 14:00:35 riverside kernel: usb 2-2: configuration #1 chosen from 2 choices Dec 3 14:00:35 riverside kernel: usb0: register 'cdc_ether' at usb-:00:10.1-2, CDC Ethernet Device, 8e:0b:55:07:0b:6c Dec 3 14:00:35 riverside NetworkManager: debug info^I[1228341635.150394] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/ usb_device_1457_5122_noserial'). Dec 3 14:00:35 riverside NetworkManager: debug info^I[1228341635.151091] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/ usb_device_1457_5122_noserial_if1'). Dec 3 14:00:35 riverside NetworkManager: debug info^I[1228341635.244100] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/ usb_device_1457_5122_noserial_if0'). Dec 3 14:00:35 riverside NetworkManager: debug info^I[1228341635.291089] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/net_8e_0b_55_07_0b_6c'). Dec 3 14:00:35 riverside NetworkManager: debug info^I[1228341635.310031] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/ usb_device_1457_5122_noserial_usbraw'). Dec 3 14:00:35 riverside avahi-daemon[2868]: New relevant interface usb0.IPv4 for mDNS. Dec 3 14:00:35 riverside avahi-daemon[2868]: Joining mDNS multicast group on interface usb0.IPv4 with address 192.168.1.200. Dec 3 14:00:35 riverside avahi-daemon[2868]: Registering new address record for 192.168.1.200 on usb0. Dec 3 14:00:45 riverside kernel: usb0: no IPv6 routers present any help would be greatly appreciated. thank you PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
working SIM install, network problems
Sorry if this is a duplicate. I never saw it returned on the mail llsi 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'. even though I have the Neo debian machines configured. not sure what log files would be helpful, but it the output from the debian /var/log/syslog; Dec 3 14:00:34 riverside kernel: usb 2-2: new full speed USB device using uhci_hcd and address 13 Dec 3 14:00:35 riverside kernel: usb 2-2: configuration #1 chosen from 2 choices Dec 3 14:00:35 riverside kernel: usb0: register 'cdc_ether' at usb-:00:10.1-2, CDC Ethernet Device, 8e:0b:55:07:0b:6c Dec 3 14:00:35 riverside NetworkManager: debug info^I[1228341635.150394] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/ usb_device_1457_5122_noserial'). Dec 3 14:00:35 riverside NetworkManager: debug info^I[1228341635.151091] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/ usb_device_1457_5122_noserial_if1'). Dec 3 14:00:35 riverside NetworkManager: debug info^I[1228341635.244100] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/ usb_device_1457_5122_noserial_if0'). Dec 3 14:00:35 riverside NetworkManager: debug info^I[1228341635.291089] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/net_8e_0b_55_07_0b_6c'). Dec 3 14:00:35 riverside NetworkManager: debug info^I[1228341635.310031] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/ usb_device_1457_5122_noserial_usbraw'). Dec 3 14:00:35 riverside avahi-daemon[2868]: New relevant interface usb0.IPv4 for mDNS. Dec 3 14:00:35 riverside avahi-daemon[2868]: Joining mDNS multicast group on interface usb0.IPv4 with address 192.168.1.200. Dec 3 14:00:35 riverside avahi-daemon[2868]: Registering new address record for 192.168.1.200 on usb0. Dec 3 14:00:45 riverside kernel: usb0: no IPv6 routers present any help would be greatly appreciated. thank you PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Creating a distro on a sim card
In my ongoing quest, I did find out I was not actually booting from the SD device, so I have printed out the instructions, and for the past week attempting to get the device configured and booting properly So far this is what I am accomplishing Still attempting to get my OM to boot from the SD card. If I fillow the instructions at http://wiki.openmoko.org/wiki/Booting_from_SD#Prepare_the_SD_card and format the 1st partition vfat, I get this error when booting (using magnifying glass); [2.68000] mmcblk0: error -84 sending read/write command [2.68000] buffer I/O error on device mmcblk0, logical block 0 [2.68500] mmcblk0: error -110 sending read/write command [2.69000] buffer I/O error on device mmcblk0, logical block 0 [8.15000] kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2) if I change 1st partition to ext2, I get this error; unable to read image uImage.bin and then pops back into the boot menu I'm at a loss to figure this out. Anymore help would be greatly appreciated PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Creating a distro on a sim card
On Nov 29, 2008, at 1:04 PM, Paul wrote: and format the 1st partition vfat, I get this error when booting (using magnifying glass); [2.68000]mmcblk0: error -84 sending read/write command [2.68000]buffer I/O error on device mmcblk0, logical block 0 [2.68500]mmcblk0: error -110 sending read/write command [2.69000]buffer I/O error on device mmcblk0, logical block 0 [8.15000]kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2) What did you do to the 2nd partition? You need to format that ext2, and put a rootfs on that. Judging from the last error message, there is no defined or formated 2nd partition. Paul 2nd partition is an ext2 partition with the rootfs.*.gz untarred as per the wiki. I just checked again, and this is what I have for the SD card; I'm doing this on a Debian Stable machine /dev/sdd1 7.8M 1.9M 5.5M 26% /home/rodney/MokoKernel /dev/sdd2 949M 157M 745M 18% /home/rodney/Moko fdisk -l /dev/sdd Disk /dev/sdd: 1019 MB, 1019216384 bytes 14 heads, 45 sectors/track, 3159 cylinders Units = cylinders of 630 * 512 = 322560 bytes Device Boot Start End Blocks Id System /dev/sdd1 1 268167+ 6 FAT16 /dev/sdd2 273159 986895 83 Linux ls -la MokoKernel/ total 1872 drwxr-xr-x 2 root root 16384 1969-12-31 16:00 . drwxr-xr-x 81 rodney rodney4096 2008-11-29 11:18 .. -rwxr-xr-x 1 root root 1894716 2008-11-29 13:48 uImage.bin ls -la Moko/ total 84 drwxr-xr-x 18 root root4096 2008-09-15 17:24 . drwxr-xr-x 81 rodney rodney 4096 2008-11-29 11:18 .. drwxr-xr-x 2 root root4096 2008-11-29 12:12 bin drwxr-xr-x 2 root root4096 2008-09-15 17:25 boot drwxr-xr-x 2 root root4096 2008-08-06 23:27 dev drwxr-xr-x 46 root root4096 2008-11-29 12:12 etc drwxr-xr-x 3 root root4096 2008-09-15 17:23 home drwxr-xr-x 4 root root4096 2008-08-07 15:26 lib drwx-- 2 root root 16384 2008-11-29 12:11 lost+found drwxr-xr-x 10 root root4096 2008-09-15 17:23 media drwxr-xr-x 3 root root4096 2008-11-29 12:12 mnt drwxr-xr-x 3 root root4096 2008-08-06 23:28 opt drwxr-xr-x 2 root root4096 2008-08-06 23:27 proc drwxr-xr-x 2 root root4096 2008-11-29 12:12 sbin drwxr-xr-x 2 root root4096 2008-08-06 23:27 sys drwxrwxrwt 2 root root4096 2008-08-06 23:27 tmp drwxr-xr-x 10 root root4096 2008-08-06 23:27 usr drwxr-xr-x 7 root root4096 2008-08-06 23:26 var Bloody wierd. Mounted, looked at, umounted, the SD card, reinserted into the, and it appears to be boot, but the IP address I edited into the /etc/network/interfaces card. does not appear to have taken. This is why it is so frustrating. One time, nothing works, then things start working PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Creating a distro on a sim card
On Nov 22, 2008, at 7:28 PM, William Kenworthy wrote:
Have a look at /etc/defaults/dropbear - does it lock ssh to usb0 only?
BillK
This is what is my /etc/defaults/dropbear says
DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS=[ /]+ } /inet /
{ print $3 }'`:22
PGP.sig
Description: This is a digitally signed message part
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Creating a distro on a sim card
On Nov 22, 2008, at 2:54 PM, Christian Adams wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi are you sure 192.168.1.202 is really the ip of your freerunner? from reading the pingtimes i would think you ping your local interface not your freerunner which would have ping-times around 1 to 5 ms or so .. ciao, christian (morlac) adams If I unplug the phone, then it says no route to host, so I am pretty sure it is the phone, and I know what the /etc/network/interface states Am 22.11.2008 um 23:40 schrieb Rodney Myers: ssh [EMAIL PROTECTED] The authenticity of host '192.168.1.202 (192.168.1.202)' can't be established. RSA key fingerprint is 75:c6:91:b7:60:a9:16:b1:19:ed: 5a:c7:2f:d3:39:c4. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.1.202' (RSA) to the list of known hosts. [EMAIL PROTECTED]'s password: Permission denied, please try again. [EMAIL PROTECTED]'s password: Permission denied, please try again. [EMAIL PROTECTED]'s password: Permission denied (publickey,password). what happens when you enter your root-pw here? ;) I'm sitting back at the command prompt, and does nothing. and I get brought back to the shell ping 192.168.1.202 PING 192.168.1.202 (192.168.1.202) 56(84) bytes of data. 64 bytes from 192.168.1.202: icmp_seq=1 ttl=64 time=0.061 ms 64 bytes from 192.168.1.202: icmp_seq=2 ttl=64 time=0.042 ms 64 bytes from 192.168.1.202: icmp_seq=3 ttl=64 time=0.044 ms 64 bytes from 192.168.1.202: icmp_seq=4 ttl=64 time=0.046 ms 64 bytes from 192.168.1.202: icmp_seq=5 ttl=64 time=0.047 ms --- 192.168.1.202 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3997ms rtt min/avg/max/mdev = 0.042/0.048/0.061/0.006 ms\ PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Creating a distro on a sim card
I was pointed to this link to help with my previous problem; http://wiki.openmoko.org/wiki/Booting_from_SD I was wondering if that read, was all that it took to get a functioning OS on the SD card, and then the ability to copy onto the phone? Thanks PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Default OM settings, no lan messed up
How does the default WIFI work with open/free wifi access? Would I be able to get connected to the internet with a wifi router that has dhcp working? I'd really like to get the OM functioning. Thanks ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Default OM settings, no lan messed up
On Oct 14, 2008, at 7:40 AM, Rodney Myers wrote: How does the default WIFI work with open/free wifi access? Would I be able to get connected to the internet with a wifi router that has dhcp working? I'd really like to get the OM functioning. Thanks I just attempted to log onto a wide open wifi router. It did not go. Anything else I can try, to get the OM working? PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Default OM settings, no lan messed up
On Oct 14, 2008, at 7:13 PM, Joel Newkirk wrote:
On Tue, 14 Oct 2008 16:44:34 -0700, Rodney Myers [EMAIL PROTECTED]
wrote:
On Oct 14, 2008, at 7:40 AM, Rodney Myers wrote:
How does the default WIFI work with open/free wifi access?
Would I be able to get connected to the internet with a wifi router
that has dhcp working?
I'd really like to get the OM functioning.
Thanks
I just attempted to log onto a wide open wifi router. It did not go.
Anything else I can try, to get the OM working?
Put the following into etc/wpa_supplicant/wpa_supplicant.conf (and
below
that edit /etc/network/interfaces)and try ifup eth0 manually:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# home:
network={
ssid=NEWKIRK
proto=WPA
key_mgmt=WPA-PSK
psk=118a8aa1abfc236ebb4df06e891172ccef6c72c7db0ad5540b7f4c77858378d4
priority=50
}
# Open:
network={
ssid=any
key_mgmt=NONE
priority=5
}
And alter /etc/network/interfaces to have the following:
iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
(I left my own network in there as an example of working WPA to a
Netgear
router - I had repeated issues with it until I used the hex key
instead of
text - and yes, that's actually the right key: I wouldn't refuse any
Freerunner owner who wanted to leech my broadband, if they happened
to be
down the dead-end road to my house ;)
The higher priority numbers are used first if multiples match, IE at
home I
can see an unsecured network from next door, but it will always
connect to
my AP. Elsewhere it will connect to whatever unsecure AP is
reachable.
(In actual practice I've got three other APs defined as well, both
secure
and not)
j
Therein lies the problem. I have no shell access, and no access
through the USB port, after I edited the /etc/network/interfaces file.
I was hoping that the OM would access a wide open wifi connection, so
I could get ahead a bit.
PGP.sig
Description: This is a digitally signed message part
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Default OM settings, no lan messed up
OS = OS X 10.5.5 I received my OM this past week. Took some time to locate an ATT sim card that would work. Yesterday, I was able to follow the instructions at; http://wiki.openmoko.org/wiki/MacOS_X ,and using the link; http://downloads.openmoko.org/releases/Om2008.9 grabbing the rootfs of Om2008.9-gta02-20080916.rootfs.jffs2 to flash the phone. Once flashed, I noticed there was no console icon anymore I was able to SSH into the OM. Once I did that, I edited changed the /etc/network/interfaces file to reflect my lan. 192.168.1.*** Before I logged out, I catted the file to make sure that I had correctly set that file. It all looked correct I then logged out of the phone restarted the phone, thinking I now would be able to ssh, without jumping through hoops. No such luck. Now, the IP address is neither the default nor anything on the 192.168.1.*** network.. Any help in getting the phone functioning again, would be greatly appreciated. Many thanks PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Default OM settings, no lan messed up
On Oct 13, 2008, at 10:36 AM, Joel Newkirk wrote: On Mon, 13 Oct 2008 10:10:28 -0700, Rodney Myers [EMAIL PROTECTED] wrote: OS = OS X 10.5.5 I received my OM this past week. Took some time to locate an ATT sim card that would work. Yesterday, I was able to follow the instructions at; http://wiki.openmoko.org/wiki/MacOS_X ,and using the link; http://downloads.openmoko.org/releases/Om2008.9 grabbing the rootfs of Om2008.9-gta02-20080916.rootfs.jffs2 to flash the phone. Once flashed, I noticed there was no console icon anymore I was able to SSH into the OM. Once I did that, I edited changed the /etc/network/interfaces file to reflect my lan. 192.168.1.*** Before I logged out, I catted the file to make sure that I had correctly set that file. It all looked correct I then logged out of the phone restarted the phone, thinking I now would be able to ssh, without jumping through hoops. No such luck. Now, the IP address is neither the default nor anything on the 192.168.1.*** network.. Any help in getting the phone functioning again, would be greatly appreciated. Many thanks What is the full IP, gateway, and subnet mask you set on the FreeRunner, and on the USB network interface on your host? Does it overlap the subnet on any other interface on the host? j If you are able to set up a packet sniffer on USB network device on the host, try tapping 'installer' on the FR and see what IP the connection attempt comes from. I thought i had it setup this way address 192.168.1.20 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.101 (my MBP) My home lan is using 192.168.1.*** range. No idea on how to sniff packets, at this time. When I click on the installer it pops up a message; ERROR: Cannot access *. Please check your network When I plug the OM into the computer, it does show the MAC address, in dmesg; net_lucid_cake_driver_AJZaurusUSB: Ethernet address 40:00:ff:f7:87:5c PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Default OM settings, no lan messed up
The main problem is, I cannot ssh into the OM to make any changes. I cannot ping the OM, using 192.168.1.0 / 192.168.0.0 In the default setup, there is no shell icon anymore, so I am unable to see what the IP address really is. PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
OpenMoko, OS X, address book sync'ing
I'm hoping to receive my OpenMoko phone this week, from the NYC group, and was wondering if any OS X user had any luck in getting their phones sync'd with AddressBook? Thanks PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Glad to see Gentoo-openmoko distro
On Sep 9, 2008, at 7:05 AM, [EMAIL PROTECTED] wrote: On Tue, Sep 09, 2008 at 02:51:14PM +0100, Rui Miguel Silva Seabra wrote: On Tue, Sep 09, 2008 at 01:00:36PM +0100, Al Johnson wrote: On Tuesday 09 September 2008, Rui Miguel Silva Seabra wrote: I hope you guys don't mind killing your phone or uSD's memory sooner than everyone else :) Why? Are you making some unwarranted assumptions about using Gentoo on embedded systems? No unwarranted assumption, the only argument you could throw back at me is an argument against using Gentoo instead of any .deb or .rpm based distribution ;) Please, no distro-war, you're free to kill your flash devices sooner ;) Why would it kill the flash? With all of the thrashing, while it's attempting to compile everything? I know that I have gentoo on a MythTV box, and when installing anything heavy, forget using it for 1/2 to 3/4 of a day. PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: OpenMoko ATT plans (Semi OT)
On Sep 4, 2008, at 7:42 PM, Eli wrote: On Wednesday 27 August 2008 09:15:24 pm Rodney Myers wrote: I'm anxiously waiting for my phone (Thanks NYC), and for my contract with verizon to finally expire next month. When I switch to ATT, only GSM provider that has decent coverage in my area, I was wondering what plans this groups uses, to get the most out of the phone? Basic phone service, SMS/text messages, and I like the GPS feature. GPS does not require a SIM; in fact, only the phone features do. I'm using mine as a PDA without a SIM at the moment. How does the gps show the maps? For some reason, I thought that some form of data plan was required. PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
OpenMoko ATT plans (Semi OT)
I'm anxiously waiting for my phone (Thanks NYC), and for my contract with verizon to finally expire next month. When I switch to ATT, only GSM provider that has decent coverage in my area, I was wondering what plans this groups uses, to get the most out of the phone? Basic phone service, SMS/text messages, and I like the GPS feature. Thanks PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
