OpenWrt Forum Archive

Topic: What about openwrt for La Fonera?

The content of this topic has been archived on 17 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

I got the router today and found out it as 8mb flash and 16mb ram. I can see a potential for these routers.  It is really small but uses an atheros chipset. I can see it doing WDS or even client mode + AP.

The problem with the La Fonera routers is that they are subsidized by Fon.  You are paying $5 (or 5 euro...) for it on the condition that you participate in the Fon network.  With the WRT54G*'s that they used to provide subsidized if you didn't remain part of the Fon network for the year that you agreed to, they would bill you for the full cost of the router.  I do not have a La Fonera device myself, but I know that the Fon Basic firmware for the WRT54G*'s was a modified version of OpenWRT.  I would assume that the firmware for La Fonera is based on the OpenWRT trunk or buildroot-ng since they support Atheros SoC platforms.  This would mean that the La Fonera device is basically supported right now, minus a few specific tweaks, which could be obtained from Fon itself depending on how easy it is to get them to send the changes they have made upstream, or at least allow access to their source so others can send the changes upstream.

Note: La Fonera costs $50 for any Fon member who has already purchased a subsidized router.  Too bad, I was one of the early adopters who paid $25 for a WRT54GL.

We're actually paying more like $15.00 with shipping and tax.  Don't you think that we should be able to do what we want with the hardware after we've paid hack the subsidy in a year?

I took got a WRT54GL for a little over $30 with shipping and tax, but Fon is offering current users the chance to buy the Fonera for the $5 + tax + shipping.  Mine arrived today and I'll be able to do whatever I want with the original GL unit. 

I think it's short sighted of Fon to try to prevent these modifications.  What if we get the next generation of Fon routers?  Do we just throw the Fonera away or put it to good use somewhere by reflashing it.

What kind of firmware can i choose to reflash "la fonera" with a standard openWRT distribution?

The firmware has to be signed by the fon key  for update ( Which could be a good idea)  :

http://www.dd-wrt.com/phpBB2/viewtopic. … ght=fonera


, I guess the bootloader checks the signature , So I guess we need to replace the bootloader , and do it via TFTP ...

(Last edited by freechelmi on 10 Oct 2006, 09:40)

Now that we got ssh working, are there any scripts to change it to client mode, repeater, wds?

No interest in getting this little box into client mode or WDS mode?

FON Sourcecode has been released:

As promised here is the source code for La Fonera: http://download.fon.com/firmware/fonera … ra.tar.bz2
Please forward suggestions for improvements to iurgi@fon.com

Also, if you like to do Openwrt projects please let us know, we are offering grants for interesting ones!

read more at http://blog.fon.com/en/

(Last edited by dadaniel on 1 Nov 2006, 18:10)

Ok, I am the dumbest person in the world smile

I've messed up the init scripts on my fonera, and it keeps rebooting every time on network initialization. I can not do anything even usin serial console because it reboots before I get a shell.

Anyone knows if I can access it in failsafe mode ?

Thank you very much.

Any development in this area to put on openwrt with full functionality?

Let me quote the readme.txt smile ...

Status of this package: Experimental

Known Problems: Adhoc+Mastermode does not work perfect, some wifi cards
do not want to cooperate (at least my atheros/madwifi does not see the
Hotspot with kubunu nor do it see the WPA "MyPlace"). A centrino IPW2100
and a Siemens-Atheros-USB (ndiswrapper) work fine. Ad-hoc is fine too now.
You also need to put FF_IP=x.x.x.x in /etc/init.d/S80freifunk currently.

Note: Automatic upgrading from fon is stopped with this pack. You will
notice after a while, that /tmp/.thinclient.sh exists. These following
updates are verified by me and are ok to install. You can use the fonlist
command which is included in ff-fonera-pack to check yourself what's in
an *.fon file (simple tgz with the fon signature). You cal download
these manually and install via Web UI if you like:

Registration bugfix:
  http://download.fon.com/firmware/update … pgrade.fon

Update of the the madwifi driver and other stuff:
  http://download.fon.com/firmware/update … pgrade.fon

PPPoE Update, will not install automatically:
  http://downloads.fon.com/firmware/updat … 3_rev4.fon

Another note: The madwifi update does _not_ fix the current parallel AdHoc+
Master mode probs. You also need a standard Freifunk router with fixed BSSID
in range in order to have AdHoc up and running.

Howto install ff-fonera-pack:

1) You need a linux shell prompt. You can add a serial console. Assemble
   a standard MAX232 serial voltage level adapter (google for "wrt54g serial"
   for soldering tips).

2) The onboard 10-pin header offers access to the command line. Pin1=3,3 Volt,
   Pin2=Ground, Pin6=TX(to PC), Pin8=RX(from PC). Speed 9600,n,8,1.

3) You may remove any configuration + fon updates by issueing "rm -r /jffs/*"
   (+restart by pulling the power plug). This will remove all changes to the
   original firmware (mini_fo overlay files are removed by this).

4) Enter "cd /etc/init.d;mv dropbear S51dropbear;./S51dropbear start" to
   enable the ssh service on the box. Now it is possible to work more
   convenient with "ssh 169.254.255.1" over ethernet connection.

5) Verify internet connectivity by "ping google.com" or so.

6) ipkg install http://olsrexperiment.de/sven-ola/foner … 1_mips.ipk

7) Change ip/wifi config in /etc/init.d/S20madwifi-freifunk using standard "vi"

The ff-fonera-pack will do these changes on the box:

- It installs the shell script variant of the ipkg command and alters the
  /bin/rmdir command. This is a bugfix for the buggy rmdir implementation of
  mini_fo (removes a directory tree while deinstalling ipks even if directory
  is non-empty. Fatal with "rmdir /lib".

- Installs olsrd daemon as well as start scripts to add a new ath2 virtual
  ad-hoc wifi interface. Opens the firewall to let any packets from-mesh
  ip address range through.

- Disables the auto-fon-update mechanism. You need to install upgrades
  manually. Verify "cat /tmp/.thinclient.sh" on a regulary basis to check
  if new FON updates are in the queue. Update is disabled, because it is
  unclear if future updates will be incompat with ff-fonera-pack and I
  personally do not like other people fiddeling with my hardware too.
  You can remove the "#" in the last line of /bin/thinclient if you
  want the autoupdate back.

- FON function (private AP with WPA and public unencrypted AP) should work
  as usual. Configure that stuff with the web UI. It may be necessary
  to configure a fixed channel (madwifi does support several virtual Wifi
  interfaces, but they all share the same channel setting).

Attention: This will open your internet connection to all users in the
mesh. You have no choice currently besides your own hacks of course. I may
add policy routing statements in future versions of this pack in order to
offer this choice (wether you will only allow OLSR mesh members to route
through your box or if you also want to offer your inet to mesh members
for free). I will not add any FON registration for mesh members - the FON
stuff is bound to the hotspot function and the chillispot software is not
compat with routing too.

!!! No warranties, no complaints. This is experimental stuff. If you want to
remove the ff-fonera-pack, issue "rm -r /jffs/*" and reboot by pulling the
plug. This restores the standard FON router function. !!!

// Sven-Ola

I also tried adhoc + AP in VAP of madwifi, but same as the readme.txt.
I am anxiously looking forward to coming to maturity of madwifi.

Thanks, max-horvath.
and always thanks, Sven-Ola.

>This is a bugfix for the buggy rmdir implementation of
>mini_fo (removes a directory tree while deinstalling ipks even if directory
>is non-empty. Fatal with "rmdir /lib".

I saw the code in the ipkg but this is not a definitive solution.
How was it solved on Openwrt?

The discussion might have continued from here.