Re: WIFI Connector Application

2008-09-29 Thread Sarton O'Brien
On Friday 26 September 2008 19:18:43 Matthias Apitz wrote:
> I've typed in the key in the FR again and again but it always said
> after some time 'ERROR Unable to join network'

Yeah, it looks like there is quite a bit of separation between all the 
different facilities.

The 'Settings->Wifi' GUI sort of works. If you select a network and enter a 
key (I've only tried WPA-PSK-TKIP), switch to a terminal, wait for the 
wireless indicator to appear and then issue 'udhcpc eth0', it all works.

The error has always appeared for me but the facility has still worked. Better 
yet, the latest testing update seems to allow the wireless indicator to 
disappear when you select wireless off.

This is with no wpa_supplicant.conf.

Manually launching wpa_supplicant is trivial for debugging, just bump up the 
verbosity and omit the '-B'.

I get the impression that a lot of the facilities haven't yet been configured 
to utilise any one particular network management scheme ... heard of 
resolvconf? ;)

Sarton

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


Re: WIFI Connector Application

2008-09-26 Thread Matthias Apitz
El día Thursday, September 25, 2008 a las 08:02:18PM +0100, Al Johnson escribió:

> > I think the work that wpa_supplicant daemon does is only to control the
> > association to the AP and bringing up the interface; then in FreeBSD
> > a devd (device daemon) lets you describe what to do else, for example
> > launch a script when IF_UP; in this script you may, based on the MAC of
> > the AP, do whatever is needed: ifconfig static IP or DHCP or 
> >
> > it is similiar to what I have described here for the cdce0 (USB) interface:
> >
> > http://wiki.openmoko.org/wiki/Usb_networking#FreeBSD
> >
> > a logic like that must exist in Debian too, I'm wrong?
> > and this is not much scripting work, or?
> 
> Exactly. The logic exists in debian. wpa_supplicant associates with the 
> access 
> point then some scripts apply the configuration you set 
> in /etc/network/interfaces that matches the AP it associated with. 
> Unfortunately in 2007.2 the bit that applies the settings is missing. For 
> someone who knows their way around the inner workings of the debian system it 
> would probably be easy to fix, but I don't. Since ASU was moving to use 
> connman instead of the debian method of network management I didn't see the 
> benefit in digging deeper at the time. 

Well, today morning I started investigating the Wifi of the FR gadget:

I configured the MAC addr of the eth0 of FR into my AP; 

I enabled the Wifi in the settings and FR saw my home SSID and asked for
the key; this AP at home is WEP protected and the 'password' (which I
normaly use in my laptop) is something like this wpa_supplicant entry:

 network={
 ssid="tarara"
 scan_ssid=1
 key_mgmt=NONE
 wep_tx_keyidx=0
 wep_key0=42FEEDDEAFBABEDEAFBEEFAA55
 }

I've typed in the key in the FR again and again but it always said
after some time 'ERROR Unable to join network'

then I SSH'ed into the FR and configured by hand:

# cat /etc/network/interfaces:
...
iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

# cat /etc/wpa_supplicant/wpa_supplicant.conf
network={
ssid="tarara"
scan_ssid=0
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=42FEEDDEAFBABEDEAFBEEFAA55
}

and restarted the eth0 interface with:

# ifdown eth0 && ifup eth0

this produced the following output:

sed: unrecognized option `--quiet'
BusyBox v1.9.1 (2008-09-04 08:23:57 CST) multi-call binary

Usage: sed [-efinr] pattern [files...]

WPA: Terminating
sed: unrecognized option `--quiet'
BusyBox v1.9.1 (2008-09-04 08:23:57 CST) multi-call binary

Usage: sed [-efinr] pattern [files...]

WPA: Configuring Interface
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
udhcpc (v1.9.1) started
run-parts: /etc/udhcpc.d/00avahi-autoipd exited with return code 1
Sending discover...
Sending select for 192.168.2.100...
Lease of 192.168.2.100 obtained, lease time 86400
run-parts: /etc/udhcpc.d/00avahi-autoipd exited with return code 1
adding dns 192.168.2.1

the network came up fin, including DNS:

# ping www.muc.de
PING www.muc.de (193.149.48.10): 56 data bytes
64 bytes from 193.149.48.10: seq=0 ttl=246 time=96.697 ms
64 bytes from 193.149.48.10: seq=1 ttl=246 time=114.740 ms
64 bytes from 193.149.48.10: seq=2 ttl=246 time=232.842 ms
64 bytes from 193.149.48.10: seq=3 ttl=246 time=154.134 ms
64 bytes from 193.149.48.10: seq=4 ttl=246 time=377.435 ms
64 bytes from 193.149.48.10: seq=5 ttl=246 time=88.150 ms

the routing looks a bit broken: note there are two default gateways:

# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags   MSS Window  irtt Iface
193.149.48.10   192.168.2.1 255.255.255.255 UGH   0 0  0 eth0
192.168.2.0 0.0.0.0 255.255.255.0   U 0 0  0 eth0
192.168.0.0 0.0.0.0 255.255.255.0   U 0 0  0 usb0
0.0.0.0 192.168.2.1 0.0.0.0 UG0 0  0 eth0
0.0.0.0 192.168.0.200   0.0.0.0 UG0 0  0 usb0

it would be nice to create some icon in the Om2008.9 desktop to launch
this "ifdown eth0 && ifup eth0", but I already learned that this is
another complex storry and at the moment I can't compile the eet library
for modifying the desktop at all; so I have to live with the command on
the sheel (which is not a big thing);

in my office the AP runs WPA-PSK and it seems that it is not associating
at all; the entry in /etc/wpa_supplicant/wpa_supplicant.conf reads:

network={
ssid="santaclara"
key_mgmt=WPA-PSK
psk="XXX"
}

again, it is the same as I use in my laptop; and I have no idea why it
does not associate; can I launch somehow the wpa_supplicant in FR in
debug mode? or I will enable the debugging in the AP and have a look

Re: WIFI Connector Application

2008-09-26 Thread Arigead
Thanks to everybody who relied to this thread you have given my much 
food for thought.

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


Re: WIFI Connector Application

2008-09-25 Thread William Kenworthy
On Thu, 2008-09-25 at 15:16 +0100, Arigead wrote:
> Hello all,
> I'm looking for an application which if it exists great and if it 
> don't exist I'll maybe try and implement it in C, if what I'm thinking 
> is even possible. I've not done too much investigating into Wifi as I 
> believe that it has its issues on the FR.
> 
At the time I installed dd-wrt on my AP, there was a script that did
exactly this.  Looked for local known/unknown networks and picked the
best one to connect to - target was an environment (appartment block)
that had a number of unsecured AP's that continually changed.  The AP
just auto-connected to the one it thought best.

Moral issues aside, that looks like the way to do it.  A quick look at
the dd-wrt site doesnt show it now, but some searching should show it.

Also noticed they have a new HAL that can do Atheros WiSOC - not sure if
that includes the AR-6000.

BillK




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


Re: WIFI Connector Application

2008-09-25 Thread Al Johnson
On Thursday 25 September 2008, Matthias Apitz wrote:
> El día Thursday, September 25, 2008 a las 03:50:21PM +0100, Al Johnson 
escribió:
> > On Thursday 25 September 2008, Matthias Apitz wrote:
> > > El día Thursday, September 25, 2008 a las 03:16:43PM +0100, Arigead
> >
> > escribió:
> > > > Hello all,
> > > > I'm looking for an application which if it exists great and if it
> > > > don't exist I'll maybe try and implement it in C, if what I'm
> > > > thinking is even possible. I've not done too much investigating into
> > > > Wifi as I believe that it has its issues on the FR.
> > >
> > >   ...
> > >
> > > Isn't wpa_supplicant doing exactly this (it does for me on my normal
> > > laptop) having /etc/wpa_supplicant.conf as the database for all your
> > > known Wifi networks?
> >
> > It would do if all the debian network scripts are in place. Last time I
> > tried (some time ago now) wpa_supplican would connect, but the scripts
> > that are supposed to run on connection to sort out IP, DNS etc. were
> > missing.
>
> I think the work that wpa_supplicant daemon does is only to control the
> association to the AP and bringing up the interface; then in FreeBSD
> a devd (device daemon) lets you describe what to do else, for example
> launch a script when IF_UP; in this script you may, based on the MAC of
> the AP, do whatever is needed: ifconfig static IP or DHCP or 
>
> it is similiar to what I have described here for the cdce0 (USB) interface:
>
> http://wiki.openmoko.org/wiki/Usb_networking#FreeBSD
>
> a logic like that must exist in Debian too, I'm wrong?
> and this is not much scripting work, or?

Exactly. The logic exists in debian. wpa_supplicant associates with the access 
point then some scripts apply the configuration you set 
in /etc/network/interfaces that matches the AP it associated with. 
Unfortunately in 2007.2 the bit that applies the settings is missing. For 
someone who knows their way around the inner workings of the debian system it 
would probably be easy to fix, but I don't. Since ASU was moving to use 
connman instead of the debian method of network management I didn't see the 
benefit in digging deeper at the time. 


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


Re: WIFI Connector Application

2008-09-25 Thread Minh Ha Duong
>launch a script when IF_UP; in this script you may, based on the MAC of
>the AP, do whatever is needed: ifconfig static IP or DHCP or 
>a logic like that must exist in Debian too, I'm wrong?
>and this is not much scripting work, or?

Yes, in Debian here is how I do it:

http://minh69.blogspot.com/2008/04/setting-up-debian-etch-to-automatically.html

Minh

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


Re: WIFI Connector Application

2008-09-25 Thread Matthias Apitz
El día Thursday, September 25, 2008 a las 03:50:21PM +0100, Al Johnson escribió:

> On Thursday 25 September 2008, Matthias Apitz wrote:
> > El día Thursday, September 25, 2008 a las 03:16:43PM +0100, Arigead 
> escribió:
> > > Hello all,
> > > I'm looking for an application which if it exists great and if it
> > > don't exist I'll maybe try and implement it in C, if what I'm thinking
> > > is even possible. I've not done too much investigating into Wifi as I
> > > believe that it has its issues on the FR.
> >
> > ...
> >
> > Isn't wpa_supplicant doing exactly this (it does for me on my normal
> > laptop) having /etc/wpa_supplicant.conf as the database for all your
> > known Wifi networks?
> 
> It would do if all the debian network scripts are in place. Last time I tried 
> (some time ago now) wpa_supplican would connect, but the scripts that are 
> supposed to run on connection to sort out IP, DNS etc. were missing.

I think the work that wpa_supplicant daemon does is only to control the
association to the AP and bringing up the interface; then in FreeBSD
a devd (device daemon) lets you describe what to do else, for example
launch a script when IF_UP; in this script you may, based on the MAC of
the AP, do whatever is needed: ifconfig static IP or DHCP or 

it is similiar to what I have described here for the cdce0 (USB) interface:

http://wiki.openmoko.org/wiki/Usb_networking#FreeBSD

a logic like that must exist in Debian too, I'm wrong?
and this is not much scripting work, or?

matthias
-- 
Matthias Apitz
Manager Technical Support - OCLC GmbH
Gruenwalder Weg 28g - 82041 Oberhaching - Germany
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <[EMAIL PROTECTED]> - w http://www.oclc.org/ http://www.UnixArea.de/
b http://gurucubano.blogspot.com/
A computer is like an air conditioner, it stops working when you open Windows
Una computadora es como aire acondicionado, deja de funcionar si abres Windows

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


Re: WIFI Connector Application

2008-09-25 Thread Al Johnson
On Thursday 25 September 2008, Matthias Apitz wrote:
> El día Thursday, September 25, 2008 a las 03:16:43PM +0100, Arigead 
escribió:
> > Hello all,
> > I'm looking for an application which if it exists great and if it
> > don't exist I'll maybe try and implement it in C, if what I'm thinking
> > is even possible. I've not done too much investigating into Wifi as I
> > believe that it has its issues on the FR.
>
>   ...
>
> Isn't wpa_supplicant doing exactly this (it does for me on my normal
> laptop) having /etc/wpa_supplicant.conf as the database for all your
> known Wifi networks?

It would do if all the debian network scripts are in place. Last time I tried 
(some time ago now) wpa_supplican would connect, but the scripts that are 
supposed to run on connection to sort out IP, DNS etc. were missing.

2008.8/9 appears to be using connman which is supposed to do a similar job to 
NetworkManager. 


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


Re: WIFI Connector Application

2008-09-25 Thread Matthias Apitz
El día Thursday, September 25, 2008 a las 03:16:43PM +0100, Arigead escribió:

> Hello all,
> I'm looking for an application which if it exists great and if it 
> don't exist I'll maybe try and implement it in C, if what I'm thinking 
> is even possible. I've not done too much investigating into Wifi as I 
> believe that it has its issues on the FR.
...

Isn't wpa_supplicant doing exactly this (it does for me on my normal
laptop) having /etc/wpa_supplicant.conf as the database for all your
known Wifi networks?

matthias

-- 
Matthias Apitz
Manager Technical Support - OCLC GmbH
Gruenwalder Weg 28g - 82041 Oberhaching - Germany
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <[EMAIL PROTECTED]> - w http://www.oclc.org/ http://www.UnixArea.de/
b http://gurucubano.blogspot.com/
A computer is like an air conditioner, it stops working when you open Windows
Una computadora es como aire acondicionado, deja de funcionar si abres Windows

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


Re: WIFI Connector Application

2008-09-25 Thread Christ van Willegen
Hello,

On Thu, Sep 25, 2008 at 4:16 PM, Arigead <[EMAIL PROTECTED]> wrote:
> I've not tagged this email [2008.09] or anything. I'm using 2008.09 but
> I'll use this on any distro if it exists and if it has to be written I
> don't want to write it for a specific Distro.

I think that at the moment the Mofi application comes closest to what
you describe here...

Christ van Willegen
-- 
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0

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


WIFI Connector Application

2008-09-25 Thread Arigead
Hello all,
I'm looking for an application which if it exists great and if it 
don't exist I'll maybe try and implement it in C, if what I'm thinking 
is even possible. I've not done too much investigating into Wifi as I 
believe that it has its issues on the FR.

I've not tagged this email [2008.09] or anything. I'm using 2008.09 but 
I'll use this on any distro if it exists and if it has to be written I 
don't want to write it for a specific Distro.

The FreeRunner as you well know is a very mobile device. Given this 
mobility the wifi is potentially connecting to different networks all 
over the place. I'm looking for an application which can scan for wifi 
networks and compares the available SSIDs to a list of know SSIDs which 
is stored in? (database/file/whatever) The list of know SSID's should 
also contain the security details of the Network.

Now if the app is started and it finds a know Network it simply connects 
to that network using the stored security settings. If there is no know 
network available but there is an open network the App prompts the user 
to see if they want to connect to an open network. Perhaps in the coffee 
shop.

I don't know if the phone should periodically check for access points or 
whether it should only connect when prompted. Maybe along the top of the 
home screen there could be icons for a connectable wifi hotspot. If the 
user sees that they are connectible then they could start their browser 
and let it all work.

as I say I've not even started looking at FR Wifi as yet as I though 
there were problems. If the app I'm describing already exists sorry but 
please direct me. I want WIFI connection not to require the command 
line. Most people who buy phones will never use a command line ;-)

I use Ubuntu on my laptop and every time I go home to the parents place 
I have to tell Ubuntu to connect to their Wifi. I must have told it a 
million times ;-) You'd think it would know by now. Actually the App I'm 
describing could be used on my laptop as well. Two birds...



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