Talk:Neo FreeRunner Wifi

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(Remove random comments: new section)
m (Talk:GTA02 WLAN moved to Talk:Wireless Networking: Better name as per talk page. Consistent with "USB Networking" page.)

Revision as of 06:17, 1 August 2008

Passphrase issues:

I have noticed that with wireless sometimes it works better to use the password hash in the wpa_supplicant.conf instead of the ascii text. You can use the wpa_passphrase utility (I don't know if this is included in the GTA02 or not as I don't have one) to generate the hash for the passphrase.

techiem2@escape-pod ~ $ wpa_passphrase MYWIFI "my passphrase" 
network={
        ssid="MYWIFI"
        #psk="my passphrase"
        psk=a4c08e767704a66d3fb27d4bf072e2da279f76adc568722b9a6f97964b982620
}

Of course you would probably want to redirect output to the end of your wpa_supplicant.conf (wpa_passphrase MYWIFI "my passphrase">>/etc/wpa_supplicant/wpa_supplicant.conf).

--techiem2 19:12, 3 July 2008 (UTC)

Contents

disabling wifi on startup

What would be the cleanest way to not enable wifi on startup? -- Relet 20:31, 9 July 2008 (UTC)


wpa_supplicant tips

These tips are universally valid on 2007.2, ASU, qtopia, and most likely FSO.

Weird ioctl messages

Ignore them, they seemingly have no effect. eg:

"ioctl[SIOCSIWENCODEEXT]: Operation not supported"

wpa_supplicant times out

eg:

CTRL-EVENT-SCAN-RESULTS 
Trying to associate with 00:1d:5a:e8:00:00 (SSID='2WIRE915' freq=2432 MHz)
Authentication with 00:1d:5a:e8:00:00 timed out.

What you need to do is re-specify the essid manually:

iwconfig eth0 essid "2WIRE915"

And it will then immediately connect and authorise with WPA/TKIP.

default route issues

Due to the way the FR configures its usb0 interface, it creates a default route. You will need to delete this in order to use wifi (or gprs/bluetooth-pan, I imagine):

route del default gw 192.168.0.200

Hope this helps others. Ieatlint 22:53, 12 July 2008 (UTC)

wpa-psk modes

On my home wireless setup, I was unable to connect to my access point while it was setup for WPA-PSK/AES or WPA2-PSK/AES. Once I reconfigured it for WPA-PSK/TKIP my FR conected immediately. If it turns out to be relevant, my access point at home is a Linksys WRT54GL running Tomato 1.19.

New page title suggestion

Does anyone object to renaming this page? I propose dropping the GTA02 prefix. GTA02 is jargon. And there's no GTA01_WLAN page, as the prefix implies. And how about "Wireless networking" instead of the "WLAN" abbreviation? --Joseph M. Jarvis 15:31, 21 July 2008 (UTC)

Remove random comments

"Success stories" really don't belong on here. At best, they can go on the talk page. And please if the various commands on this talk page are relevant, they should be integrated into the main content, or discarded as old. And yes, please rename as appropriate.

Personal tools

Passphrase issues:

I have noticed that with wireless sometimes it works better to use the password hash in the wpa_supplicant.conf instead of the ascii text. You can use the wpa_passphrase utility (I don't know if this is included in the GTA02 or not as I don't have one) to generate the hash for the passphrase.

techiem2@escape-pod ~ $ wpa_passphrase MYWIFI "my passphrase" 
network={
        ssid="MYWIFI"
        #psk="my passphrase"
        psk=a4c08e767704a66d3fb27d4bf072e2da279f76adc568722b9a6f97964b982620
}

Of course you would probably want to redirect output to the end of your wpa_supplicant.conf (wpa_passphrase MYWIFI "my passphrase">>/etc/wpa_supplicant/wpa_supplicant.conf).

--techiem2 19:12, 3 July 2008 (UTC)

disabling wifi on startup

What would be the cleanest way to not enable wifi on startup? -- Relet 20:31, 9 July 2008 (UTC)


wpa_supplicant tips

These tips are universally valid on 2007.2, ASU, qtopia, and most likely FSO.

Weird ioctl messages

Ignore them, they seemingly have no effect. eg:

"ioctl[SIOCSIWENCODEEXT]: Operation not supported"

wpa_supplicant times out

eg:

CTRL-EVENT-SCAN-RESULTS 
Trying to associate with 00:1d:5a:e8:00:00 (SSID='2WIRE915' freq=2432 MHz)
Authentication with 00:1d:5a:e8:00:00 timed out.

What you need to do is re-specify the essid manually:

iwconfig eth0 essid "2WIRE915"

And it will then immediately connect and authorise with WPA/TKIP.

default route issues

Due to the way the FR configures its usb0 interface, it creates a default route. You will need to delete this in order to use wifi (or gprs/bluetooth-pan, I imagine):

route del default gw 192.168.0.200

Hope this helps others. Ieatlint 22:53, 12 July 2008 (UTC)

wpa-psk modes

On my home wireless setup, I was unable to connect to my access point while it was setup for WPA-PSK/AES or WPA2-PSK/AES. Once I reconfigured it for WPA-PSK/TKIP my FR conected immediately. If it turns out to be relevant, my access point at home is a Linksys WRT54GL running Tomato 1.19.

New page title suggestion

Does anyone object to renaming this page? I propose dropping the GTA02 prefix. GTA02 is jargon. And there's no GTA01_WLAN page, as the prefix implies. And how about "Wireless networking" instead of the "WLAN" abbreviation? --Joseph M. Jarvis 15:31, 21 July 2008 (UTC)

Remove random comments

"Success stories" really don't belong on here. At best, they can go on the talk page. And please if the various commands on this talk page are relevant, they should be integrated into the main content, or discarded as old. And yes, please rename as appropriate.