Re: USB networking && Win7

2014-01-17 Thread matteo sanvito
Yeah, i can confirm what rhn said, I did the same!

good luck!
matteo


2014/1/17 rhn 

> On Fri, 17 Jan 2014 18:25:24 +0100
> Matthias Apitz  wrote:
>
> > El día Friday, January 17, 2014 a las 05:07:22PM +, Michael
> Spacefalcon escribió:
> >
> > > "dmatthews.org"  wrote:
> > >
> > > > PuTTY is quite a decent (free as in beer) ssh client for windows
> > >
> > > PuTTY is free as in speech too, i.e., it is bona fide free software -
> > > not just free as in beer.  Of course Windows isn't, but we are talking
> > > about PuTTY, right?
> >
> > I know PuTTY very well. But, I was talking about how to bring up the
> > USB network interface in Win7
> >
> > Thanks
> >
> >   matthias
>
> The Freerunner works as a USB Ethernet gadget (RNDIS).
> You need to install an .inf file (some kind of a description?) or else
> Windows will not work with it.
>
> [1] is describing how to do it. I did it a long time ago myself with the
> Freerunner, but I'm not sure if I used this exact guide.
>
> Cheers,
> rhn
>
> [1]
> http://wiki.openmoko.org/wiki/Neo_1973_and_Windows#USB_Ethernet_emulation
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking && Win7

2014-01-17 Thread rhn
On Fri, 17 Jan 2014 18:25:24 +0100
Matthias Apitz  wrote:

> El día Friday, January 17, 2014 a las 05:07:22PM +, Michael Spacefalcon 
> escribió:
> 
> > "dmatthews.org"  wrote:
> > 
> > > PuTTY is quite a decent (free as in beer) ssh client for windows
> > 
> > PuTTY is free as in speech too, i.e., it is bona fide free software -
> > not just free as in beer.  Of course Windows isn't, but we are talking
> > about PuTTY, right?
> 
> I know PuTTY very well. But, I was talking about how to bring up the
> USB network interface in Win7
> 
> Thanks
> 
>   matthias

The Freerunner works as a USB Ethernet gadget (RNDIS).
You need to install an .inf file (some kind of a description?) or else Windows 
will not work with it.

[1] is describing how to do it. I did it a long time ago myself with the 
Freerunner, but I'm not sure if I used this exact guide.

Cheers,
rhn

[1]http://wiki.openmoko.org/wiki/Neo_1973_and_Windows#USB_Ethernet_emulation

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking && Win7

2014-01-17 Thread Matthias Apitz
El día Friday, January 17, 2014 a las 05:07:22PM +, Michael Spacefalcon 
escribió:

> "dmatthews.org"  wrote:
> 
> > PuTTY is quite a decent (free as in beer) ssh client for windows
> 
> PuTTY is free as in speech too, i.e., it is bona fide free software -
> not just free as in beer.  Of course Windows isn't, but we are talking
> about PuTTY, right?

I know PuTTY very well. But, I was talking about how to bring up the
USB network interface in Win7

Thanks

matthias
-- 
Matthias Apitz   |  /"\ ASCII Ribbon Campaign: www.asciiribbon.org
E-mail: g...@unixarea.de |  \ / - No HTML/RTF in E-mail
WWW: http://www.unixarea.de/ |   X  - No proprietary attachments
phone: +49-170-4527211   |  / \ - Respect for open standards

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking && Win7

2014-01-17 Thread Michael Spacefalcon
"dmatthews.org"  wrote:

> PuTTY is quite a decent (free as in beer) ssh client for windows

PuTTY is free as in speech too, i.e., it is bona fide free software -
not just free as in beer.  Of course Windows isn't, but we are talking
about PuTTY, right?

VLR,
SF

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking && Win7

2014-01-17 Thread dmatthews.org
Hi Matthias

chiark.greenend.org.uk/~sgtatham/putty/

PuTTY is quite a decent (free as in beer) ssh client for windows

-- 
David Matthews 
m...@dmatthews.org

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


USB networking && Win7

2014-01-17 Thread Matthias Apitz

Hello,

I'm using fine my FR on my FreeBSD laptop and can connect to the FR with
SSH (...) over the USB network; how can I do this from a Windows 7
laptop? Thanks in advance and please dont blame me for Win7, it's not my
fault :-)

matthias
-- 
Sent from my FreeBSD netbook

Matthias Apitz, , http://www.unixarea.de/ f: +49-170-4527211
UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: possible to use wifi and usb networking at the same time? (qtmoko)

2013-01-07 Thread robin
Paul Wise  bonedaddy.net> writes:

> 
> Thats a bug in QtMoko's network setup, it seems to take full control
> of the kernel's networking setup without asking the kernel what
> networks are setup already and should remain. It also needs to be
> aware that not all network interfaces are managed by the QtMoko
> network UI.
> 
> You can work around it by starting the USB network from a terminal
> after starting the WiFi. Run ifup usb0 if using ifupdown for the USB
> connection (which is the default on Debian). That will give you two
> default routes because ifupdown also doesn't pay attention to existing
> kernel network state, but you will still be able to login. If USB is
> not connected or not forwarding connections then you may need to
> delete the extra default route to connect to the Internet though:
> 
> ip route del default via 192.168.0.200 dev usb0
> 


hi paul,

is this bug also causing the network interface on the freerunner to change type
once in a while. Sometimes my usb/ssh connection fails and if I then go to the 
setup of my network I see that there is a new interface on the freerunner which
hasn't been configured yet and the one which previously was working stopped 
doing
so.

br

robin



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: possible to use wifi and usb networking at the same time? (qtmoko)

2013-01-07 Thread robin
hi Ed,

thanks for your reply. in the end was easy, just use wifi through the internal 
network...

my setup us a rather standard setup I guess: 
Desktop (OpenSuse) -> Freerunner via USB, ssh OK, Masquerading apparently not
Desktop -> Router via LAN 
Freerunner -> Router via Wifi

Freerunner -> Desktop via Wifi, ssh without problems. But as this was so easy, 
it was now definetly the time to set up a root password on the freerunner...

br

robin




___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: possible to use wifi and usb networking at the same time? (qtmoko)

2013-01-04 Thread Paul Wise
Thats a bug in QtMoko's network setup, it seems to take full control
of the kernel's networking setup without asking the kernel what
networks are setup already and should remain. It also needs to be
aware that not all network interfaces are managed by the QtMoko
network UI.

You can work around it by starting the USB network from a terminal
after starting the WiFi. Run ifup usb0 if using ifupdown for the USB
connection (which is the default on Debian). That will give you two
default routes because ifupdown also doesn't pay attention to existing
kernel network state, but you will still be able to login. If USB is
not connected or not forwarding connections then you may need to
delete the extra default route to connect to the Internet though:

ip route del default via 192.168.0.200 dev usb0

-- 
bye,
pabs

http://wiki.openmoko.org/wiki/User:PaulWise

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: possible to use wifi and usb networking at the same time? (qtmoko)

2013-01-04 Thread Ed Kapitein
On 01/04/2013 04:02 PM, robin wrote:
> hi 
>
> I somehow messed up my routing, so I can no longer access the internet/router 
> from my freerunner (ping 192.168.0.200 works 192.168.0.1 (router) doesn't 
> anymore). 
>
> Now I thought as long as I can log in via ssh from my desktop I could still
> access the internet from my phone, by powering on wifi. BUT as soon as the
> wifi connection is up (and actually permits me to access the internet) my
> usb connection dies...
>
> so I was wondering if there is a setup, where you can just ssh into your phone
> power up wifi (maybe even from command line) and still have fully functional
> usb access to the phone.
>
> best regards and happy new year
>
>
> robin
>
>
Hi Robin,

Can you ssh to the wifi address of the FR?
That way it wouldn't matter if the USB connection dies.

Can you tell a bit more about your setup?
192.168.0.200 is connected to an usb port on your router?
What kind of router is it? a linux box with multiple interfaces?
Are you able to open up a terminal on the FR  and access the command line?

Kind regards,
Ed

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


possible to use wifi and usb networking at the same time? (qtmoko)

2013-01-04 Thread robin
hi 

I somehow messed up my routing, so I can no longer access the internet/router 
from my freerunner (ping 192.168.0.200 works 192.168.0.1 (router) doesn't 
anymore). 

Now I thought as long as I can log in via ssh from my desktop I could still
access the internet from my phone, by powering on wifi. BUT as soon as the
wifi connection is up (and actually permits me to access the internet) my
usb connection dies...

so I was wondering if there is a setup, where you can just ssh into your phone
power up wifi (maybe even from command line) and still have fully functional
usb access to the phone.

best regards and happy new year


robin


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking Issue

2012-05-13 Thread Timo Juhani Lindfors
Cristian Gómez  writes:
> Do you know how to fix this?

It'd be useful to see the output of the "dmesg", "ip address" and "ip
route" commands from both arch and ubuntu.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking Issue

2012-05-13 Thread Matthias Apitz
El día Sunday, May 13, 2012 a las 09:57:55AM -0500, Cristian Gómez escribió:

> Hi guys, I'm using SHR (last build) on NAND and QTMoko on SD and when I
> connect my FR to my Arch Linux box, I can't get a new network interface to
> ping/ssh to. This happens on Arch, in Ubuntu the interface is created
> without problems
> 
> Do you know how to fix this?

I do not know anything about Arch Linux. But, I have had the same
problem with FreeBSD. With the older SHR version (around 2010) the
interface was created fine, while with the recent (stage 046, or even
before) it was not created. The problem was that the USB vendor and
product ID is now presented by the SHR Linux kernel as 0x0525:0xa4a2
(and as well the IP addr pair changed, btw.). In FreeBSD I have had to
adjust my device daemon hook scripts to that. Maybe Arch Linux uses a
similar procedure to detect the USB device as a network device ...

HIH, espero que te ayude

matthias
-- 
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e  - w http://www.unixarea.de/
UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


USB Networking Issue

2012-05-13 Thread Cristian Gómez
Hi guys, I'm using SHR (last build) on NAND and QTMoko on SD and when I
connect my FR to my Arch Linux box, I can't get a new network interface to
ping/ssh to. This happens on Arch, in Ubuntu the interface is created
without problems

Do you know how to fix this?

Thanks in advance

/
* *Don't Worry...Be Linux*
* Cristian Gómez Alvarez
* Ingeniero en Sistemas y Computación --- Universidad de Caldas
* Almera Information Management
* Comunidad de Software Libre Manizales
* Linux User #463617
* Mi blog 
*/
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [shr-u] Furthermore problems with USB-networking

2010-07-09 Thread Martin Jansa
On Fri, Jul 09, 2010 at 02:13:35AM -0700, sferic wrote:
> 
> BTW, my Freerunner running on SHR-U is now eth again (eth4)?!?

that's because g_ether is included in kernel not as module

see what /etc/init.d/g_ether.sh does with g_ether module params and 
update your kernel params

-- 
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [shr-u] Furthermore problems with USB-networking

2010-07-09 Thread sferic

BTW, my Freerunner running on SHR-U is now eth again (eth4)?!?

Sferic
-- 
View this message in context: 
http://openmoko-public-mailinglists.1958.n2.nabble.com/shr-u-Furthermore-problems-with-USB-networking-tp5273334p5273587.html
Sent from the Openmoko Community mailing list archive at Nabble.com.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


[shr-u] Furthermore problems with USB-networking

2010-07-09 Thread sferic

Hello List,

The network connection via usb still gives me problems. After the
installation of shr unstable on sd card, it was even possible for me to
connect to internet on my pc (ubuntu 10:04) once and carry out an upgrade.
My freerunner has connected (and ist stillconnecting) to the PC via usb0
(Unlike my previous installation (see here
http://openmoko-public-mailinglists.1958.n2.nabble.com/SHR-U-Missing-UsbHost-tp5247792p5247792.html),
which was connected via eth8 (and is broken after a failed upgrade on
wifi).)

I suspect that something was installed through the upgrade on my freerunner,
which prevents internet access. But how can I find out? 

/usr/lib/opkg/info/ contains a large number of installation logs. Which of
them might have something to do with my problem, can not recognize myself.
If it helps, I can post a table of contents from the directory. But perhaps
the problem is already known and someone can give me a hint? For this ever
thank you
Sferic


-- 
View this message in context: 
http://openmoko-public-mailinglists.1958.n2.nabble.com/shr-u-Furthermore-problems-with-USB-networking-tp5273334p5273334.html
Sent from the Openmoko Community mailing list archive at Nabble.com.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Stuck in setting up usb networking for the simulator in ubuntu.

2010-05-03 Thread saravanan T
Hello,
I am stuck ssh into the phone to obtain the shell for the simulator. I have
gone through the steps of setting up usb networking for ubuntu in
openmokowiki.org.
*
*
*My Steps*
1.Download the kernel (Mine:2.6.28.10). Make the kernel by setting the
options in the configuration.(I enabled all the options except the first one
which says ' Enable support for usb gadgets' , as this option was not found)
2.Install the kernel.
3.modprobe, and adding gadget to fstab. mounting /dev/gadget

After that I checked my config-host.h in qemu (it has CONFIG_GADGETS =1).( I
did some google search and found this)
Then started the emulator by rebuilding it(make qemu).
After the emulator starts when I enter this in the qemu_moniter 'usb_add
gadget:1', then it hangs.

*Error Log:*
In the emulator it says 'Could not remove USB Device 0.5'
In the shell it says
'gadget_ep_setup: endpoint configuration failed :-22'
's3c_udc_handle_packet: EP0 overrun'
'pcf_write:automatic: fast -charge enabled'
's3c_udc_handle_packet: EP0 overrun'

I have checked this in Ubuntu 9.04 - Jaunty Jackalope - Quad Core
I have also tried this in the weekend in my vmware in macos - Ubuntu Karmic
9.10 (Kernel tried - 2.6.31.10)

In both the os the same problem occurs.
Please help regarding this issue, as I am stuck getting the shell of the
simulator to send command and pppd is also not working.. The terminal in the
simulator, is not so good.I cannot also install any other terminal package
without the shell.


Regards
Saravanan.L
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [QtMoko] no WLAN support nor USB networking with Windows 7 in QtMoko v18? (FR unusability rant)

2010-04-10 Thread Radek Polak
Brolin Empey wrote:

> upgrade path in his recent announcements of QtMoko v20 + v21.  radekp’s
> 2.6.32 kernel apparently now has support for USB Host, but I do not know
> if it has RNDIS support.

USB networking works with v21 on windows 7 32bit. The testing (v20) does not 
work yet.

Regards

Radek

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [QtMoko] no WLAN support nor USB networking with Windows 7 in QtMoko v18? (FR unusability rant)

2010-04-10 Thread David Lanzendörfer
> > [...]
> I'm a full time linux user but sometime I need RNDIS too.
Uhmm. Ok. I'll look then that its also in the defconfig for htcdream then.
Because probably we will run into the same problem there

> anyway I can suggest you to do backups of your (also non-critical) data
>  _before_ a critical upgrade... and yes, upgrades on moko are _always_
>  critical also if tagged as "stable" ;) (in the past I've lost my data too)
Basically you should alway backup critical data!

> > Anyway, sorry about my complaining and ranting.  Sometimes I allow my
> > actions to be based on my emotions instead of logical reasoning;  of
> you are a human, welcome between us! :)
I suggest Hypericum tea. It helps overcoming this unneeded human weaknessed:
http://en.wikipedia.org/wiki/Hypericum

> bye
bye
leviathan
-- 
David Lanzendörfer
OpenSourceSupport GmbH
System engineer and supporter


signature.asc
Description: This is a digitally signed message part.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [QtMoko] no WLAN support nor USB networking with Windows 7 in QtMoko v18? (FR unusability rant)

2010-04-10 Thread Alfa21
2010-04...@03:42 Brolin Empey

> As you can probably tell, I was very frustrated and in rant mode when I 

I see! :P


> Windows NT over Linux as a desktop client OS, but I still think the 
> distro maintainers should have a release checklist to prevent releasing 
> a kernel without RNDIS support, for example.  RNDIS support is critical 
> for me because I need it for ssh access to my FR.  I know I could use a 

I agree!
I'm a full time linux user but sometime I need RNDIS too.


> try regular Qi instead of qi-bootmenu.  My ext3 rootfs on SD got 
> partially corrupted too, though, and apparently I have lost my entire 
> calendar + all of my >400 tasks. :((  I will survive, though:  I have 
> tried to spend more effort on progressing than worrying about my 
> non-critical data loss.

anyway I can suggest you to do backups of your (also non-critical) data 
_before_ a critical upgrade... and yes, upgrades on moko are _always_ critical 
also if tagged as "stable" ;)
(in the past I've lost my data too)


> Anyway, sorry about my complaining and ranting.  Sometimes I allow my 
> actions to be based on my emotions instead of logical reasoning;  of 

you are a human, welcome between us! :)

bye

-- 
ALFA21 IS PROVIDED "AS IS" AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR 
IMPLIED.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [QtMoko] no WLAN support nor USB networking with Windows 7 in QtMoko v18? (FR unusability rant)

2010-04-10 Thread Brolin Empey
As you can probably tell, I was very frustrated and in rant mode when I 
wrote my original post.  My problems were caused by my wrong approach, 
though.  I should have booted QtMoko from SD instead of NAND because SD 
is far more flexible, especially when troubleshooting.

QtMoko v18’s lack of USB networking with Windows 7 was caused by its 
2.6.32 kernel config.  I have been chatting with radekp (and others) in 
#openmoko:  he tried to help me by providing new kernel images with 
RNDIS support enabled, but I never got RNDIS working until I switched to 
QtMoko v19.  I know I am a minority Openmoko user because I prefer 
Windows NT over Linux as a desktop client OS, but I still think the 
distro maintainers should have a release checklist to prevent releasing 
a kernel without RNDIS support, for example.  RNDIS support is critical 
for me because I need it for ssh access to my FR.  I know I could use a 
Linux guest in VirtualBox or another virtual machine on my Windows 7 
host, but I have been avoiding installing a VM because I fear it will 
become Yet Another of my countless underestimated projects. 
Furthermore, I have Ubuntu tower PCs at both home and work.  I prefer 
Cygwin over a Linux guest because Cygwin is better integrated with the 
host:  Cygwin uses the same file system, for example.  Anyway, I should 
not blame distro maintainers for not using a release checklist because I 
should ask if their new release contains the features and/or support I 
need before upgrading, especially for a minority case such as RNDIS 
support.  You can read the #openmoko logs on the Web if you are 
interested in my conversations with radekp (and others).

My QtMoko v19 installation in NAND became unusable because my JFFS2 
rootfs somehow got partially corrupted while my FR was suspended 
overnight.  I still do not know how that happened, but I learned there 
is no fsck for JFFS2 only after I needed an fsck to repair my rootfs.  I 
migrated my QtMoko v19 installation from NAND to an 8 GB microSDHC card, 
which I managed to eventually boot with qi-bootmenu.  QtEI restarts when 
I tell it to “Restart Device” or “Shutdown Device”, though, so I need to 
try regular Qi instead of qi-bootmenu.  My ext3 rootfs on SD got 
partially corrupted too, though, and apparently I have lost my entire 
calendar + all of my >400 tasks. :((  I will survive, though:  I have 
tried to spend more effort on progressing than worrying about my 
non-critical data loss.

I should have tried upgrading QtMoko by replacing the kernel image, 
modules, and /opt/qtmoko/ with the versions from the new release instead 
of tarring my current installation, starting over with the new release, 
then trying to copy everything I need from my backup tarball of the 
previous release.  radekp even explicitly mentions this (untested) 
upgrade path in his recent announcements of QtMoko v20 + v21.  radekp’s 
2.6.32 kernel apparently now has support for USB Host, but I do not know 
if it has RNDIS support.

Anyway, sorry about my complaining and ranting.  Sometimes I allow my 
actions to be based on my emotions instead of logical reasoning;  of 
course, I lack control over my emotions.  I want to help improve my FR 
experience, including helping radekp make QtMoko the best and most 
usable FR distro, instead of only complaining without offering 
constructive criticism.  I realise the FR is a community project;  I am 
grateful radekp and others, including Alishams Hassam locally, are 
willing to help me personally.  I know radekp has a wife, 2 children, 
and a full-time (day) job in addition to his (volunteer) role as QtMoko 
maintainer.  I have a full-time day job too, but it is very flexible and 
is in a very supportive and understanding environment.  I have never 
been married and have no children, though.

I have probably forgotten to mention something important in this 
message, but I think it will still be sufficient for now.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


[QtMoko] no WLAN support nor USB networking with Windows 7 in QtMoko v18? (FR unusability rant)

2010-03-28 Thread Brolin Empey
Hello fans of cute trolls ;),

I finally used tar to back up my QtMoko v14 installation in my FR’s 
onboard NAND, then reflashed QtMoko v18 because, among other annoyances, 
I was tired of missing incoming SMS messages until I restarted QtEI. 
Anyway, QtMoko v18 boots and appears to work, but the WLAN interface 
does not exist and USB networking with Windows 7 does not work at all, 
even though it partially worked (was intermittent) with QtMoko v14.  No 
Neo Connection is created when I connect my FR to my Windows 7 laptop, 
so I cannot bridge Neo Connection to Local Area Connection so I cannot 
ssh from Cygwin on Windows 7 to QtMoko v18.  The WLAN interface somehow 
appeared after I started writing this message, but it is useless 
because, of course, I cannot connect to my WLAN at home.  I tried with 
both the QtEI GUI and the CLI.  I decided to finally try using Bluetooth 
to network QtMoko v18 with Windows 7, but QtEI says Bluetooth is 
unavailable when I open Bluetooth from the Main Menu.  I tried using 
“Power on Bluetooth” in the Dev Tools, but, of course, it does not 
appear to do anything so I cannot even configure Bluetooth on QtMoko 
v18, so there is no point in continuing trying to configure Bluetooth. 
I do not want to have to reboot my FR just to get Bluetooth working 
again in QtMoko v18 because Bluetooth will probably die again after I 
suspend and resume.  So, since the FR’s WLAN is useless, as usual, 
Bluetooth is broken, and USB networking with Windows 7 is completely 
broken, I have to (try to) use my wired Ethernet LAN again, even though 
I think this is how my FR’s USB connector got broken last time.  Of 
course, though, I cannot even enable logical USB host mode on QtMoko v18 
(at least electrical USB device mode works, which is surprising because 
it means something actually works on my FR! (fail)) because the Dev Tool 
to enable USB host mode appears to do nothing, which makes sense if it 
uses sysfs because there is no usb_mode file in sysfs.  lsmod does not 
list ohci-hcd, so I guess either the module is not loaded or it is built 
into the kernel image.  I cannot load ohci-hcd because it does not exist 
in /lib/modules/, which appears to be missing many modules.  Why? (fail) 
  Are most modules built into the kernel, or were these modules not 
built at all because they would be too useful?  I need to restore at 
least my QtEI config and user data from my QtMoko v14 backup tarball, 
but this is a huge PITA without ssh access to QtMoko v18 because I have 
to use the tedious onscreen keyboard in qterminal.  QtMoko v18 has no 
Internet access because I cannot connect it to my PC, nor my home 
(wired) LAN nor WLAN, so I cannot install mc to see if the version in 
lenny has been upgraded so it is no longer useless because of the 
regression which prevented me from listing the contents of my QtMoko v11 
backup tarball on QtMoko v14, so I have to use tar from the command 
line, which takes ages to do anything, such as listing archive contents 
and extracting specific files.  I probably use QtMoko as a PDA more than 
a phone:  I rely on it for my personal calendar and had over 400 tasks, 
including completed tasks.  I do not know how anyone considers paper 
calendars on their wall at home useful because they do not have them 
with them when they are away from home;  I am often away from home when 
I make appointments.  Anyway, I know I have appointments next week (the 
week starts on Monday, not Sunday, for me.  I hate calendars which start 
on Sunday.), but I cannot access my calendar because I cannot restore my 
QtMoko v14 backup.  I also have at least 2 upcoming events I need to add 
to my calendar, but I cannot do so, so I have to rely on people to call 
me to remind me because I will probably forget if I do not have the 
events in my calendar.  I know I should have properly backed up my 
QtMoko v14 installation by saving a disk (memory) image of the onboard 
NAND instead of creating a tarball of the files, but I was very 
foolishly optimistic QtMoko v18 would work better (be less unusable) 
than v14. (epic fail)  I know this message has a very negative tone, but 
I am currently very frustrated because my FR is still unusable after 
spending most of my weekend so far trying to upgrade from QtMoko v14 to 
v18.  Alishams Hassam (in To above) asked me how it could take so many 
hours for me to upgrade QtMoko;  now he has a written record of the 
explanation.  As much as I want to make my FR usable, everything always 
seems to end up being a huge PITA.  I think I should really buy an N900 
because I want a usable Linux phone (proper, standard, Debian-based 
Linux, not crappy, non-standard Android Linux) which does not literally 
take days to upgrade to fix problems which should not have been present 
in a release in the first place. :((

Brolin

-- 
Sometimes I forget how to do small talk: <http://xkcd.com/222/>

“If you have to ask why, you’re not a member of the intended au

Re: [QtMoko] intermittent USB networking + non-working WLAN = must use wired LAN = USB port hardware problem

2010-03-04 Thread Brolin Empey
Radek Polak wrote:
> On Monday 01 March 2010 04:16:22 Brolin Empey wrote:
>
>> Does anyone use USB networking with their FreeRunner with Windows Vista
>> or Windows 7?
>
> I had it working with XP.

That does not matter to me because I do not use Windows XP any more.

> But now i switched all my machines (even at work) to
> linux. I think i left preinstalled win 7 on my notebook so i can try at home.

Did you try USB networking on Windows 7?

>
>> that does not even matter any more until I fix the USB port hardware
>> problem.
>
> You can try besides wifi also bluetooth networking. It should not be hard to
> set it up

It should not be hard to connect to my WLAN either, but of course it is. 
:P  The USB networking with Windows 7 should work reliably instead of 
intermittently too.

> (but doing it all with onscreen keyboard could require some
> patience). But there can be problem that bluetooth is sometimes gone after
> suspend/resume.

I thought that was fixed in 2.6.3x kernels?

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [QtMoko] intermittent USB networking + non-working WLAN = must use wired LAN = USB port hardware problem

2010-03-01 Thread Paul Fertser
Dave  writes:
> Using qtmoko V16, I have found that suspending using the power
> button or waking by plugging in the charger guarantee that bluetooth
> is killed.

And what do you mean by killed? Does BT adapter disappear from lsusb
list? Or does bluetoothd get confused by something? Or what? Please
clarify, probably adding relevant dmesg and bluetoothd debug log
lines, along with the information about the kernel version you use.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [QtMoko] intermittent USB networking + non-working WLAN = must use wired LAN = USB port hardware problem

2010-03-01 Thread Dave
Hi
Using qtmoko V16, I have found that suspending using the power button or
waking by plugging in the charger guarantee that bluetooth is killed. If I
allow the phone to suspend through timeout settings or wake the phone before
attaching to a charge/usb source then bluetooth remains good for weeks.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [QtMoko] intermittent USB networking + non-working WLAN = must use wired LAN = USB port hardware problem

2010-03-01 Thread Radek Polak
On Monday 01 March 2010 04:16:22 Brolin Empey wrote:

> Does anyone use USB networking with their FreeRunner with Windows Vista
> or Windows 7? 

I had it working with XP. But now i switched all my machines (even at work) to 
linux. I think i left preinstalled win 7 on my notebook so i can try at home.

> that does not even matter any more until I fix the USB port hardware
> problem.

You can try besides wifi also bluetooth networking. It should not be hard to 
set it up (but doing it all with onscreen keyboard could require some 
patience). But there can be problem that bluetooth is sometimes gone after 
suspend/resume.

Regards

Radek

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


[QtMoko] intermittent USB networking + non-working WLAN = must use wired LAN = USB port hardware problem

2010-02-28 Thread Brolin Empey
Hello FreeRunners,

I am still using QtMoko v14 in onboard NAND on my US GTA02A6.  I know 
v16 is old by now, but I am not upgrading because it is a huge hassle. 
I already upgraded from v11 to v14 months ago;  I do not want to repeat 
that hassle.  I will have even more to do after upgrading from v14 than 
from v11 because I have many customisations to restore and packages to 
reinstall.  Anyway, when I was still living in my parents’s house, I had 
the USB networking working with Windows Vista Ultimate Edition SP1 
32-bit on optiplex960.  My QtMoko had reliable Internet access via the 
network bridge (Local Area Connection + Neo Connection).  I upgraded 
from Windows Vista SP1 to SP2 because I wanted full support for 
RealTimeIsUniversal=1.  I do not remember testing the USB networking 
after upgrading to SP2, so maybe it broke with SP2.  I finally chose a 
model of laptop, ordered it, and received it.  brolin-V13 (my laptop) 
runs Windows 7 Professional 32-bit.  The USB networking is intermittent 
with Windows 7:  I can ssh to QtMoko from Cygwin on brolin-V13, but 
QtMoko can only partially access the Internet.  Name resolution works 
sometimes, but most of the time I get “destination host unreachable” 
when pinging hosts on my LAN or on the Internet.  Sometimes, though, the 
pings start working, but I do not know why and I cannot reliably 
reproduce the behaviour.  I tried USB networking with optiplex960 again 
since it used to work there, but QtMoko cannot access the Internet 
because I get “destination host unreachable” when pinging hosts on my 
LAN or on the Internet.  Actually, I do not fully remember what happened 
because it was weeks ago and I did not keep a log.  I know I should have 
asked for help on this list then, but I was trying to be practical and 
avoid sidetracking by using what works and not bothering asking for help 
with what I cannot get working (USB networking with Windows Vista + 
Windows 7).  I cannot connect my QtMoko to my WLAN because the QtEI WLAN 
GUI does not work properly and using the command line is too much 
hassle:  sometimes it works, other times it does not, but I do not even 
know what is different between when it works and does not work.  So, 
other than using sneakernet to transfer files to my FreeRunner, the only 
reliable network connection is my USB→Ethernet adapter.  I had a miniUSB 
M→USB AF adapter connected directly to my FreeRunner (not using a long 
cable, which I should have done as I discovered later, after it was too 
late), then my dual-power USB hub, then my USB→Ethernet adapter, then an 
Ethernet cable to my USB→Ethernet adapter.  This worked for a day or so, 
but I think it was a mistake because there was too much weight on the 
miniUSB M→USB AF adapter while I was holding my FreeRunner to use it for 
voice calls.  Now my FreeRunner’s USB port works for power, so I can 
still charge the battery, but not for communications, so I think a 
solder connection must have come undone.  I need to try disassembling my 
FreeRunner to check the connections for the USB connector so I can ask 
someone at work to fix (resolder) the connection, but I have not yet 
done so.  It must be a hardware problem because QtMoko can still charge, 
but nothing happens when I connect USB devices to my FreeRunner:  no 
kernel modules are automatically loaded, there are no kernel messages. 
Manually loading the kernel modules (e.g., dm9601 for my USB→Ethernet 
adapter) for the USB device does not help.  It is not because of the 
electrical/logical USB host/device setting because I checked that;  I 
know how to use sysfs to change it.

Does anyone use USB networking with their FreeRunner with Windows Vista 
or Windows 7?  I do not want to uninstall Windows Vista SP2 on 
optiplex960 because I want full support for RealTimeIsUniversal=1. 
There is nothing I can do with Windows 7 because no service pack has 
even been released.  I have Ubuntu v8.04 LTS on k7t266 at home, but even 
if I could get USB networking working with k7t266, that does not help 
when I am at work because k7t266 (+ optiplex960) stay(s) on my desk at 
home.  I want reliable USB networking with Windows 7 on brolin-V13, but 
that does not even matter any more until I fix the USB port hardware 
problem.  I am not running Linux or any other OS on brolin-V13 because I 
highly prefer Windows Vista or Windows 7 over Linux (Ubuntu) as a 
desktop client OS.  I do not want to debate this preference.

Oh well, at least I think I finally have satisfactory earpiece volume on 
my QtMoko, at least when there is no or little background noise.  I can 
live with using the Docked Keyboard in qterminal, but now I cannot even 
ssh to QtMoko, never mind reflash nor access the Internet from QtMoko. :(

Brolin

-- 
Sometimes I forget how to do small talk: <http://xkcd.com/222/>

“If you have to ask why, you’re not a member of the intended audience.” 
— Bob Zimbinski, <http://webpages.mr.net/bobz

Re: USB networking with Ubuntu 9.04

2009-10-08 Thread Eric Olson
I copied Sander's exact lines into /etc/network/interfaces (I changed 
eth2 to usb0 -- I don't know if that matters) on my ubuntu 9.04 laptop 
and it's working for me.  I have plugged and unplugged the cable a 
couple times and no longer have to run my manual script each time.

Thanks!
Eric

Tony Berth wrote:
> did try that and did work when I was using a debian 5 box but no chance with
> ubuntu 9.04 :(
> 
> Thanks
> 
> Tony
> 
> On Thu, Oct 8, 2009 at 1:21 PM, Sander van Grieken  wrote:
> 
>> Why use a script that you need to run manually each time?
>>
>> It can be done automatically just by putting the right stuff in
>> /etc/network/interfaces:
>>
>> auto eth2
>> iface eth2 inet static
>>   address 192.168.0.200
>>   netmask 255.255.255.0
>>   post-up iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -j MASQUERADE
>>  post-up echo 1 > /proc/sys/net/ipv4/ip_forward
>>  post-up route add -host 192.168.0.202 dev eth2
>>  post-up dnsmasq
>>  pre-down echo 0 > /proc/sys/net/ipv4/ip_forward
>>  pre-down iptables -t nat -D POSTROUTING -s 192.168.0.0/24 -j MASQUERADE
>>  pre-down killall dnsmasq
>>
>>
>> when you plug in the FR, eth2 will activate automatically..
>>
>> grtz
>> Sander
>>
>>
>> On Thursday 08 October 2009 03:24:06 Cristian Gómez wrote:
>>> Hi Tony, thanks for giving a try to the script. I'm glad it helped you. I
>>> just create a sub-section on the wiki page [1] where I put the script to
>>> help others to get connected easily.
>>>
>>> Cheers
>>>
>>> [1] http://wiki.openmoko.org/wiki/USB_Networking#Connection_Script
>>>
>>> /***
>>> * Don't Worry...Be Linux
>>> * Cristian Gómez Alvarez
>>> * Ingeniero en Sistemas y Computación
>>> * Universidad de Caldas
>>> * Comunidad de Software Libre Manizales
>>> * IEEE/WIE Student Member
>>> * Linux User #463617
>>> * Mi Blog: http://cristianpark.sehablalinux.com/
>>> /
>>>
>>>
>>> 2009/10/7 Tony Berth 
>>>
 On Wed, Oct 7, 2009 at 10:27 AM, Matthias Huber <

 matthias.hu...@wollishausen.de> wrote:
>  Tony Berth schrieb:
>
> Bingo. Thanks A LOT!
>
> Is it possible to update the Wiki with that one. I think this will be
>> a
> great help to the whole community
>
>  if you would tell me wich of / or both tricks did it on your system ?
>
>>> but i had to add this two lines to my /etc/ufw/ufw.conf
>>>
>>> ufw allow from 192.168.0.202
>>> ufw allow to 192.168.0.202
>>>
>>>
>>> another trial with iptables needs to load some modules too:
>>>
>>> #!/bin/sh
>>>
>>> MOKO=192.168.0.202
>>>
>>> echo 1 > /proc/sys/net/ipv4/ip_forward
>>>  modprobe ipt_MASQUERADE
>>>
>>> iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
>>> iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
>>> iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32
 what works was the script Cristian Gomez included in his reply!

 Just for the records, the first time I run that script it does assign
>> the
 192.168.0.200 IP to eth1 but can't ping/access 192.168.0.202! Then:

 - I disconnect Openmoko
 - connect it again
 - re-run the script and voila the connection is there!

 Thanks

 Tony


 ___
 Openmoko community mailing list
 community@lists.openmoko.org
 http://lists.openmoko.org/mailman/listinfo/community
>> ___
>> Openmoko community mailing list
>> community@lists.openmoko.org
>> http://lists.openmoko.org/mailman/listinfo/community
>>
> 
> 
> 
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking with Ubuntu 9.04

2009-10-08 Thread Tony Berth
did try that and did work when I was using a debian 5 box but no chance with
ubuntu 9.04 :(

Thanks

Tony

On Thu, Oct 8, 2009 at 1:21 PM, Sander van Grieken  wrote:

> Why use a script that you need to run manually each time?
>
> It can be done automatically just by putting the right stuff in
> /etc/network/interfaces:
>
> auto eth2
> iface eth2 inet static
>   address 192.168.0.200
>   netmask 255.255.255.0
>   post-up iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -j MASQUERADE
>  post-up echo 1 > /proc/sys/net/ipv4/ip_forward
>  post-up route add -host 192.168.0.202 dev eth2
>  post-up dnsmasq
>  pre-down echo 0 > /proc/sys/net/ipv4/ip_forward
>  pre-down iptables -t nat -D POSTROUTING -s 192.168.0.0/24 -j MASQUERADE
>  pre-down killall dnsmasq
>
>
> when you plug in the FR, eth2 will activate automatically..
>
> grtz
> Sander
>
>
> On Thursday 08 October 2009 03:24:06 Cristian Gómez wrote:
> > Hi Tony, thanks for giving a try to the script. I'm glad it helped you. I
> > just create a sub-section on the wiki page [1] where I put the script to
> > help others to get connected easily.
> >
> > Cheers
> >
> > [1] http://wiki.openmoko.org/wiki/USB_Networking#Connection_Script
> >
> > /***
> > * Don't Worry...Be Linux
> > * Cristian Gómez Alvarez
> > * Ingeniero en Sistemas y Computación
> > * Universidad de Caldas
> > * Comunidad de Software Libre Manizales
> > * IEEE/WIE Student Member
> > * Linux User #463617
> > * Mi Blog: http://cristianpark.sehablalinux.com/
> > /
> >
> >
> > 2009/10/7 Tony Berth 
> >
> > > On Wed, Oct 7, 2009 at 10:27 AM, Matthias Huber <
> > >
> > > matthias.hu...@wollishausen.de> wrote:
> > >>  Tony Berth schrieb:
> > >>
> > >> Bingo. Thanks A LOT!
> > >>
> > >> Is it possible to update the Wiki with that one. I think this will be
> a
> > >> great help to the whole community
> > >>
> > >>  if you would tell me wich of / or both tricks did it on your system ?
> > >>
> >  but i had to add this two lines to my /etc/ufw/ufw.conf
> > 
> >  ufw allow from 192.168.0.202
> >  ufw allow to 192.168.0.202
> > 
> > 
> >  another trial with iptables needs to load some modules too:
> > 
> >  #!/bin/sh
> > 
> >  MOKO=192.168.0.202
> > 
> >  echo 1 > /proc/sys/net/ipv4/ip_forward
> >   modprobe ipt_MASQUERADE
> > 
> >  iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
> >  iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
> >  iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32
> > >
> > > what works was the script Cristian Gomez included in his reply!
> > >
> > > Just for the records, the first time I run that script it does assign
> the
> > > 192.168.0.200 IP to eth1 but can't ping/access 192.168.0.202! Then:
> > >
> > > - I disconnect Openmoko
> > > - connect it again
> > > - re-run the script and voila the connection is there!
> > >
> > > Thanks
> > >
> > > Tony
> > >
> > >
> > > ___
> > > Openmoko community mailing list
> > > community@lists.openmoko.org
> > > http://lists.openmoko.org/mailman/listinfo/community
> >
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking with Ubuntu 9.04

2009-10-08 Thread Sander van Grieken
Why use a script that you need to run manually each time?

It can be done automatically just by putting the right stuff in 
/etc/network/interfaces:

auto eth2
iface eth2 inet static
  address 192.168.0.200
  netmask 255.255.255.0
  post-up iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -j MASQUERADE
  post-up echo 1 > /proc/sys/net/ipv4/ip_forward
  post-up route add -host 192.168.0.202 dev eth2
  post-up dnsmasq
  pre-down echo 0 > /proc/sys/net/ipv4/ip_forward
  pre-down iptables -t nat -D POSTROUTING -s 192.168.0.0/24 -j MASQUERADE
  pre-down killall dnsmasq


when you plug in the FR, eth2 will activate automatically..

grtz
Sander


On Thursday 08 October 2009 03:24:06 Cristian Gómez wrote:
> Hi Tony, thanks for giving a try to the script. I'm glad it helped you. I
> just create a sub-section on the wiki page [1] where I put the script to
> help others to get connected easily.
> 
> Cheers
> 
> [1] http://wiki.openmoko.org/wiki/USB_Networking#Connection_Script
> 
> /***
> * Don't Worry...Be Linux
> * Cristian Gómez Alvarez
> * Ingeniero en Sistemas y Computación
> * Universidad de Caldas
> * Comunidad de Software Libre Manizales
> * IEEE/WIE Student Member
> * Linux User #463617
> * Mi Blog: http://cristianpark.sehablalinux.com/
> /
> 
> 
> 2009/10/7 Tony Berth 
> 
> > On Wed, Oct 7, 2009 at 10:27 AM, Matthias Huber <
> >
> > matthias.hu...@wollishausen.de> wrote:
> >>  Tony Berth schrieb:
> >>
> >> Bingo. Thanks A LOT!
> >>
> >> Is it possible to update the Wiki with that one. I think this will be a
> >> great help to the whole community
> >>
> >>  if you would tell me wich of / or both tricks did it on your system ?
> >>
>  but i had to add this two lines to my /etc/ufw/ufw.conf
> 
>  ufw allow from 192.168.0.202
>  ufw allow to 192.168.0.202
> 
> 
>  another trial with iptables needs to load some modules too:
> 
>  #!/bin/sh
> 
>  MOKO=192.168.0.202
> 
>  echo 1 > /proc/sys/net/ipv4/ip_forward
>   modprobe ipt_MASQUERADE
> 
>  iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
>  iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
>  iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32
> >
> > what works was the script Cristian Gomez included in his reply!
> >
> > Just for the records, the first time I run that script it does assign the
> > 192.168.0.200 IP to eth1 but can't ping/access 192.168.0.202! Then:
> >
> > - I disconnect Openmoko
> > - connect it again
> > - re-run the script and voila the connection is there!
> >
> > Thanks
> >
> > Tony
> >
> >
> > ___
> > Openmoko community mailing list
> > community@lists.openmoko.org
> > http://lists.openmoko.org/mailman/listinfo/community
> 

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking with Ubuntu 9.04

2009-10-07 Thread Cristian Gómez
Hi Tony, thanks for giving a try to the script. I'm glad it helped you. I
just create a sub-section on the wiki page [1] where I put the script to
help others to get connected easily.

Cheers

[1] http://wiki.openmoko.org/wiki/USB_Networking#Connection_Script

/***
* Don't Worry...Be Linux
* Cristian Gómez Alvarez
* Ingeniero en Sistemas y Computación
* Universidad de Caldas
* Comunidad de Software Libre Manizales
* IEEE/WIE Student Member
* Linux User #463617
* Mi Blog: http://cristianpark.sehablalinux.com/
/


2009/10/7 Tony Berth 

>
>
> On Wed, Oct 7, 2009 at 10:27 AM, Matthias Huber <
> matthias.hu...@wollishausen.de> wrote:
>
>>  Tony Berth schrieb:
>>
>> Bingo. Thanks A LOT!
>>
>> Is it possible to update the Wiki with that one. I think this will be a
>> great help to the whole community
>>
>>  if you would tell me wich of / or both tricks did it on your system ?
>>
>>
 but i had to add this two lines to my /etc/ufw/ufw.conf

 ufw allow from 192.168.0.202
 ufw allow to 192.168.0.202


 another trial with iptables needs to load some modules too:

 #!/bin/sh

 MOKO=192.168.0.202

 echo 1 > /proc/sys/net/ipv4/ip_forward
  modprobe ipt_MASQUERADE

 iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
 iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
 iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32


> what works was the script Cristian Gomez included in his reply!
>
> Just for the records, the first time I run that script it does assign the
> 192.168.0.200 IP to eth1 but can't ping/access 192.168.0.202! Then:
>
> - I disconnect Openmoko
> - connect it again
> - re-run the script and voila the connection is there!
>
> Thanks
>
> Tony
>
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>
>
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking with Ubuntu 9.04

2009-10-07 Thread Tony Berth
On Wed, Oct 7, 2009 at 10:27 AM, Matthias Huber <
matthias.hu...@wollishausen.de> wrote:

>  Tony Berth schrieb:
>
> Bingo. Thanks A LOT!
>
> Is it possible to update the Wiki with that one. I think this will be a
> great help to the whole community
>
>  if you would tell me wich of / or both tricks did it on your system ?
>
>
>>> but i had to add this two lines to my /etc/ufw/ufw.conf
>>>
>>> ufw allow from 192.168.0.202
>>> ufw allow to 192.168.0.202
>>>
>>>
>>> another trial with iptables needs to load some modules too:
>>>
>>> #!/bin/sh
>>>
>>> MOKO=192.168.0.202
>>>
>>> echo 1 > /proc/sys/net/ipv4/ip_forward
>>>  modprobe ipt_MASQUERADE
>>>
>>> iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
>>> iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
>>> iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32
>>>
>>>
what works was the script Cristian Gomez included in his reply!

Just for the records, the first time I run that script it does assign the
192.168.0.200 IP to eth1 but can't ping/access 192.168.0.202! Then:

- I disconnect Openmoko
- connect it again
- re-run the script and voila the connection is there!

Thanks

Tony
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking with Ubuntu 9.04

2009-10-07 Thread Matthias Huber

Tony Berth schrieb:

Bingo. Thanks A LOT!

Is it possible to update the Wiki with that one. I think this will be 
a great help to the whole community



if you would tell me wich of / or both tricks did it on your system ?



but i had to add this two lines to my /etc/ufw/ufw.conf

ufw allow from 192.168.0.202
ufw allow to 192.168.0.202


another trial with iptables needs to load some modules too:

#!/bin/sh

MOKO=192.168.0.202


echo 1 > /proc/sys/net/ipv4/ip_forward
modprobe ipt_MASQUERADE

iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32




--
Mit freundlichen Grüssen
Matthias Huber 
Kohlstattstr. 14

86459 Wollishausen
Tel: 08238-7998
LPI000181125

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking with Ubuntu 9.04

2009-10-06 Thread Tony Berth
Bingo. Thanks A LOT!

Is it possible to update the Wiki with that one. I think this will be a
great help to the whole community

Cheers

Tony

2009/10/7 Cristian Gómez 

> Hi, What I do to connect the FreeRunner to the PC is running this script
> [1] that I've made with the things listed on the wiki. To run it just type
> sudo sh usb_networking.sh.
>
> I used it on Arch Linux and Ubuntu and I think it works on every distro as
> well. Any changes, suggestions are welcome. Currently it's on spanish.
>
> Note: The script is configured for SHR so it uses the eth1 interface not
> the usb0
>
> [1] http://www.mediafire.com/download.php?zm0gtz2tyjq
>
> /***
> * Don't Worry...Be Linux
> * Cristian Gómez Alvarez
> * Ingeniero en Sistemas y Computación
> * Universidad de Caldas
> * Comunidad de Software Libre Manizales
> * IEEE/WIE Student Member
> * Linux User #463617
> * Mi Blog: http://cristianpark.sehablalinux.com/
> /
>
>
> 2009/10/6 Matthias Huber 
>
>>  Tony Berth schrieb:
>>
>> On Tue, Oct 6, 2009 at 10:00 PM, Frederik Sdun <
>> frederik.s...@googlemail.com> wrote:
>>
>>> * Tony Berth  [06.10.2009 18:06]:
>>>  >followed as described in:
>>> >
>>> >http://wiki.openmoko.org/wiki/USB_Networking
>>> >
>>> >-
>>> >
>>> >   Ubuntu 9.04 - the Jaunty Jackalope -- udev
>>> >
>>> >One can see /etc/udev/rules.d that a device plugged in on USB will
>>> be
>>> >called eth1. Go to system->Administration->Network and add the
>>> parameters
>>> >for eth1 < static ip, address 192.168.0.200 mask 255.255.255.192 add
>>> your
>>> >default gateway>. Thats is all.
>>> >
>>> >Tested with Qi bootloader aka official MAC address of the Freerunner
>>> : on
>>> >Android Koolu beta 7
>>> >
>>> >Carig Philippines --frank 14:11, 17 June 2009 (UTC)
>>> >
>>> >--
>>> >
>>> >and eth1 gets assigned the proper IP address. I can connect to Neo
>>> but
>>> >from there I don't have any connection to the 'outside'. Please
>>> notice
>>> >that resolv.conf has the correct Opendns IPs!
>>> >
>>> >Actually I should face the same problem as described in:
>>> >
>>> >http://lists.openmoko.org/nabble.html#nabble-td3119750
>>> >
>>> >but the postings there weren't of any help :(
>>> >
>>> >Thanks
>>> >
>>> >Tony
>>>  I used the config you can find in [0] and it works.
>>>
>>>
>>> [0]
>>> http://wiki.openmoko.org/wiki/USB_Networking#Debian.2C_Ubuntu_and_others
>>> > ___
>>>
>>>
>> but this one 'ties' it in usb0 although it connects as eth1! How can this
>> work?
>>
>> I also used the following entries in /etc/network/interfaces:
>>
>> #freerunner3
>> allow-hotplug eth1
>> iface eth1 inet static
>> address 192.168.0.200
>> netmask 255.255.255.0
>> network 192.168.0.0
>> up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
>> up echo 1 > /proc/sys/net/ipv4/ip_forward &
>> up iptables -P FORWARD ACCEPT &
>> down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
>>
>> and didn't work! Openmoko wasn't able to get an IP address at all!
>>
>> get ip adress ? dont understand this.
>>
>> but i had to add this two lines to my /etc/ufw/ufw.conf
>>
>> ufw allow from 192.168.0.202
>> ufw allow to 192.168.0.202
>>
>>
>> another trial with iptables needs to load some modules too:
>>
>> #!/bin/sh
>>
>> MOKO=192.168.0.202
>>
>> echo 1 > /proc/sys/net/ipv4/ip_forward
>> modprobe ipt_MASQUERADE
>>
>> iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
>> iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
>> iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32
>>
>>
>> --
>> Mit freundlichen Grüssen
>> Matthias Huber
>> Kohlstattstr. 14
>> 86459 Wollishausen
>> Tel: 08238-7998
>> LPI000181125
>>
>>
>> ___
>> Openmoko community mailing list
>> community@lists.openmoko.org
>> http://lists.openmoko.org/mailman/listinfo/community
>>
>>
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>
>
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking with Ubuntu 9.04

2009-10-06 Thread Cristian Gómez
Hi, What I do to connect the FreeRunner to the PC is running this script [1]
that I've made with the things listed on the wiki. To run it just type sudo
sh usb_networking.sh.

I used it on Arch Linux and Ubuntu and I think it works on every distro as
well. Any changes, suggestions are welcome. Currently it's on spanish.

Note: The script is configured for SHR so it uses the eth1 interface not the
usb0

[1] http://www.mediafire.com/download.php?zm0gtz2tyjq

/***
* Don't Worry...Be Linux
* Cristian Gómez Alvarez
* Ingeniero en Sistemas y Computación
* Universidad de Caldas
* Comunidad de Software Libre Manizales
* IEEE/WIE Student Member
* Linux User #463617
* Mi Blog: http://cristianpark.sehablalinux.com/
/


2009/10/6 Matthias Huber 

>  Tony Berth schrieb:
>
> On Tue, Oct 6, 2009 at 10:00 PM, Frederik Sdun <
> frederik.s...@googlemail.com> wrote:
>
>> * Tony Berth  [06.10.2009 18:06]:
>>  >followed as described in:
>> >
>> >http://wiki.openmoko.org/wiki/USB_Networking
>> >
>> >-
>> >
>> >   Ubuntu 9.04 - the Jaunty Jackalope -- udev
>> >
>> >One can see /etc/udev/rules.d that a device plugged in on USB will be
>> >called eth1. Go to system->Administration->Network and add the
>> parameters
>> >for eth1 < static ip, address 192.168.0.200 mask 255.255.255.192 add
>> your
>> >default gateway>. Thats is all.
>> >
>> >Tested with Qi bootloader aka official MAC address of the Freerunner
>> : on
>> >Android Koolu beta 7
>> >
>> >Carig Philippines --frank 14:11, 17 June 2009 (UTC)
>> >
>> >--
>> >
>> >and eth1 gets assigned the proper IP address. I can connect to Neo
>> but
>> >from there I don't have any connection to the 'outside'. Please
>> notice
>> >that resolv.conf has the correct Opendns IPs!
>> >
>> >Actually I should face the same problem as described in:
>> >
>> >http://lists.openmoko.org/nabble.html#nabble-td3119750
>> >
>> >but the postings there weren't of any help :(
>> >
>> >Thanks
>> >
>> >Tony
>>  I used the config you can find in [0] and it works.
>>
>>
>> [0]
>> http://wiki.openmoko.org/wiki/USB_Networking#Debian.2C_Ubuntu_and_others
>> > ___
>>
>>
> but this one 'ties' it in usb0 although it connects as eth1! How can this
> work?
>
> I also used the following entries in /etc/network/interfaces:
>
> #freerunner3
> allow-hotplug eth1
> iface eth1 inet static
> address 192.168.0.200
> netmask 255.255.255.0
> network 192.168.0.0
> up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
> up echo 1 > /proc/sys/net/ipv4/ip_forward &
> up iptables -P FORWARD ACCEPT &
> down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
>
> and didn't work! Openmoko wasn't able to get an IP address at all!
>
> get ip adress ? dont understand this.
>
> but i had to add this two lines to my /etc/ufw/ufw.conf
>
> ufw allow from 192.168.0.202
> ufw allow to 192.168.0.202
>
>
> another trial with iptables needs to load some modules too:
>
> #!/bin/sh
>
> MOKO=192.168.0.202
>
> echo 1 > /proc/sys/net/ipv4/ip_forward
> modprobe ipt_MASQUERADE
>
> iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
> iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
> iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32
>
>
> --
> Mit freundlichen Grüssen
> Matthias Huber
> Kohlstattstr. 14
> 86459 Wollishausen
> Tel: 08238-7998
> LPI000181125
>
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>
>
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking with Ubuntu 9.04

2009-10-06 Thread Matthias Huber

Tony Berth schrieb:
On Tue, Oct 6, 2009 at 10:00 PM, Frederik Sdun 
mailto:frederik.s...@googlemail.com>> 
wrote:


* Tony Berth mailto:tonybe...@googlemail.com>> [06.10.2009 18:06]:
>followed as described in:
>
>http://wiki.openmoko.org/wiki/USB_Networking
>
>-
>
>   Ubuntu 9.04 - the Jaunty Jackalope -- udev
>
>One can see /etc/udev/rules.d that a device plugged in on USB
will be
>called eth1. Go to system->Administration->Network and add
the parameters
>for eth1 < static ip, address 192.168.0.200 mask
255.255.255.192 add your
>default gateway>. Thats is all.
>
>Tested with Qi bootloader aka official MAC address of the
Freerunner : on
>Android Koolu beta 7
>
>Carig Philippines --frank 14:11, 17 June 2009 (UTC)
>
>--
>
>and eth1 gets assigned the proper IP address. I can connect
to Neo but
>from there I don't have any connection to the 'outside'.
Please notice
>that resolv.conf has the correct Opendns IPs!
>
>Actually I should face the same problem as described in:
>
>http://lists.openmoko.org/nabble.html#nabble-td3119750
>
>but the postings there weren't of any help :(
>
>Thanks
>
>Tony
I used the config you can find in [0] and it works.


[0]
http://wiki.openmoko.org/wiki/USB_Networking#Debian.2C_Ubuntu_and_others
> ___


but this one 'ties' it in usb0 although it connects as eth1! How can 
this work?


I also used the following entries in /etc/network/interfaces:

#freerunner3
allow-hotplug eth1
iface eth1 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 
 &

up echo 1 > /proc/sys/net/ipv4/ip_forward &
up iptables -P FORWARD ACCEPT &
down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 
 &


and didn't work! Openmoko wasn't able to get an IP address at all!

get ip adress ? dont understand this.

but i had to add this two lines to my /etc/ufw/ufw.conf

ufw allow from 192.168.0.202
ufw allow to 192.168.0.202


another trial with iptables needs to load some modules too:

#!/bin/sh

MOKO=192.168.0.202

echo 1 > /proc/sys/net/ipv4/ip_forward
modprobe ipt_MASQUERADE

iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32


--
Mit freundlichen Grüssen
Matthias Huber 
Kohlstattstr. 14

86459 Wollishausen
Tel: 08238-7998
LPI000181125

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking with Ubuntu 9.04

2009-10-06 Thread Tony Berth
On Tue, Oct 6, 2009 at 10:00 PM, Frederik Sdun  wrote:

> * Tony Berth  [06.10.2009 18:06]:
> >followed as described in:
> >
> >http://wiki.openmoko.org/wiki/USB_Networking
> >
> >-
> >
> >   Ubuntu 9.04 - the Jaunty Jackalope -- udev
> >
> >One can see /etc/udev/rules.d that a device plugged in on USB will be
> >called eth1. Go to system->Administration->Network and add the
> parameters
> >for eth1 < static ip, address 192.168.0.200 mask 255.255.255.192 add
> your
> >default gateway>. Thats is all.
> >
> >Tested with Qi bootloader aka official MAC address of the Freerunner :
> on
> >Android Koolu beta 7
> >
> >Carig Philippines --frank 14:11, 17 June 2009 (UTC)
> >
> >--
> >
> >and eth1 gets assigned the proper IP address. I can connect to Neo but
> >from there I don't have any connection to the 'outside'. Please notice
> >that resolv.conf has the correct Opendns IPs!
> >
> >Actually I should face the same problem as described in:
> >
> >http://lists.openmoko.org/nabble.html#nabble-td3119750
> >
> >but the postings there weren't of any help :(
> >
> >Thanks
> >
> >Tony
> I used the config you can find in [0] and it works.
>
>
> [0]
> http://wiki.openmoko.org/wiki/USB_Networking#Debian.2C_Ubuntu_and_others
> > ___
>
>
but this one 'ties' it in usb0 although it connects as eth1! How can this
work?

I also used the following entries in /etc/network/interfaces:

#freerunner3
allow-hotplug eth1
iface eth1 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
up echo 1 > /proc/sys/net/ipv4/ip_forward &
up iptables -P FORWARD ACCEPT &
down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &

and didn't work! Openmoko wasn't able to get an IP address at all!

Thanks

Tony
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking with Ubuntu 9.04

2009-10-06 Thread Frederik Sdun
* Tony Berth  [06.10.2009 18:06]:
>followed as described in:
> 
>http://wiki.openmoko.org/wiki/USB_Networking
> 
>-
> 
>   Ubuntu 9.04 - the Jaunty Jackalope -- udev
> 
>One can see /etc/udev/rules.d that a device plugged in on USB will be
>called eth1. Go to system->Administration->Network and add the parameters
>for eth1 < static ip, address 192.168.0.200 mask 255.255.255.192 add your
>default gateway>. Thats is all.
> 
>Tested with Qi bootloader aka official MAC address of the Freerunner : on
>Android Koolu beta 7
> 
>Carig Philippines --frank 14:11, 17 June 2009 (UTC)
> 
>--
> 
>and eth1 gets assigned the proper IP address. I can connect to Neo but
>from there I don't have any connection to the 'outside'. Please notice
>that resolv.conf has the correct Opendns IPs!
> 
>Actually I should face the same problem as described in:
> 
>http://lists.openmoko.org/nabble.html#nabble-td3119750
> 
>but the postings there weren't of any help :(
> 
>Thanks
> 
>Tony
I used the config you can find in [0] and it works.


[0] http://wiki.openmoko.org/wiki/USB_Networking#Debian.2C_Ubuntu_and_others
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community


-- 
IRC: playya @ Freenode, Gimpnet
xmpp: pla...@draugr.de


signature.asc
Description: Digital signature
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


USB networking with Ubuntu 9.04

2009-10-06 Thread Tony Berth
followed as described in:

http://wiki.openmoko.org/wiki/USB_Networking

-
 Ubuntu 9.04 - the Jaunty Jackalope -- udev

One can see /etc/udev/rules.d that a device plugged in on USB will be called
*eth1*. Go to system->Administration->Network and add the parameters for
eth1 < static ip, address 192.168.0.200 mask 255.255.255.192 add your
default gateway>. Thats is all.

Tested with Qi bootloader aka official MAC address of the Freerunner : on
Android Koolu beta 7

Carig Philippines
--frank14:11,
17 June 2009 (UTC)

--

and eth1 gets assigned the proper IP address. I can connect to Neo but from
there I don't have any connection to the 'outside'. Please notice that
resolv.conf has the correct Opendns IPs!


Actually I should face the same problem as described in:

http://lists.openmoko.org/nabble.html#nabble-td3119750

but the postings there weren't of any help :(


Thanks


Tony
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking disabled

2009-09-10 Thread Neil M. Stewart
I now have it working. I changed the USB networking related features
including cdc-ether as built-in, as opposed to modules, which was the
original configuration.

On Thu, Sep 10, 2009 at 4:31 AM, arne anka  wrote:
> - is cdc-ether built-in or a module?
> - how do you make sure it is not recognized? syslog?
> - das the log say anything at all about usb?
> - what exactly are you seeing when pluggin in the fr on the host side?
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: udev rule for the freerunner or make usb networking enduser friendly

2009-09-10 Thread Al Johnson
On Thursday 10 September 2009, Olivier Migeot wrote:
> On Thu, Sep 10, 2009 at 1:26 PM, Al Johnson
>
>  wrote:
> > Check dnsmasq which is available in OE, and provides a lightweight
> > caching DNS server and DHCP server. I don't know if it's in the SHR feeds
> > or not, but it worked well when I tried it a while back.
>
> How lighter could it be than a /bin/busybox symlink? ;)

I thought busybox only did the client end. Good to know I was wrong :-)


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: udev rule for the freerunner or make usb networking enduser friendly

2009-09-10 Thread Olivier Migeot
On Thu, Sep 10, 2009 at 1:26 PM, Al Johnson
 wrote:

> Check dnsmasq which is available in OE, and provides a lightweight caching DNS
> server and DHCP server. I don't know if it's in the SHR feeds or not, but it
> worked well when I tried it a while back.

How lighter could it be than a /bin/busybox symlink? ;)

Plus I don't really need the DNS part. But thanks anyway.

-- 
Olivier

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: udev rule for the freerunner or make usb networking enduser friendly

2009-09-10 Thread Al Johnson
On Wednesday 02 September 2009, Olivier Migeot wrote:
> On Wed, Sep 2, 2009 at 6:41 AM, c_c wrote:
> > Hi,
> >  Same here - just a static ip for the fr's mac address on ubuntu works
> > great for me.
>
> I've been on static IP for quite a while, but between work and home it
> was starting to get messy. With udhcpd, it's now much more convenient.
> I could even decide to change the Moko's network for something less
> common than 192.168.0.0 at no cost.
>
> The best would be to have a very light dhcpd daemon who only runs on
> USB insertion, serves only one address with a very long lease, and
> then dies after a few minutes. But maybe I'm dreaming there ;)

Check dnsmasq which is available in OE, and provides a lightweight caching DNS 
server and DHCP server. I don't know if it's in the SHR feeds or not, but it 
worked well when I tried it a while back.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking disabled

2009-09-10 Thread arne anka
- is cdc-ether built-in or a module?
- how do you make sure it is not recognized? syslog?
- das the log say anything at all about usb?
- what exactly are you seeing when pluggin in the fr on the host side?

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking disabled

2009-09-10 Thread arne anka
> I just posted a message on the smartphone mailing-list about a similar
> problem I have.

according to your description on smartphone-users, yours is totally  
different an issue (and i answered with a way to fix that).
you simply fell in the well known qi/udev trap, while the op according to  
his description does not get any cdc ether device at all.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking disabled

2009-09-09 Thread Rask Ingemann Lambertsen
On Wed, Sep 09, 2009 at 03:33:50PM -0400, Stefan Monnier wrote:

> I just posted a message on the smartphone mailing-list about a similar
> problem I have.  In my case the USB netowkring fails when I boot with
> Qi, but works when I boot with U-Boot.

   IIRC, Qi adds kernel parameters in an attempt to set the Ethernet address
used by the Freerunner's CDC Ethernet device. If you have the 'lsusb'
command on the system you're connecting to the Freerunner, what does it say?

-- 
Rask Ingemann Lambertsen
Danish law requires addresses in e-mail to be logged and stored for a year

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking disabled

2009-09-09 Thread Stefan Monnier
> I recently compile the latest andy-tracking branch of the kernel
> (GTA02_mystable-a3587e4ed77974ad), however the usb networking feature
> is no longer operational.
> Prior to installing the new kernel, my Linux system would recognize
> the Neo Freerunner as a CDC Ethernet device, now it no longer
> recognizes the device once it is attached.
> I used the gta02_moredrivers_defconfig in the build process. Does
> anyone know what might be causing this issue?
> Thanks in advance for you help.

I just posted a message on the smartphone mailing-list about a similar
problem I have.  In my case the USB netowkring fails when I boot with
Qi, but works when I boot with U-Boot.


Stefan


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


USB Networking disabled

2009-09-09 Thread Neil M. Stewart
Hi List,

I recently compile the latest andy-tracking branch of the kernel
(GTA02_mystable-a3587e4ed77974ad), however the usb networking feature
is no longer operational.
Prior to installing the new kernel, my Linux system would recognize
the Neo Freerunner as a CDC Ethernet device, now it no longer
recognizes the device once it is attached.
I used the gta02_moredrivers_defconfig in the build process. Does
anyone know what might be causing this issue?
Thanks in advance for you help.

Regards,
Neil Stewart

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: udev rule for the freerunner or make usb networking enduser friendly

2009-09-02 Thread Olivier Migeot
On Wed, Sep 2, 2009 at 6:41 AM, c_c wrote:
>
> Hi,
>  Same here - just a static ip for the fr's mac address on ubuntu works
> great for me.
I've been on static IP for quite a while, but between work and home it
was starting to get messy. With udhcpd, it's now much more convenient.
I could even decide to change the Moko's network for something less
common than 192.168.0.0 at no cost.

The best would be to have a very light dhcpd daemon who only runs on
USB insertion, serves only one address with a very long lease, and
then dies after a few minutes. But maybe I'm dreaming there ;)

-- 
Olivier

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: udev rule for the freerunner or make usb networking enduser friendly

2009-09-01 Thread c_c

Hi,
  Same here - just a static ip for the fr's mac address on ubuntu works
great for me.

-- 
View this message in context: 
http://n2.nabble.com/udev-rule-for-the-freerunner-or-make-usb-networking-enduser-friendly-tp3554706p3564747.html
Sent from the Openmoko Community mailing list archive at Nabble.com.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: udev rule for the freerunner or make usb networking enduser friendly

2009-09-01 Thread Helge Hafting
Radek Polak wrote:
> Laszlo KREKACS wrote:
> 
>> I would like to use my freerunner in a plug&play mode. Just attach to the
>> computer, and simply ssh in using terminal or nautilus.
> 
> You have to setup dhcp server on your freerunner. E.g. on debian:

Seems like a lot of effort, I find it easier to set up static 
192.168.0.200 for eth1 on the computer. This avoids running a dhcp
server on the rather limited phone.

Still, the dhcp server may be easier if you regularly connect to many 
different computers.

Helge Hafting

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: udev rule for the freerunner or make usb networking enduser friendly

2009-09-01 Thread Jose Luis Perez Diez
El Monday, 31 de August de 2009 18:40:33 Laszlo KREKACS va escriure:
> Hi!
>
> I would like to use my freerunner in a plug&play mode. Just attach to the
> computer, and simply ssh in using terminal or nautilus.

I've it working on leny with the following configs:

on /etc/udev/rules.d/70-persistent-net.rules I force the frerruner to be usb0 
see (http://wiki.openmoko.org/wiki/OUI):

# USB device 0x1457:0x5122 (cdc_ether) freeruner
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", \
ATTR{address}=="00:1f:11:??:??:??", ATTR{type}=="1", KERNEL=="eth*", \
NAME="usb0"

set /etc/network/interfaces  and /etc/network/freerunner as tell in the wiki 
page:
http://wiki.openmoko.org/wiki/Usb_networking#Masquerading_support

and for $HOME/.ssh/config use: 
http://wiki.openmoko.org/wiki/Usb_networking#Changing_host_keys

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: udev rule for the freerunner or make usb networking enduser friendly

2009-08-31 Thread Radek Polak
Laszlo KREKACS wrote:

> I would like to use my freerunner in a plug&play mode. Just attach to the
> computer, and simply ssh in using terminal or nautilus.

You have to setup dhcp server on your freerunner. E.g. on debian:

apt-get install dhcp3-server

edit dhcp server configuration:

nano /etc/dhcp3/dhcpd.conf

and place something like this there:

option domain-name-servers 208.67.222.222, 208.67.220.220;
option routers 192.168.0.202;

subnet 192.168.0.0 netmask 255.255.255.0 {
option routers 192.168.0.1;

 # Unknown clients get this pool.
 pool {
   #option domain-name-servers bogus.example.com;
   max-lease-time 7200;
   range 192.168.0.200 192.168.0.201;
   allow unknown clients;
 }
}

Now restart dhcps server:

/etc/init.d/dhcp3-server restart

plug your Freerunner and NetworkManager should always assign the right
IP address.

Regards

Radek


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: udev rule for the freerunner or make usb networking enduser friendly

2009-08-31 Thread Paul Fertser
Laszlo KREKACS  writes:
> The current way is really hard to teach for a nonexperienced user
> (ie. gf), how to upload musics to the "music player device".;-\

Hahaha, a gf capable of applying the "bass fix" shouldn't need much
help disabling NM and adding several trivial strings to
/etc/network/interfaces (Debian) or /etc/conf.d/net (Gentoo).

Really, the way you propose is wrong, you need to use your OS's
facilities, all modern distros support proper hotplug and configuring
of network devices. 

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


udev rule for the freerunner or make usb networking enduser friendly

2009-08-31 Thread Laszlo KREKACS
Hi!

I would like to use my freerunner in a plug&play mode. Just attach to the
computer, and simply ssh in using terminal or nautilus.

Currently 2 things break the above experience:
1. I need to issue manually the following command:
sudo ip address add 192.168.0.200/24 dev eth3

If you use two freerunner, it will get different ethX interface (eth2 vs. eth3)
which is rather annoying.
There is ifrename (http://linux.die.net/man/8/ifrename), which could fix it.

2. After some seconds (30-40 sec) the connection is broken. I need to
reissue the above command, and after it does not break anymore.
I highly suspect Networkmanager is f*cking with me.


So the question is, can it be written an udev rule, which do the above
things automatically, and also stop disconnecting the freerunner?

The current way is really hard to teach for a nonexperienced user (ie. gf),
how to upload musics to the "music player device".;-\

Best regards,
 Laszlo

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [Om2009] Still no usb networking from windows ?

2009-07-15 Thread Paul Fertser
Xavier Cremaschi  writes:
> I don't think I am the only one who uses Microsoft Windows at work...

Just tried to attach my FR to a coworker's PC running windows
xpsp3. It just works with the inf file from wiki.

I run the latest andy-tracking kernel.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


[Om2009] Still no usb networking from windows ?

2009-07-15 Thread Xavier Cremaschi
Hi folks,
I don't think I am the only one who uses Microsoft Windows at work...

The last time I succeeded in ssh-ing from Windows to my FR I was using 
Om2008 (or maybe an early version of SHR)...

Since this time (January 2009 ?), the kernel used by SHR and Om2009 
doesn't seem to support the windows 'driver' (the .inf file available on 
the wiki).

As I don't want to boot on deb...@microsd (kernel 2.6.24) and chroot, 
does anyone have a solution to ssh from a windows xp to a FR with Om2009 ?

Thanks,
Xavier.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking MAC regression (aka the usb0 -> eth0 change)

2009-05-24 Thread Johny Tenfinger
On Sun, May 24, 2009 at 16:34, Nicolas Cavallari  wrote:
> I don't want to try SHR-unstable right now (i use my FR as my main phone), 
> but hacking the
> g_ether.sh script to do the same thing also fix the problem.

Well, for me SHR-unstable is more usable as daily phone than
SHR-testing, but that's only my opinion and off-topic :)

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking MAC regression (aka the usb0 -> eth0 change)

2009-05-24 Thread Nicolas Cavallari
>> Johny Tenfinger wrote :
>>> On Sat, May 23, 2009 at 17:05, Nicolas Cavallari  wrote:
 This worked fine during the usb0 phase. But since the distro started using 
 the official
 MAC address, This wouldn't work anymore.
>>> Which distro? In SHR-unstable it should be fixed for long time, but in
>>> others, where kernel is using arguments passed by Qi (dunno if Om2009
>>> is using Qi or SHR way for settings MAC address...) it isn't, because
>>> of bug in Qi.
> On Sat, May 23, 2009 at 19:33, Nicolas Cavallari  wrote:
>> It's the latest SHR Testing. 
>> but my Qi installation may not be up to date...

Screw that, Qi was up to date.

Johny Tenfinger wrote :
> 
> Try latest SHR-unstable. It should be really better than -testing, and
> it should have it fixed (not depending to bootloader).

>From what i saw, unstable does just increment the host mac adress if the 
>device and the host mac are
the same, just like Paul Fertser's Qi patch on the kernel@ mailling list.

I don't want to try SHR-unstable right now (i use my FR as my main phone), but 
hacking the
g_ether.sh script to do the same thing also fix the problem.


I also created a ticket on trac, as suggested :
https://docs.openmoko.org/trac/ticket/2290

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking MAC regression (aka the usb0 -> eth0 change)

2009-05-23 Thread Paul Fertser
Hi,

Nicolas Cavallari  writes:
> For a while, I used to use USB networking to connect my FR to the interwebs.
[snip]
> The bridge fails because it consider the host mac address to be a local mac 
> (brctl showmacs) and
> so ignore any host with the same mac. Changing the host mac address (with 
> ifconfig ethXXX hw ether)
> solves the problem, but it clearly not a acceptable solution.

Thanks for reporting. I've just sent a patch to the kernel ML that
should fix the issue.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking MAC regression (aka the usb0 -> eth0 change)

2009-05-23 Thread Johny Tenfinger
On Sat, May 23, 2009 at 19:33, Nicolas Cavallari  wrote:
> Johny Tenfinger a écrit :
>> On Sat, May 23, 2009 at 17:05, Nicolas Cavallari  wrote:
>>> This worked fine during the usb0 phase. But since the distro started using 
>>> the official
>>> MAC address, This wouldn't work anymore.
>>
>> Which distro? In SHR-unstable it should be fixed for long time, but in
>> others, where kernel is using arguments passed by Qi (dunno if Om2009
>> is using Qi or SHR way for settings MAC address...) it isn't, because
>> of bug in Qi.
>
> It's the latest SHR Testing. but my Qi installation may not be up to date...

Try latest SHR-unstable. It should be really better than -testing, and
it should have it fixed (not depending to bootloader).

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking MAC regression (aka the usb0 -> eth0 change)

2009-05-23 Thread Nicolas Cavallari
Johny Tenfinger a écrit :
> On Sat, May 23, 2009 at 17:05, Nicolas Cavallari  wrote:
>> This worked fine during the usb0 phase. But since the distro started using 
>> the official
>> MAC address, This wouldn't work anymore.
> 
> Which distro? In SHR-unstable it should be fixed for long time, but in
> others, where kernel is using arguments passed by Qi (dunno if Om2009
> is using Qi or SHR way for settings MAC address...) it isn't, because
> of bug in Qi.

It's the latest SHR Testing. but my Qi installation may not be up to date...

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking MAC regression (aka the usb0 -> eth0 change)

2009-05-23 Thread Johny Tenfinger
On Sat, May 23, 2009 at 17:05, Nicolas Cavallari  wrote:
> This worked fine during the usb0 phase. But since the distro started using 
> the official
> MAC address, This wouldn't work anymore.

Which distro? In SHR-unstable it should be fixed for long time, but in
others, where kernel is using arguments passed by Qi (dunno if Om2009
is using Qi or SHR way for settings MAC address...) it isn't, because
of bug in Qi.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


USB networking MAC regression (aka the usb0 -> eth0 change)

2009-05-23 Thread Nicolas Cavallari
For a while, I used to use USB networking to connect my FR to the interwebs.

I wanted to be able to connect my moko to any computer and let my entire LAN 
talk to it,
so instead of using masquerading or routing, i used the much simpler bridge 
mechanism,
to bridge my FR with my network.

This worked fine during the usb0 phase. But since the distro started using the 
official
MAC address, This wouldn't work anymore.


I traced this problem down to the fact that both the host NIC and the device 
NIC share the
same mac address. I wonder if this is a deliberate change (i hope not), because 
this not only break
bridging, but it would break many other advanced network configurations.

The bridge fails because it consider the host mac address to be a local mac 
(brctl showmacs) and
so ignore any host with the same mac. Changing the host mac address (with 
ifconfig ethXXX hw ether)
solves the problem, but it clearly not a acceptable solution.

What should i do instead ? Should i report this as a bug ?

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking now creates eth1 on host

2009-05-14 Thread Paul Fertser
reznor  writes:
> You just have to know what's going on and then it's easy. That information
> should have been distributed a few months ago and that way that everyone
> gets it who uses Qi. At the fyp forums nobody seemed to know.

You see? Fyp community is disconnected because they use forums, QOD.

Here [1] the change was described in all details along with
justifications. Also the wiki page was updated accordingly.

And to be honest i just can't understand why it created so much
confusion because it's plain obvious from reading host's dmesg right
after inserting FR, really.

[1] http://lists.openmoko.org/pipermail/devel/2009-April/005384.html

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking now creates eth1 on host

2009-05-14 Thread reznor

22. April, that's only 3-4 weeks ago, a bit late. Some people just stopped
using Qi because of that months ago and lost interest also, just like me.
But finally the message arrives. -.-



Nelson Castillo-2 wrote:
> 
> On Thu, May 14, 2009 at 5:35 PM, reznor  wrote:
>>
>> Works with Qi.
>> You just have to know what's going on and then it's easy. That
>> information
>> should have been distributed a few months ago and that way that everyone
>> gets it who uses Qi. At the fyp forums nobody seemed to know.
> 
> Hello.
> 
> Check this:
> 
> http://lists.openmoko.org/pipermail/devel/2009-April/005384.html
> 
> Nelson.-
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
> 
> 

-- 
View this message in context: 
http://n2.nabble.com/-neovento-5--applications%21-tp2881940p2904213.html
Sent from the Openmoko Community mailing list archive at Nabble.com.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking now creates eth1 on host

2009-05-14 Thread Nelson Castillo
On Thu, May 14, 2009 at 5:35 PM, reznor  wrote:
>
> Works with Qi.
> You just have to know what's going on and then it's easy. That information
> should have been distributed a few months ago and that way that everyone
> gets it who uses Qi. At the fyp forums nobody seemed to know.

Hello.

Check this:

http://lists.openmoko.org/pipermail/devel/2009-April/005384.html

Nelson.-

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking now creates eth1 on host

2009-05-14 Thread reznor

Works with Qi. 
You just have to know what's going on and then it's easy. That information
should have been distributed a few months ago and that way that everyone
gets it who uses Qi. At the fyp forums nobody seemed to know.

-- 
View this message in context: 
http://n2.nabble.com/-neovento-5--applications%21-tp2881940p2903754.html
Sent from the Openmoko Community mailing list archive at Nabble.com.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Every web-forum sucks by definition, isn't it obvious? (was: Re: USB networking now creates eth1 on host)

2009-05-14 Thread Paul Fertser
reznor  writes:
> Excuse me, but for not wanting to be offensive you are writing some really
> arrogant crap.

:D

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking now creates eth1 on host

2009-05-14 Thread reznor


Paul Fertser wrote:
> 
> Heh, my remark wasn't meant to be offensive, take it easy ;)
> 
> The problem is that i feel neovento guys are separating from the
> developers community by not using our mailing lists and IRC. I've
> heard you're using some web-forum (is it really true?) i can't imagine
> you'll get any help from the other devs using such a crappy method.
> 
neovento is not such a professional distribution like all the others like
SHR, Android, OM and so on. Additionally it is quite new. I started it just
about four months ago as a one man fun thing. That it actually turned into
something useful for some people is nice. I think you have a completely
wrong idea of the whole thing.

We have one thread on the fyp forum, that's right. It's just for some
communication within that community. I actually don't know what's crappy on
that and why we need so much help from the devs? When there were issues I
just mailed into the debianonfreerunner mailinglist and got response.

Excuse me, but for not wanting to be offensive you are writing some really
arrogant crap.




-- 
View this message in context: 
http://n2.nabble.com/-neovento-5--applications%21-tp2881940p2889594.html
Sent from the Openmoko Community mailing list archive at Nabble.com.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking now creates eth1 on host (was: Re: [neovento 5] applications!)

2009-05-14 Thread arne anka
>> Why do you suggest this instead of using the correct method?!
>>
> Why didn't you suggest the correct method before, though you knew the
> correct method all the time???

it was suggested -- at least once and i repeated it after seeing that  
apparently no one cared to read that.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking now creates eth1 on host

2009-05-14 Thread Paul Fertser
reznor  writes:
> Paul Fertser wrote:
>> 
>> Why do you suggest this instead of using the correct method?!
>> 
> Why didn't you suggest the correct method before, though you knew the
> correct method all the time???

Sorry, i was a bit busy and the thread called "neovento apps" wasn't
of the most interest to me so i've read it a bit later, just
that. Moreover, the problem is obvious from the host's dmesg.

>> I wonder why you neovento guys don't read kernel mailing list, devel
>> mailing list where this was elaborated in details, why you never come
>> to IRC to discuss low-level issues etc.
> Lack of motivation and time. This is only some hobby, we spend as much time
> in it as we consider being appropriate. You guys can just ignore the
> neovento guys. So what's the problem?
> As long there won't be any usable distributions for my freerunner, I'll make
> my own. Easy, right?

Heh, my remark wasn't meant to be offensive, take it easy ;)

The problem is that i feel neovento guys are separating from the
developers community by not using our mailing lists and IRC. I've
heard you're using some web-forum (is it really true?) i can't imagine
you'll get any help from the other devs using such a crappy method.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking now creates eth1 on host (was: Re: [neovento 5] applications!)

2009-05-14 Thread reznor


Paul Fertser wrote:
> 
> Why do you suggest this instead of using the correct method?!
> 
Why didn't you suggest the correct method before, though you knew the
correct method all the time???


Paul Fertser wrote:
> 
> The guy obviously got eth1 on host. Every time. He should have used it
> instead of finding older incorrectly working versions of bootloaders.
> 
> The reason is simple: since Qi was fixed to properly provide
> factory-configured MAC address for the usb networking interface, it's
> detected on the host as it should, every time udev sees that device
> it'll assign the same static interface to it (in the simplest case
> it'll be eth1), that's the main improvement actually! 
Ok, Ill try that.


Paul Fertser wrote:
> 
> I wonder why you neovento guys don't read kernel mailing list, devel
> mailing list where this was elaborated in details, why you never come
> to IRC to discuss low-level issues etc.
Lack of motivation and time. This is only some hobby, we spend as much time
in it as we consider being appropriate. You guys can just ignore the
neovento guys. So what's the problem?
As long there won't be any usable distributions for my freerunner, I'll make
my own. Easy, right?
-- 
View this message in context: 
http://n2.nabble.com/-neovento-5--applications%21-tp2881940p2889485.html
Sent from the Openmoko Community mailing list archive at Nabble.com.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


USB networking now creates eth1 on host (was: Re: [neovento 5] applications!)

2009-05-13 Thread Paul Fertser
neovento  writes:
> Ok please try with Uboot. 
> There were often problems with Qi and debian kernels.

Why do you suggest this instead of using the correct method?!

The guy obviously got eth1 on host. Every time. He should have used it
instead of finding older incorrectly working versions of bootloaders.

The reason is simple: since Qi was fixed to properly provide
factory-configured MAC address for the usb networking interface, it's
detected on the host as it should, every time udev sees that device
it'll assign the same static interface to it (in the simplest case
it'll be eth1), that's the main improvement actually!

I wonder why you neovento guys don't read kernel mailing list, devel
mailing list where this was elaborated in details, why you never come
to IRC to discuss low-level issues etc.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [SHR unstable] no USB networking (with Windows)?

2009-02-27 Thread Vasco Névoa

There is also a closed ticket for the same bug (with different  
symptoms, but that should be a Windows problem I guess):
http://docs.openmoko.org/trac/ticket/1279

It looks like this patch is going in and out, or something... the  
problem comes and goes depending on kernel version...

Citando Paul Fertser :

> Vasco Névoa  writes:
>> Second, a weird problem I'm having... I updated my system with opkg
>> yesterday, and a bunch os problems were corrected (yay!) and I'm using
>> the phone in "everyday life", but now I can't login via SSH on my
>> windows box.
>
> http://docs.openmoko.org/trac/ticket//2211
>
> --
> Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
> mailto:fercer...@gmail.com
>


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [SHR unstable] no USB networking (with Windows)?

2009-02-27 Thread Vasco Névoa
Thanks Paul, that's exactly it.
So, it's most probably a 2.6.* USB driver problem and we'll have to  
wait for the kernel folks to get it right...

Citando Paul Fertser :

> Vasco Névoa  writes:
>> Second, a weird problem I'm having... I updated my system with opkg
>> yesterday, and a bunch os problems were corrected (yay!) and I'm using
>> the phone in "everyday life", but now I can't login via SSH on my
>> windows box.
>
> http://docs.openmoko.org/trac/ticket//2211
>
> --
> Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
> mailto:fercer...@gmail.com
>


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [SHR unstable] no USB networking (with Windows)?

2009-02-26 Thread Steve " 'dillo" Okay

On Feb 26, 2009, at 19:03 , Vasco Névoa wrote:

>
> Hi folks.
> First off, a BIG THANKS to the SHR team; this is the best distro I
> tried for GTA02 in a long while. :)
>
> Second, a weird problem I'm having... I updated my system with opkg
> yesterday, and a bunch os problems were corrected (yay!) and I'm using
> the phone in "everyday life", but now I can't login via SSH on my
> windows box.

Does SHR use dbus ?
Your USB net might have been turned off by default as a power saving  
measure.
This happened when I upgraded to the latest FSO unstable the other  
day and the AR6000
was turned off by default. Having read some of the discussion on  
Trac, this made sense in the end but it still took me a few minutes  
to figure out.

---Steve



> This works just fine if I reboot into the "Hackable:1" distro on the
> card and also worked fine with the OM2008.12/testing distro previously
> on flash.
> The "g_ether" module is loaded and the usb0 interface is UP and
> configured with the correct IP... but the Windows box just doesn't
> connect anymore. I don't have a Linux box here, I'll have to try much
> later on.
>
> Hints, anyone?
>
> Vasco.
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [SHR unstable] no USB networking (with Windows)?

2009-02-26 Thread Paul Fertser
Vasco Névoa  writes:
> Second, a weird problem I'm having... I updated my system with opkg  
> yesterday, and a bunch os problems were corrected (yay!) and I'm using  
> the phone in "everyday life", but now I can't login via SSH on my  
> windows box.

http://docs.openmoko.org/trac/ticket//2211

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


[SHR unstable] no USB networking (with Windows)?

2009-02-26 Thread Vasco Névoa

Hi folks.
First off, a BIG THANKS to the SHR team; this is the best distro I  
tried for GTA02 in a long while. :)

Second, a weird problem I'm having... I updated my system with opkg  
yesterday, and a bunch os problems were corrected (yay!) and I'm using  
the phone in "everyday life", but now I can't login via SSH on my  
windows box.
This works just fine if I reboot into the "Hackable:1" distro on the  
card and also worked fine with the OM2008.12/testing distro previously  
on flash.
The "g_ether" module is loaded and the usb0 interface is UP and  
configured with the correct IP... but the Windows box just doesn't  
connect anymore. I don't have a Linux box here, I'll have to try much  
later on.

Hints, anyone?

Vasco.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: e[sho]ternal usb networking problems

2009-01-18 Thread arne anka
i do not recall any specific error messages you posted.
but that might be because of the high traffic of this list.
so, please, specify what exactly does not work:
- what exactly are you trying to achieve? connecting your host via wlan to  
inet and accessing inet from your fr through usb to host?
- are you able to connect to your ap? does inet work?
- are you able to connect to/fro your pc via usb?
- did you enable forwarding and do you use different subnets?

please, post the output of
ifconfig -a
of both the host and fr. if you are behind a router (your wlan ap probably  
act as one), there's no need to obscure the ip addresses -- in fact they  
are necessary to narrow down your problem.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


e[sho]ternal usb networking problems

2009-01-17 Thread Harry L. Lee
i run ubuntu gutsy, i 've tried every approach in the usb networking doc,
except udev, and i can find no combination that gives me a wifi connection
to the Net (not  optional) AND usb connection to my freerunner. i'm planning
on thrashng at 8.10 on my netbook monday. at this point, i've basically
decided to throw up my hands and buy a g1 in 2 weeks on the logic that it is
actually a supported product. all i really want is working wifi on the
freerunner, which does not seem much to ask.

-- 
ha...@jonesnose.com
Harry L Lee (via gmail)
chief cook and bottle washer
http://jonesnose.com
mailto:ha...@jonesnose.com
207-384-8030 (email preferred)
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking

2008-11-28 Thread Michael Tansella
I think 
the seasiest way is to use wicd, it is much further in development than 
networkmanager. It doesnt'make any problems with Freerunner.

http://wicd.sourceforge.net/

Greets
Michael
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking

2008-11-07 Thread Stefan Monnier
> With Ubuntu 8.04 and 8.10 I've had 100% success on four or five different
> systems with:

> auto usb0
> iface usb0 inet static
> address 192.168.0.201
> netmask 255.255.255.252
> post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.202
> post-up iptables -I PREROUTING -i usb0 -p udp --dport 53 -j DNAT --to
> 192.168.0.254
> post-up echo 1 > /proc/sys/net/ipv4/ip_forward
> post-up iptables -P FORWARD ACCEPT
> pre-down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.202
> pre-down iptables -D PREROUTING -i usb0 -p udp --dport 53 -j DNAT --to
> 192.168.0.254


> in /etc/network/interfaces, and the fix noted on the wiki at
> http://wiki.openmoko.org/wiki/Usb_networking#Ubuntu_Issues

If you use "allow-hotplug" instead of "auto", it should work without
needing any "fix".


Stefan


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


RE: USB Networking

2008-11-06 Thread Joel Newkirk
On Thu, 6 Nov 2008 17:54:09 +, "Matthias Camenzind "
<[EMAIL PROTECTED]> wrote:
> I had also some problems with the Usb networking with ubuntu 8.04. But i
> could solve it with this: ifconfig usb0 192.168.0.200 netmask
255.255.255.0
> I had to enter it every time after i connected FR with my Computer or I
> rebooted the FR. But it worked fine. I found this solution in the Getting
> Started Guide for Neo 1973.
> Today network is automatically set up after connecting but today I don't
> know exactly what I did.
> 
> -Original Message-
> From: Denis Johnson <[EMAIL PROTECTED]>
> Sent: 11/6/2008 1:06:23 PM
> To: List for Openmoko community discussion 
> Subject: Re: USB Networking
> 
> 
> On Thu, Nov 6, 2008 at 9:06 PM, Tony Berth <[EMAIL PROTECTED]>
> wrote:
>> the wiki posted solution was tested by myself on a the currebt debian
> and
>> did work! Are you using the same environment?
> 
> I believe so, I'm using Ubuntu 8.10 but have had this problem since 8.04.

With Ubuntu 8.04 and 8.10 I've had 100% success on four or five different
systems with:

auto usb0
iface usb0 inet static
address 192.168.0.201
netmask 255.255.255.252
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.202
post-up iptables -I PREROUTING -i usb0 -p udp --dport 53 -j DNAT --to
192.168.0.254
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
pre-down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.202
pre-down iptables -D PREROUTING -i usb0 -p udp --dport 53 -j DNAT --to
192.168.0.254


in /etc/network/interfaces, and the fix noted on the wiki at
http://wiki.openmoko.org/wiki/Usb_networking#Ubuntu_Issues

NOTES: I use 192.168.0.201 on host and 192.168.0.202 on FR, with netmask of
/30 or 255.255.255.252 - to match 'standard' {dumb as I feel it is}
FreeRunner network setup, use 192.168.0.200 on host with 255.255.255.0 as
netmask.  Also, 192.168.0.254 is my local DNS server, hence the DNAT rule
forwarding DNS requests there (which I don't actually need anymore since I
use local dnscache on the FR).  In fact, none of the post-up and pre-down
parts affect me anymore as I utilize a static permanent ruleset to
accomplish this, so I leave them all commented out.

(and yes, 'auto' DOES work, provided the fix linked above is employed, and
works without it some times)

j



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


RE: USB Networking

2008-11-06 Thread Matthias Camenzind
I had also some problems with the Usb networking with ubuntu 8.04. But i could 
solve it with this: ifconfig usb0 192.168.0.200 netmask 255.255.255.0 
I had to enter it every time after i connected FR with my Computer or I 
rebooted the FR. But it worked fine. I found this solution in the Getting 
Started Guide for Neo 1973.
Today network is automatically set up after connecting but today I don't know 
exactly what I did.

-Original Message-
From: Denis Johnson <[EMAIL PROTECTED]>
Sent: 11/6/2008 1:06:23 PM
To: List for Openmoko community discussion 
Subject: Re: USB Networking


On Thu, Nov 6, 2008 at 9:06 PM, Tony Berth <[EMAIL PROTECTED]> wrote:
> the wiki posted solution was tested by myself on a the currebt debian and
> did work! Are you using the same environment?

I believe so, I'm using Ubuntu 8.10 but have had this problem since 8.04.

> On Thu, Nov 6, 2008 at 10:46 AM, Denis Johnson <[EMAIL PROTECTED]>
> wrote:
>>
>> I have had this setting for months it does not work for me.
>>
>> Whenever I want to connect my FR, I must first plug it in into the usb
>> and then run the following script which someone once posted here or on
>> the #openmoko irc. Until I run ths script I cannot ping and hence ssh
>> into the FR. Unfortunately I don't know enough to integrate and
>> automate what the script does into my interfaces file. If someone can
>> shed some more light, it would be appreciated:
>>
>> --
>> #!/bin/sh
>> # Enables Hostside USB-Networking for neo
>> ifconfig usb0 down
>> ifconfig usb0 192.168.0.200 netmask 255.255.255.0 up
>> iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
>> echo 1 > /proc/sys/net/ipv4/ip_forward
>> iptables -P FORWARD ACCEPT
>> route add -host 192.168.0.202 gw 192.168.0.200
>> route -n | grep -e "Destination" -e "usb0"
>> --

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking

2008-11-06 Thread Denis Johnson
On Thu, Nov 6, 2008 at 9:06 PM, Tony Berth <[EMAIL PROTECTED]> wrote:
> the wiki posted solution was tested by myself on a the currebt debian and
> did work! Are you using the same environment?

I believe so, I'm using Ubuntu 8.10 but have had this problem since 8.04.

> On Thu, Nov 6, 2008 at 10:46 AM, Denis Johnson <[EMAIL PROTECTED]>
> wrote:
>>
>> I have had this setting for months it does not work for me.
>>
>> Whenever I want to connect my FR, I must first plug it in into the usb
>> and then run the following script which someone once posted here or on
>> the #openmoko irc. Until I run ths script I cannot ping and hence ssh
>> into the FR. Unfortunately I don't know enough to integrate and
>> automate what the script does into my interfaces file. If someone can
>> shed some more light, it would be appreciated:
>>
>> --
>> #!/bin/sh
>> # Enables Hostside USB-Networking for neo
>> ifconfig usb0 down
>> ifconfig usb0 192.168.0.200 netmask 255.255.255.0 up
>> iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
>> echo 1 > /proc/sys/net/ipv4/ip_forward
>> iptables -P FORWARD ACCEPT
>> route add -host 192.168.0.202 gw 192.168.0.200
>> route -n | grep -e "Destination" -e "usb0"
>> --

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking

2008-11-06 Thread Tony Berth
the wiki posted solution was tested by myself on a the currebt debian and
did work! Are you using the same environment?

Cheers

Tony

On Thu, Nov 6, 2008 at 10:46 AM, Denis Johnson <[EMAIL PROTECTED]>wrote:

> I have had this setting for months it does not work for me.
>
> Whenever I want to connect my FR, I must first plug it in into the usb
> and then run the following script which someone once posted here or on
> the #openmoko irc. Until I run ths script I cannot ping and hence ssh
> into the FR. Unfortunately I don't know enough to integrate and
> automate what the script does into my interfaces file. If someone can
> shed some more light, it would be appreciated:
>
> ----------
> #!/bin/sh
> # Enables Hostside USB-Networking for neo
> ifconfig usb0 down
> ifconfig usb0 192.168.0.200 netmask 255.255.255.0 up
> iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
> echo 1 > /proc/sys/net/ipv4/ip_forward
> iptables -P FORWARD ACCEPT
> route add -host 192.168.0.202 gw 192.168.0.200
> route -n | grep -e "Destination" -e "usb0"
> --
>
> cheers Denis
>
> On Thu, Nov 6, 2008 at 7:13 AM, joezeewails <[EMAIL PROTECTED]> wrote:
> >
> > Stefan Monnier wrote:
> > >
> > > That's probably not right.  You probably want to try "allow-hotplug
> > > ubs0" instead.  "auto" means to do it at boot time and it may just fail
> > > if (for some reason) the usb0 interface is not yet created.
> > >
> > >
> > > Stefan
> > >
> > I could confirm this.
> > It doesn't work with "auto usb0" with "allow-hotplug usb0" it works just
> > fine.
> > Every time I plug the Freerunner in my debian etch it brings the
> > interface up.
> > I use the version from the wiki with a extra freerunner script.
> >
> > My entry in /etc/network/interfaces:
> >
> > #freerunner
> > allow-hotplug usb0
> > iface usb0 inet static
> > address 192.168.0.200
> > netmask 255.255.255.0
> > post-up /etc/network/freerunner start
> > pre-down /etc/network/freerunner stop
> >
> >
> >
> > Someone should correct the wiki, should I?
> >
> >
> > Cheers,
> > Joe
> >
> >
> > ___
> > Openmoko community mailing list
> > community@lists.openmoko.org
> > http://lists.openmoko.org/mailman/listinfo/community
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking

2008-11-06 Thread Tony Berth
done!

Thanks

On Thu, Nov 6, 2008 at 11:01 AM, Max Giesbert <[EMAIL PROTECTED]> wrote:

> @Tone Berth: The wiki is a community thing. You should update it yourself.
>
> Tony Berth schrieb:
> > Indeed that was the problem. 'allow-hotplug' instead of 'auto' is the
> > solution! PLEASE correct the WIKI asap!
> >
> > Thanks for your prompt support
> >
> > Cheers
> >
> > Tony
> >
> > On Wed, Nov 5, 2008 at 10:13 PM, joezeewails <[EMAIL PROTECTED]
> > > wrote:
> >
> > Stefan Monnier wrote:
> > >
> > > That's probably not right.  You probably want to try "allow-hotplug
> > > ubs0" instead.  "auto" means to do it at boot time and it may just
> > fail
> > > if (for some reason) the usb0 interface is not yet created.
> > >
> > >
> > > Stefan
> > >
> > I could confirm this.
> > It doesn't work with "auto usb0" with "allow-hotplug usb0" it works
> just
> > fine.
> > Every time I plug the Freerunner in my debian etch it brings the
> > interface up.
> > I use the version from the wiki with a extra freerunner script.
> >
> > My entry in /etc/network/interfaces:
> >
> > #freerunner
> > allow-hotplug usb0
> > iface usb0 inet static
> > address 192.168.0.200 
> > netmask 255.255.255.0 
> > post-up /etc/network/freerunner start
> > pre-down /etc/network/freerunner stop
> >
> >
> >
> > Someone should correct the wiki, should I?
> >
> >
> > Cheers,
> > Joe
> >
> >
> > ___
> > Openmoko community mailing list
> > community@lists.openmoko.org 
> > http://lists.openmoko.org/mailman/listinfo/community
> >
> >
> >
> > 
> >
> > ___
> > Openmoko community mailing list
> > community@lists.openmoko.org
> > http://lists.openmoko.org/mailman/listinfo/community
>
> --
> exactt technology
> Dipl. Inf. (FH) Max Giesbert
>
> Schießstättstr. 16  T: +49 17 75 07 53 44
> D-80339 München F: +49 89 1 22 21 97 02
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking

2008-11-06 Thread Max Giesbert
@Tone Berth: The wiki is a community thing. You should update it yourself.

Tony Berth schrieb:
> Indeed that was the problem. 'allow-hotplug' instead of 'auto' is the
> solution! PLEASE correct the WIKI asap!
> 
> Thanks for your prompt support
> 
> Cheers
> 
> Tony
> 
> On Wed, Nov 5, 2008 at 10:13 PM, joezeewails <[EMAIL PROTECTED]
> > wrote:
> 
> Stefan Monnier wrote:
> >
> > That's probably not right.  You probably want to try "allow-hotplug
> > ubs0" instead.  "auto" means to do it at boot time and it may just
> fail
> > if (for some reason) the usb0 interface is not yet created.
> >
> >
> > Stefan
> >
> I could confirm this.
> It doesn't work with "auto usb0" with "allow-hotplug usb0" it works just
> fine.
> Every time I plug the Freerunner in my debian etch it brings the
> interface up.
> I use the version from the wiki with a extra freerunner script.
> 
> My entry in /etc/network/interfaces:
> 
> #freerunner
> allow-hotplug usb0
> iface usb0 inet static
> address 192.168.0.200 
> netmask 255.255.255.0 
> post-up /etc/network/freerunner start
> pre-down /etc/network/freerunner stop
> 
> 
> 
> Someone should correct the wiki, should I?
> 
> 
> Cheers,
> Joe
> 
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org 
> http://lists.openmoko.org/mailman/listinfo/community
> 
> 
> 
> 
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community

-- 
exactt technology
Dipl. Inf. (FH) Max Giesbert

Schießstättstr. 16  T: +49 17 75 07 53 44
D-80339 München F: +49 89 1 22 21 97 02

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking

2008-11-06 Thread Denis Johnson
I have had this setting for months it does not work for me.

Whenever I want to connect my FR, I must first plug it in into the usb
and then run the following script which someone once posted here or on
the #openmoko irc. Until I run ths script I cannot ping and hence ssh
into the FR. Unfortunately I don't know enough to integrate and
automate what the script does into my interfaces file. If someone can
shed some more light, it would be appreciated:

--
#!/bin/sh
# Enables Hostside USB-Networking for neo
ifconfig usb0 down
ifconfig usb0 192.168.0.200 netmask 255.255.255.0 up
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -P FORWARD ACCEPT
route add -host 192.168.0.202 gw 192.168.0.200
route -n | grep -e "Destination" -e "usb0"
--

cheers Denis

On Thu, Nov 6, 2008 at 7:13 AM, joezeewails <[EMAIL PROTECTED]> wrote:
>
> Stefan Monnier wrote:
> >
> > That's probably not right.  You probably want to try "allow-hotplug
> > ubs0" instead.  "auto" means to do it at boot time and it may just fail
> > if (for some reason) the usb0 interface is not yet created.
> >
> >
> > Stefan
> >
> I could confirm this.
> It doesn't work with "auto usb0" with "allow-hotplug usb0" it works just
> fine.
> Every time I plug the Freerunner in my debian etch it brings the
> interface up.
> I use the version from the wiki with a extra freerunner script.
>
> My entry in /etc/network/interfaces:
>
> #freerunner
> allow-hotplug usb0
> iface usb0 inet static
> address 192.168.0.200
> netmask 255.255.255.0
> post-up /etc/network/freerunner start
> pre-down /etc/network/freerunner stop
>
>
>
> Someone should correct the wiki, should I?
>
>
> Cheers,
> Joe
>
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking

2008-11-06 Thread Pander
Any ideas regarding (semi)automatic configuration via
https://bugs.launchpad.net/ubuntu/+bug/289548 are also welcome.

On Thu, November 6, 2008 09:28, Tony Berth wrote:
> Indeed that was the problem. 'allow-hotplug' instead of 'auto' is the
> solution! PLEASE correct the WIKI asap!
>
> Thanks for your prompt support
>
> Cheers
>
> Tony
>
> On Wed, Nov 5, 2008 at 10:13 PM, joezeewails <[EMAIL PROTECTED]> wrote:
>
>> Stefan Monnier wrote:
>> >
>> > That's probably not right.  You probably want to try "allow-hotplug
>> > ubs0" instead.  "auto" means to do it at boot time and it may just
>> fail
>> > if (for some reason) the usb0 interface is not yet created.
>> >
>> >
>> > Stefan
>> >
>> I could confirm this.
>> It doesn't work with "auto usb0" with "allow-hotplug usb0" it works just
>> fine.
>> Every time I plug the Freerunner in my debian etch it brings the
>> interface up.
>> I use the version from the wiki with a extra freerunner script.
>>
>> My entry in /etc/network/interfaces:
>>
>> #freerunner
>> allow-hotplug usb0
>> iface usb0 inet static
>> address 192.168.0.200
>> netmask 255.255.255.0
>> post-up /etc/network/freerunner start
>> pre-down /etc/network/freerunner stop
>>
>>
>>
>> Someone should correct the wiki, should I?
>>
>>
>> Cheers,
>> Joe
>>
>>
>> ___
>> Openmoko community mailing list
>> community@lists.openmoko.org
>> http://lists.openmoko.org/mailman/listinfo/community
>>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking

2008-11-06 Thread Tony Berth
Indeed that was the problem. 'allow-hotplug' instead of 'auto' is the
solution! PLEASE correct the WIKI asap!

Thanks for your prompt support

Cheers

Tony

On Wed, Nov 5, 2008 at 10:13 PM, joezeewails <[EMAIL PROTECTED]> wrote:

> Stefan Monnier wrote:
> >
> > That's probably not right.  You probably want to try "allow-hotplug
> > ubs0" instead.  "auto" means to do it at boot time and it may just fail
> > if (for some reason) the usb0 interface is not yet created.
> >
> >
> > Stefan
> >
> I could confirm this.
> It doesn't work with "auto usb0" with "allow-hotplug usb0" it works just
> fine.
> Every time I plug the Freerunner in my debian etch it brings the
> interface up.
> I use the version from the wiki with a extra freerunner script.
>
> My entry in /etc/network/interfaces:
>
> #freerunner
> allow-hotplug usb0
> iface usb0 inet static
> address 192.168.0.200
> netmask 255.255.255.0
> post-up /etc/network/freerunner start
> pre-down /etc/network/freerunner stop
>
>
>
> Someone should correct the wiki, should I?
>
>
> Cheers,
> Joe
>
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking

2008-11-05 Thread Joel Newkirk
On Wed, 5 Nov 2008 18:42:33 -0800 (PST), abatrour <[EMAIL PROTECTED]>
wrote:
> 
> Also double check to make sure your LAN ip address isn't in the
> 192.168.0.*
> range.
> I've wasted too much time making that mistake.
> --
> View this message in context:
> http://n2.nabble.com/USB-Networking-tp1461467p1463175.html
> Sent from the Openmoko Community mailing list archive at Nabble.com.

Which is why my desktops (home and work) are set to use 192.168.0.201/30,
and the FreeRunner is set to 192.168.0.202/30. (on first SSH after flash I
change the FR settings for subnet, gateway and DNS)  Better would be to go
entirely 'elsewhere' within private IP address blocks, like 10.20.30.1/24
or something, but since the default IP on a FreeRunner after flashing is
always 192.168.0.202/24, I gave ground and kept it there, just narrowed the
subnet to /30 (two usable IPs, 192.168.0.201-202) so that only
102.168.0.200-203 are unworkable on my LAN.

j



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking

2008-11-05 Thread abatrour

Also double check to make sure your LAN ip address isn't in the 192.168.0.*
range.
I've wasted too much time making that mistake.
-- 
View this message in context: 
http://n2.nabble.com/USB-Networking-tp1461467p1463175.html
Sent from the Openmoko Community mailing list archive at Nabble.com.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking

2008-11-05 Thread joezeewails
Stefan Monnier wrote:
>
> That's probably not right.  You probably want to try "allow-hotplug
> ubs0" instead.  "auto" means to do it at boot time and it may just fail
> if (for some reason) the usb0 interface is not yet created.
>
>
> Stefan
>   
I could confirm this.
It doesn't work with "auto usb0" with "allow-hotplug usb0" it works just
fine.
Every time I plug the Freerunner in my debian etch it brings the
interface up.
I use the version from the wiki with a extra freerunner script.

My entry in /etc/network/interfaces:

#freerunner
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
post-up /etc/network/freerunner start
pre-down /etc/network/freerunner stop



Someone should correct the wiki, should I?


Cheers,
Joe


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking

2008-11-05 Thread Stefan Monnier
> "Tony" == Tony Berth <[EMAIL PROTECTED]>
> Edit /etc/network/interfaces and add:
> auto usb0

That's probably not right.  You probably want to try "allow-hotplug
ubs0" instead.  "auto" means to do it at boot time and it may just fail
if (for some reason) the usb0 interface is not yet created.


Stefan




___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


USB Networking

2008-11-05 Thread Tony Berth
Dear group,

I just installed (following the wiki) 2008.9 on my FR and tried to connect
from a debian box. Applied the following:

---
 Debian, Ubuntu and others

Edit /etc/network/interfaces and add:

auto usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
up echo 1 > /proc/sys/net/ipv4/ip_forward &
up iptables -P FORWARD ACCEPT &
down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
---

as mentioned in: http://wiki.openmoko.org/wiki/USB_Networking

After re-booting the debian box and connected my FR via USB, ifconfig -a shows:

---
usb0  Link encap:Ethernet  HWaddr 9A:99:92:BD:1A:34
  BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
---

and ping to 192.168.0.202 returns nothing!

Your help is much appreciated!

Thanks

Tony
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


USB networking problems with Ubuntu host (was RE: Default OM settings, no lan messed up)

2008-10-13 Thread Joel Newkirk
On Mon, 13 Oct 2008 19:03:54 +, Matthias Camenzind
<[EMAIL PROTECTED]> wrote:

> Using 192.168.1.x for local network with internet acess and 192.168.0.202
> is my freerunner. I find no reason for this but sometimes internet acess
> from FR won't work, then I run firestarter (a firewall out of the ubuntu
> repositories) and internet works again (even if i shutdown firestarter).
> On freerunner (192.168.1.1 is my router, 192.168.0.200 is my host
> computer):
> auto usb0
> iface usb0 inet static
>   address 192.168.0.202
>   netmask 255.255.255.0
>   network 192.168.0.200
>   gateway 192.168.0.200
>   up echo nameserver 192.168.1.1> /etc/resolv.conf
> 
> On Host (Ubuntu):
> auto usb0
> iface usb0 inet static
> address 192.168.0.200
> netmask 255.255.255.192
> post-up /etc/network/freerunner start
> pre-down /etc/network/freerunner stop
> 
> the /etc/network/freerunner script you can find in the wiki
> (USB_Networking in section "Ubuntu, Debian and others")

Is it possible that it's not working after reboot?  I'm wondering if
there's a DROP rule in the FORWARD chain of the hosts's firewall.  ("sudo
iptables -vnL FORWARD" shows Policy, rules, and packet/byte counts that
matched each - check it next time there's a problem BEFORE you run
firestarter, as well as "cat /proc/sys/net/ipv4/ip_forward" which should
return '1')

The simple fix in this scenario would probably be just to add these two
lines to the 'start' section of /etc/network/freerunner, based on what's in
the wiki:
iptables -I FORWARD -s 192.168.0.202 -j ACCEPT
iptables -I FORWARD -d 192.168.0.202 -j ACCEPT 

You can add the corresponding 'iptables -D' commands in the 'stop' section
to delete these rules if you like, but leaving them "laying around" is
pretty harmless.

I run Ubuntu on several workstations, three servers, and a bridge, with my
FR regularly connected to three of the above.  We'll make it work.

j



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking vs. iptables

2008-09-20 Thread Christian Weßel
Am Freitag, den 19.09.2008, 16:06 -0400 schrieb Joel Newkirk:

> You're most welcome.  The one problem with your reasoning regarding the
> default policy of ACCEPT is that the last rule in the RH-Firewall-1-INPUT
> chain is a 'drop all' rule...  Every RedHat/Fedora/CentOS box I've ever set
> up nearly the first thing I do is delete the default firewall and construct
> my own - I don't like the way they structure theirs.  IMHO best practice
> (and clearest logic) is to enable a DROP policy on INPUT and FORWARD
> chains, and add explicit ACCEPT rules for desired traffic. 
You are right. I have planned to do so, but after first installation of
FC I don't had any idea about iptables and SELinux. And currently I have
running my web server and don't want to block it. But I found a good
discription about a iptables based server FW. I will implement it in
future.

Now FR is more important :-).
-- 

mfg/br, christian

Flurstraße 14
29640 Schneverdingen
Germany

E-Mail: [EMAIL PROTECTED]
Telefon: +49 5193 97 14 95
Mobile:  +49 171 357 59 57
http://wesselch.homelinux.org


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


  1   2   >