Wednesday, January 03, 2007

Fonera Autoupdate version 0.7.1 rev 2

My La Fonera just wants a new autoupdate. The extracted .fon is available here (thanks to Stefan).

It updates the webinterface, the validate.awk (checks correct input of the webinterface) and haserl (CGI wrapper for shell scripts).

We will investigate if they fixed webinterface.

Update: We tried a lot, but still with no luck. It looks like, the FON developers did a good job (this time). But we didn't give up yet...

Tuesday, January 02, 2007

Chillispot for OpenWrt for FON

FON patched chillispot a little bit. E.g. the 001-endian_fix.patch fixes the dhcp server of chillispot. This one and 100-fon.patch works fine with chillispot 1.1, but the others need further attention. I am not a C programmer. Maybe someone could help.

Anyway you can use the chillispot of the FON sources. It is version 1.0. It also installs chilli_radconfig. You can generate the long string - describe in the previous post. Thanks Anton for the comment. He says, that you can just use uamserver https://login.fon.com/cp/index.php in the chilli.conf. Anyway, I generated the string with chilli_radconfig. Maybe the string is needed for the first time registration of a La Fonera. This would support the assumption. But this is all speculations.

I tried to use it but with no success yet. The chilli.conf looks like that:

radiusserver1 radius01.fon.com
radiusserver2 radius02.fon.com
radiussecret garrafon
# MAC address of wlan device (wifi0)
radiusnasid XX:XX:XX:XX:XX:XX

# IP of the OpenFonera
dns1 192.168.1.223
dns2 192.168.1.223

# interface of the FON_AP
dhcpif ath0

uamsecret garrafon
uamanydns
uamallowed www.martinvarsavsky.net,www.google.com,www.flickr.com,static.flickr.com,video.google.com,216.239.51.0/24,66.249.81.0/24
uamallowed www.fon.com,www.paypal.com,www.paypalobjects.com,www.skype.com,66.249.93.0/24,72.14.207.0/24,72.14.209.0/24,84.96.67.0/24,213.91.9.0/24,80.118.99.0/24
uamallowed shop.fon.co.kr,secure.nuguya.com,inilite.inicis.com,fon-en.custhelp.com,maps.fon.com,c20.statcounter.com
uamserver https://login.fon.com/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/cp/index.php

When I start it with chilli -d -f -c /etc/chilli.conf and connecting a peer to the FON_AP the output is:
chillispot[675]: chilli.c: 3090: New DHCP request from MAC=XX-XX-XX-XX-XX-XX
New DHCP connection established
DHCP requested IP address
chillispot[675]: ippool.c: 436: No more IP addresses available
chillispot[675]: chilli.c: 3045: Failed allocate dynamic IP address
DHCP requested IP address
chillispot[675]: chilli.c: 3051: Client MAC=XX-XX-XX-XX-XX-XX assigned IP 192.168.182.2

When I try to open a webpage, chillispot reports several times:
cb_dhcp_data_ind. Packet received. DHCP authstate: 5
cb_tun_ind. Packet received: Forwarding to link layer

But it won't open a webpage. The redirection doesn't work. I think the problem is my iptables configuration. Anyone who knows how to set up iptables proper for chillispot please leave a comment.

Chillispot configuration for OpenWRT for FON

As you know in the last days I flashed a La Fonera with OpenWRT (Kamikaze). Currently I am working on a proper configuration for chillispot, to make it possible to add FON support (FON AP) to every device running OpenWRT.

Configuration is simple, but the problem is, that the /etc/chilli.conf of an original La Fonera contains a line like:

uamserver https://login.fon.com/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/cp/index.php

The XXX... is a string of numbers and letters. This string is created by /usr/sbin/chilli_radconfig. Stefan told me that chilli_radconfig fetches the configuration file somehow from FON. One of the parameters for it is the MAC address of the WIFI device.

I'll keep you up to date on any progress.

Friday, December 29, 2006

OpenFonera

After receiving my second La Fonera I was brave enough to flash OpenWRT Kamikaze. The used HOWTO described it very well and it worked without problems.

Now my first La Fonera serves a FON hotspot and my private (bridged) LAN. The second La Fonera is connected to my privat LAN via WPA over the first La Fonera. Now I can play with OpenWRT (Kamikaze) on my second La Fonera.

The described method uses the RedBoot shell. I don't know exactly how RedBoot works and wonder if it is possible to rescue the La Fonera in any case (wrong flashing, wrong configuration, ...). If anyone knows, please tell.

Tuesday, December 26, 2006

OpenWRT for the La Fonera?

It is nothing new, that the firmware for the La Fonera is based on OpenWRT. But in the last few days the developers are making progress to get OpenWRT running on the La Fonera. I found an interesting thread on the OpenWRT forum. The developers added support for Atheros based devices (La Fonera, Meraki) to the Kamikaze (the experimental branch of OpenWRT). So don't grab the sources, compile it and flash it, unless you know what you are doing.

My advice: Be patient and stay tuned!

Friday, December 22, 2006

Code injection without the FON servers

Stefan and me have written another script to open your La Fonera. It works with the firmware version 0.7.1 rev 1. The script and more information is available here.

UPDATE: There are now two scripts available. One for the new and one for the old firmware version.

Have yourself some happy holidays and Merry Christmas!

ipkg of the La Fonera broken?

Before christmas a new post. There are some issues with the ikpg system of the La Fonera. You can use repositories like this, this and this. I installed successfully e.g. the wol (Wake On Lan) package with ipkg install wol after adding one of the repositories above. But after executing ipkg remove wol it took too long, so I hit Ctrl-C. ipkg started to delete the /usr/bin/ directory. There is something wrong with the ipkg version of the La Fonera. USE IT WITH CAUTION! I will try to investigate this issue.

Hmm, it tried to install and remove a package again - without a flaw. Last night I did it, and the /usr/bin was partly deleted. The difference between the two cases: Last night I was a little bit impatient and hit Ctrl-C.

So my advice, keep it running and be patient. :)