**** BEGIN LOGGING AT Thu Apr 01 02:59:57 2010 Apr 01 05:14:55 Does anyone other than me use their FR's USB networking with RNDIS (Windows host)? Apr 01 05:17:02 * brolin_empey has successfully bridged his Local Area Connection + Neo Connection on Win7 Pro 32-bit. I can ssh from Cygwin on Win7 to QtMoko on my FR, but QtMoko cannot even ping my LAN's gateway: I always get "Destination Host Unreachable". :( Apr 01 06:31:01 brolin_empey: check routing on FR Apr 01 07:00:46 brolin_empey: I try not to use it as it regularly crashed the XP machine Apr 01 07:36:24 PaulFertser: The routing is correct. RNDIS worked intermittently on QtMoko v14, so maybe it will start working later on v19. I am back to using my USB→Ethernet adapter on my FR because it is the only reliable way I have found to network QtMoko with Win7. Apr 01 07:38:12 blindcoder: I do not use Windows XP on my own PCs any more. RealTimeIsUniversal=1 support is /still/ partially broken on Windows XP. Apr 01 07:38:39 blindcoder: Are you using a Braille terminal? ;) Apr 01 07:39:03 brolin_empey: what's RealTimeIsUniversal? Apr 01 07:39:14 brolin_empey: I have to use XP on the company laptop :-( Apr 01 07:39:20 blindcoder: Or a screen reader? Apr 01 07:39:27 brolin_empey: nah, blindness is just metaphorical Apr 01 07:39:55 brolin_empey: as in "hey, I just had a look at your code and increased its usefulness by an order of magnitude with just 15 additional characters!" Apr 01 07:40:07 blindcoder: Yes, I figured, hence the ";)". ;) Apr 01 07:41:56 blindcoder: http://www.cl.cam.ac.uk/~mgk25/mswish/ut-rtc.html Apr 01 07:42:41 blindcoder: Using local time (zone) in a RTC is illogical, especially if the time zone uses DST. Apr 01 07:48:23 brolin_empey: if you can ssh, then it means theres no problem with rndis Apr 01 07:49:28 PaulFertser: Then why can QtMoko not even ping my LAN's gateway, which is the default gateway in its routing table? Apr 01 07:49:59 brolin_empey: why do not you start tcpdump on your host to find out? Apr 01 07:50:00 I mean in QtMoko's routing table. Apr 01 07:50:15 brolin_empey: can you show your FR's routing table? Apr 01 07:54:20 neo:~# route Apr 01 07:54:20 Kernel IP routing table Apr 01 07:54:20 Destination Gateway Genmask Flags Metric Ref Use Iface Apr 01 07:54:20 192.168.0.0 * 255.255.255.0 U 0 0 0 eth1 Apr 01 07:54:20 default 192.168.0.2 0.0.0.0 UG 0 0 0 eth1 Apr 01 07:54:20 neo:~# Apr 01 07:55:16 eth1 = my USB→Ethernet adapter. s/eth1/usb0/g for RNDIS. Apr 01 07:57:14 so 192.168.0.2 is your LANs default router? Apr 01 07:57:26 brolin_empey: something tells me that tcpdumping on your host will almost immediately reveal the cause rndis doesn't work as expected for you. Apr 01 07:57:28 and it responds to ping from other hosts? Apr 01 07:57:56 PaulFertser: Because I did not want to get sidetracked by trying to find why RNDIS is intermittent. Sometimes it started working without me changing any networking config. I use my USB→Ethernet adapter because it is always reliable. Apr 01 07:58:51 brolin_empey: ok, your choice. Also i've no idea how bridging works on win7, so you're on your own here. I'd say that's not a kernel problem anymore, and rather some configuration issue, probably on host. Apr 01 07:59:58 It's also not apparent to me why you do not want to set your win7 host to do NAT for FR. Apr 01 08:00:41 blindcoder: Yes and yes. Apr 01 08:02:36 PaulFertser: Why would I want Win7 to do NAT for my FR? That sounds unnecessarily complex. Apr 01 08:04:12 brolin_empey: hm, on Linux that's one command, not any more complex than setting up a bridge configuration-wise. Apr 01 08:04:45 PaulFertser: I could try, but I do not want to have to manually reconfigure networking on Win7 every time I connect or disconnect my FR. Apr 01 08:06:16 PaulFertser: I do not mean the commands to configure the NAT for the FR are complex, I mean why would I want to do that instead of bridging Local Area Connection + Neo Connection? Apr 01 08:06:56 brolin_empey: i'm not sure you need to reconfigure NAT every time you attach/detach the FR, at least that's not the case with Linux. Apr 01 08:07:24 brolin_empey: well, as i've said: i'm not sure how bridging works with win7, just that. It should be ok, just use tcpdump/wireshark or whatever to see what's going on... Apr 01 08:10:00 PaulFertser: Do I need to enable IPv4 forwarding on my FR and/or Win7? Apr 01 08:11:28 brolin_empey: for bridging most probably not, but again, i've no experience with bridging on windows. Apr 01 08:25:55 * brolin_empey just discovered a better (safer) hardware solution, still using the USB→Ethernet adapter. Apr 01 08:33:25 I was using a 5-pin mini USB M→USB A F adapter connected to the USB A M black upstream connector of my dual-power USB hub so my FR is line-powered while I am using the USB→Ethernet adapter connected to the dual-power USB hub. This was risky because there could be too much weight on the 5-pin mini USB M→USB A F adapter, or the adapter could get bent, etc. I had USB A F→USB A F couplers, but I never used them for my FR until n Apr 01 08:35:04 Now I can use my FR with a direct wired Ethernet connection to my LAN with only a regular USB cable connected to the FR, so I do not have to worry about breaking my FR's USB socket again! :) Apr 01 08:37:01 This is so cool! Now I do not need to worry about bridging, NAT, nor routing any more. :) Apr 01 08:37:43 As usual, the best solution is a hardware solution. ;) Apr 01 08:44:20 Congrats :) Apr 01 08:46:31 PaulFertser: Thanks. I guess I would not be able to do this with an N900 since it lacks USB Host! ;) Apr 01 08:48:23 Are there any non-Openmoko Linux phones with USB Host? Maybe the Greenphone? Apr 01 08:49:33 Of course, I would not need a USB→Ethernet adapter if QtMoko could connect to my WLAN at home and work. :P Apr 01 08:55:10 brolin_empey: btw which kernel do you use now? Apr 01 09:02:34 radekp: QtMoko v19-debug because v19-nodebug would not suspend. (fail) Apr 01 09:06:32 * brolin_empey wonders if his landlord would accept not paying his rent for April as an April/All Fool's Day joke. ;) Apr 01 09:07:04 Let me guess: no. :( Apr 01 09:07:29 He can accept you not paying the rent on the 1th though i'd guess. Apr 01 09:08:18 PaulFertser: s/1th/1st/gi ;) Apr 01 09:09:22 brolin_empey: i knew something's wrong in that statement, thanks :) Apr 01 09:09:25 PaulFertser: English inconsistently uses "first, second, third", not "oneth, twoth, third". Apr 01 09:10:02 brolin_empey: as i do not say words i type usually, i missed the typo :) Apr 01 09:11:49 PaulFertser: 1th and 2th instead of 1st and 2nd is common with non-native English speakers who do not know the first 2 ordinals (excluding zeroth ;)) are exceptional. Apr 01 09:12:34 brolin_empey: well, believe me or not, but i do know about those exceptions. Apr 01 09:12:40 ;) Apr 01 09:21:15 radekp: Will I ever be able to use the QtEI GUI to connect to my WLAN at home and work? Apr 01 09:22:27 iPhone users will still laugh at me for using wired Ethernet instead of WLAN on my FR. :P Apr 01 09:33:54 * brolin_empey spoke too soon: USB data does not work through the cable + coupler. :( Why not? Apr 01 09:35:24 * naquan 's really disappointed, they set up the stable directory in SHR build host and still nothing's in it, is this a Apr 1st trick? :( Apr 01 09:36:39 naquan: SHR is not stable. Can't you tell that from the Stable in the name Stable Hybrid Release? ;) Apr 01 09:37:23 misnomer++; Apr 01 09:40:25 brolin_empey: so the stable directory 's really a April Fool's trick? Apr 01 09:40:58 naquan: read about it in shr mailing lists Apr 01 09:41:01 No, just the stable branch of Stable Hybrid Release isn't stable, isn't it obvious? :P Apr 01 09:41:20 naquan: I do not know; I was just joking. Apr 01 09:43:01 * brolin_empey would really like working WLAN in the QtEI GUI on QtMoko, or at least in the CLI. :( Apr 01 09:43:10 hehe Apr 01 09:43:25 * Weiss enjoys how SHR is not really Stable, Hybrid or Released Apr 01 09:43:46 Weiss: sheshe? ;) Apr 01 09:44:08 :) Apr 01 10:10:00 JaMa: ok, i got it. "When it'll be ready" Apr 01 10:29:19 brolin_empey: i dont know what is your problem exactly - the gui uses wpa_supplicant, so if you can connect manually via wpa_supplicant then problem is in GUI Apr 01 10:29:51 brolin_empey: if not the problem is in wpa_supplicant (or it's configuration) or on some lower level Apr 01 10:31:55 brolin_empey: laugh at iPhone users - they cant use wired Ethernet :) Apr 01 10:34:50 brolin_empey: anyway i am afraid i cant help you very much with wifi from command line - i never did anything more advanced then "iwconfig essid" Apr 01 10:51:16 radekp: Most iPhone users probably do not even want to use wired Ethernet because they have working WLAN. Anyway, I need to try wpa_supplicant again on QtMoko v19. Maybe I was just missing the "iwconfig essid" command before I run "udhcpc eth0"? Anyway, I really need to go to bed now. Apr 01 13:24:56 radio check Apr 01 16:54:43 my installation is borked. always do an fsck *before* upgrading :) **** ENDING LOGGING AT Fri Apr 02 02:59:56 2010