beta 1 testing release

After a lot of work on the 3G support in the Fonera firmware, it’s finally time to share some of this work with you in the form of this beta release. As the name suggests, this release should be considered a testing release – it’ll probably not eat your data, but don’t be surprised if your internet connection breaks at some point. Having said that, we welcome you to try this release and provide feedback about any issues you encounter. You can always downgrade back to the latest stable firmware if there is a problem that is a showstopper for you.

3G improvements
As mentioned, improved 3G support is the biggest change in this release. By itself, this release does not magically add support for more 3G devices (though it’s likely that some devices that didn’t work before now do due to usb-modeswitch updates and kernel fixes), but it mostly cleans up the 3G support and makes it easier to debug issues with 3G devices.

For some more details about how the new 3G interface works and how to go about getting your device working, a separate blogpost is available. Please carefully read that post if you run into 3G problems.

Note that 3G devices no longer automatically connect when plugged in. By default, you’ll have to connect by clicking a button in the webinterface, though you can still configure the old behaviour of automatically connecting on device insertion by going to 3G -> Configure and then select “On device insertion: connect automatically”.

3G dongles and hubs
One change to point out specifically is that 3G devices in combination with USB hubs should not cause any problems anymore. Previously, using an USB hub would break connectivity for some 3G dongles. It turned out there were two unrelated bugs in the kernel USB driver that both caused problems with hubs under different circumstances. After extensive debugging, these issues have been found and fixed.

If you still find an issue with a hub (i.e., your dongle works without a hub, but doesn’t when connected through a hub) please report it.

Debug application
Another new addition in this release is the debug application. It’s not very powerful yet, but allows collecting some debugging information through the webinterface, as well as increasing the log buffer size. This should help us to collect debug information from users that are not comfortable with using the SSH interface.

To install this application, just head over to the “Applications” page on your dashboard – it should be listed there.

So, how do I upgrade?

Download the web upgrade tarball below, navigate to your Fonera’s dashboard through “Settings” and then “System” and upload the tarball there (under “Firmware update”). Note that you should not unpack the file you download (and make sure your browser doesn’t automatically unzip the file either, it should remain a .tgz file).

Note: On 2.0g, the firmware update might fail due to insufficient memory. If you upload the firmware through the webinterface, but that page keeps loading indefinitely (and you do not get the updating countdown), you’re probably seeing this issue as well. As a workaround, you can disable windows file sharing (“Settings” -> “Fileserver” -> “Windows Network Shares”) and/or the public Fonspot (“Settings” -> “FONSpot”) to free up some memory. This should allow the 2.0g to successfully unpack the firmware and start flashing it.

This firmware is available for the following hardware. Be sure to pick the version for your hardware. If you pick the wrong one, the firmware update will silently bail out and no upgrade will happen (no error will appear either).

Since this is a beta release, only developer’s versions are available. For the .img version (which can be installed through SSH), you can look in the directory on the download server.

If the upgrade somehow fails and you need to recover, the FAQ section has recovery instructions.

Have fun!

47 Responses to “ beta 1 testing release”

  1. JazzyJ Says:

    Cool an update,

    I don’t have any 3G dongles to test things out, but it’s nice to get an update even though FON has stopped selling this product…

    A while ago someone emailed me to say my plugins no longer install, at the time I didn’t have access to my router but I’ve plugged it in this weekend as my other one blew up and have fixed the issue, it was basically because the version of wget on the router doesn’t support SSL and Dropbox have redirected all downloads to https, So I’ve moved where some of the files are located. I don’t know if anyone still uses these but the updated links are

    MiniDLNA for 2.0g and 2.0n
    Mediatomb for 2.0n

    If anyone has any problems with them I can try and give limited support at Jazzy-J@outlook.com
    Good things! :)

  2. dllud Says:

    Will try. Thanks for keeping up the work on Fonera. It is becoming the longest and best supported hardware I ever bought.

  3. Michael Says:

    Thank you for this update! Waiting for the stable version :)

  4. gabox Says:

    Thanks a lot!! i am waiting for the stable version.

  5. Wil Says:

    Keep up the good work! We really appreciate it :-)

  6. Unplug Says:


    Would be nice to set the auto off and auto on the wifi signals.

    This function is in many current router



    Estaría bien poder programar el auto apagado y auto encendido de las señales wifi.

    Esta función esta en muchos routers actuales.

  7. Akuma Says:

    Yes!! Thanks a lot!!!

    I don’t need any of this update (except the log part) but I really appreciate the effort and support that you’re still giving to the devices.

    Congratulations for it and keep up the good work!!

  8. Christian Says:

    thanks for your work and the overall progress/ are there any further updates, for OpenVPN for instance?

  9. Fhil Says:

    Thanks for the update. Works well with Huawe1 E376 and rock-solid stability.

  10. ary Says:

    thanks, my old modem worked.

  11. Fhil Says:

    I think I have found a bug:
    with a dongle inserted…
    Dashboard > Wi-Fi Settings (bottom left) > Public Wi-Fi, I see “Disabled during 3G” even though I have enabled under “FonSpot” and enabled under “3G>Configure>Activate Hotspot”

    Also, IMO, I think it would be better to move the 3G Hotspot control from the 3G section to the Fonspot section to make it easier to find and configure!

    Keep up the good work!


  12. Matthijs Says:

    @Phil, weird. I just double-checked the code responsible for this, which didn’t show anything unusual. To easier track this problem, could you open up a ticket on our trac? Please include the output of the SSH command `uci export fon` if possible (but don’t forget to remove the (default) wifi password from the output.

    As for moving the hotspot control, that is an excellent suggestion (though it might be even better to _copy_ it there, so you can change the same value in both places). Could you perhaps also create a ticket on the trac about this?

  13. Fhil Says:

    Done, as requested.


  14. s3boun3t Says:

    thanks for support fonera 2.0n

  15. toto Says:


    I need to register a fonera 2200. I can’t find how to do.

    Can someone could help me ?


  16. Matthijs Says:

    @toto, try contacting fon support – they should be able to help you out with manual registration (though I think there were some changes in the backend that prevented registration of some of the older hardware, but support will be able to tell you that).

  17. John G Says:

    I’ve been running this beta for many months now (since very soon after its release) and it has been about as stable as the previous 2.3.7.x version – ie. great. Only crashed once in this time. This needed a full power-off reset to resolve, after being away for a weekend came back and turned other networking stuff back on and it had a whoopsie (or already had done). Couldn’t connect on ssh to examine the issue. But otherwise great, though I’m only using the Printer plugin and sometimes Samba access to a drive (or 2) – all via a Plexus powered usb hub.

    Only have issues with port forwarding (changing the port on the way through to avoid clashes, directed to an internal host on port 22 for ssh) at present, I just can’t connect externally though others ok – will ask about this separately.

  18. fhocorp Says:

    Thanks for your work ! My fonera 20n is now working very well !

    She’s connected in a datacenter at Lyon now.

    Best Regards

  19. iinokinji Says:

    Hi all,

    I’ve a fon2.0g (2202) with firmware, how to upgrade to latest?

    I’ve tried in all ways, web interface, SSH, but I think is possible only via redboot.


  20. Matthijs Says:

    @iinokinji, Firmware doesn’t sound like a firmware for the 2.0g. Are you sure this is isn’t a classic Fonera? If it has a USB port, it’s a 2.0g, if it doesn’t, it’s a classic one. See also this image

    If it really is a 2.0g with this older firmware, I’m not sure how to upgrade it. Through redboot or serial is probably the only way, but I’m not sure if this is still documented anywhere.

  21. iinokinji Says:

    Hi Matthijs,

    is a 2.0g, as I said model 2202.
    I’ve flashed via redboot with openwrt 14.07 in the end.
    I don’t know how and if is possible to flash with this firmware and in wich way.
    Via SSH and mtd says image too long.

    Thanks for the help, if you have any clue I’m here, otherwise I don’t wont go OT :)


  22. Matthijs Says:

    Might be an early beta version of the 2202 then I guess. I suspect that the mtd partition table is different as well the, which explains why flashing in this image won’t work.

    Perhaps you could drop by in #fonosfera on the Freenode IRC network, so we can talk more directly and see if we can solve this?

  23. iinokinji Says:


    yes, is possible that is an early version becouse I’ve bougth the 2.0g as soon as released. When I’ll find the time and I’ve the fonera near I’ll join the irc channel :)


  24. Fredrik Says:

    About once a week, the external harddrive (usb, ext3) seems to crash and ther router assigns a new name (from Disc-A1 to Disc-B1). The logs I can find (/var/log/) are all empty.
    I’m mounting the hard drive through samba on an Ubuntu 14.10-computer and the firmware on the router is beta. I’ve had this problem a long time (since as far as i remember, maybe even earlier), though it happens less frequently on the than the

  25. Matthijs Says:

    @Fredrik, try running the “logread” command through SSH to view the system log. I suspect that somehow the USB connection is being reset, but it will probably be hard to diagnose what’s happening exactly. If the hard drive is not self-powered, inserting a powered hub might help.

  26. Fredrik Says:

    @Matthijs, thanks for the tip! I’ll try that the next time the router decides to change the name of the disc.
    I do have a self-powered usb now. The weird thing is that it seems like there’s some kind of chronological order in the name change. I’ll try to monitor that as well.

  27. Fredrik Says:

    Ok, so now I found something! I deleted a folder, and then (I’m not exactly sure if it was immediate, but it was after this that I noticed it) all of a sudden, the usb connection crashed.
    Here’s a log (created from logread): https://dl.dropboxusercontent.com/u/3126822/fon_20150503.log

    It seems like there’s an I/O error, forcing it to change from usb1-0 to usb1-1/sda1 to sdb1.

  28. @lexus Says:

    @JazzyJ: I’ve installed mediatomb but its webpage is not loading(page cannot be found in firefox). Is something which I can do to fix it?

  29. Andrey Says:

    Hi, I have problem with the Fonera 2.0 n Firmware Version:
    Beta 1. You can not play online games , because the constant disconnections . With another router no such problems . How to fix it ?

  30. Nestore Says:

    Hey Guys, abandoned project?

  31. Aldo Says:

    hi, there are several security bugs in open ssl (0.9.8h) present in firmware version 2.0n, you can get an upgrade to the latest version?

  32. Sander Says:

    Like Aldo is saying…. can we please get regular security updates or the possibility to compile it ourselves with source code….

  33. Matthijs Says:

    This is something we will be looking into. However, simply updating openssl entirely might be tricky, since I think there have been quite some patches on top of it. Also, newer openssl versions might end up being too big for the available flash space (IIRC the current version is already tricky for the 2.0g). An alternative could be to backport some security fixes, though this might not be hard to get right.

    As for compiling the firmware yourself, see http://trac.fonosfera.org/fon-ng/wiki/build for instructions on how to do that.

  34. Nuno Says:

    I would like to configure my fonera2n running firmware beta 1 in order to map a remote server samba share into fonera’s (run as samba client).

    When mounting it always returns: “failed: No such device”

    “” is the correct ip of the device and it is accessible from my fonera2n (Pingable).
    “g” is the correct share name.
    user is not needed as it is openned to all users – anyway tried none and “guest”.

    any ideas ?

    = commands used:

    opkg update
    opkg install kmod-fs-cifs

    mkdir /tmp/mounts/mount_point
    mount -t cifs // /tmp/mounts/mount_point -o user=sambauser

  35. Peter Says:

    I’m very new to fonera. I’ve purchased my first ever fon router just over 2 weeks ago. It is a second hand 2.0n fon2303D off ebay.

    I have set up the router and it was working ok. beta1 was on it in wifi client bridge mode connected to my main router and one device (cellfi mobile phone signal booster) was connected to it via ethernet port. I had about 6 or 8 torrent files added and minidlna app was running but I wasn’t watching any movie. So I went to sleep. Next morning the router did not respond to ssh torrent web ui nothing. Went to check it and power light usb wifi and lan1 led was solid. Tried to reset it with the button at the back but nothing happened. So.. unplugged power and reconnect. No lights what so ever.. rtied again and again. Nothing. Tried with another 2 power adaptor (netgear 12v 1a and netgear 12v 1.5a). Nothing it is just dead no lights. Tried to hold reset and power it that way but no joy.
    Removed cover and noticed that the ralink chip gets really hot when plugged in. I can touch it but cannot hold my finger on it for long as it is burning hot.
    I guess.. the router is dead.
    Now the big question..
    I’m just about to replace it with a 2302A.
    Do I need to add any sort of cooling to this router if I want to use transmission and minidlna?

  36. Peter Says:

    No lights.. not even power light. Totally dark..

  37. Peter Says:

    Forgot to mention.. before the router died I’ve added about 600gb of movies to the hard drive directly via USB. Minidlna was configured to rescan on restart. So I guess when I plugged the hard drive in the router it started to work.. hard..
    Has anyone heard similar issue with this router? Or is it just me who was unlucky?

  38. @lexus Says:

    I have almost 1TB for more than 6 months.. and still working :)

  39. Matthijs Says:

    @Peter, the 2.0n routers are known to get warm when they’re busy, but they should be able to handle it normally (though they might wear down more quickly when warm, so perhaps you were unlucky and this was just the final bit of wear before breakage). Most cases of a Fonera that completely stops working are caused by a bad power supply, bad it seems you already ruled that out.

    As for cooling, make sure you don’t put the router in a confined and non-ventilated area. If you want to take extra measures, getting a small self-adhesive heat sink to stick onto the chip should allow the chip to run cooler.

  40. Peter Says:

    I have replaced my fonera. It’s up and running for a week now. All good.
    But there is one thing that I can’t make work.
    The public wifi and hartbeat to fon’s server.
    I’m emailing with fon support but what they tell me to do I’ve done them already and still doesn’t work.
    The setup is the following.
    Router’s mac id is registered on fon userzone but every time I check it is offline and firmware version shows 0.0 0.0
    I have tried a few different ways to connect to the internet just in case..
    Here are some setups.
    Fonera connects to main router as a wireless bridge. Static IP on fonera and this address has been allocated in main router for the device. Main router is Fonera is online. Torrent works and opkg update works. And connected to myPlace wifi everithing is OK I can browse any page and so on. Also web UI doesn’t show the router is offline message so I’m sure router is online. Public wifi ssid is broadcasted as fon_free_internet and I can connect to the ssid with another device. If want to open http://www.fon.com then it works. If I want to open anything else then I’m diverted to
    Where aa-aa-aa-aa-aa is the mac of the pc I’m using and xx-xx-xx-xx-xx is the fonera’s mac.
    Now the page is diverted to the addess above but doesn’t load in. Connection timeout message appears.
    I cannot open login.fon.com even if I connect diretly to my main router.
    Is the website down?
    After a few attempts of trying to use public wifi the fon_free_internet ssid broadcast stops. Disables itself?
    I have tried the same thing using ethernet cable between main router and fonera with dhcp and later static ip with the same results.
    I have also set in main router to port forward all ports to fonera. No change.
    Does this work for anyone?
    I have very little knowledge about using ssh. Can anyone tell me how to find out why is my router cannot register on fon’s server to be online?

  41. Aldo Says:

    Okay, I try to apply the patch!

    A question: which are the kernel modules to be included in the compilation for the proper functioning of all hw?

    Thank you

  42. Juicefin Says:

    Hi there. Been away for some years. Would be nice to use the 2.0n as the router of choice. With dongles it’s near impossible. Shops are having shelves full of 3g routers that work, so is there some reason why it should not do that on a Fon 2.0n?
    I’m still waiting for a proper way to handle 3G/4G dongles. At least to be able to modify dongle settings graphically from the web ui. I have not seen direct commitments for making this work. So will it? Meanwhile I’m getting middle-aged waiting for fonosfera. I would like the answer to be more of a yes/no, rather than mystical and über diplomatic.

    Has the fonosfera project been abandoned? Is it still running? Will we get frequent security updates? Will we get updates? Still like the idea, though.
    Take care

  43. Aldo Says:

    https://wiki.openwrt.org/toh/fon/fonera2.0n :)

  44. anonymous Says: beta 1 testing release was maybe the latest final release for Fonera 2.0n because, there is no development for a next firmware release in source code repositerie here :
    The latest commit was in october 2014.

  45. A fonera user Says:


    I think that the beta 1 testing release will be the latest release for Fonera 2.0n and 2.0g. Since this release in October 2014, matthijs had not updated the source code repository at http://trac.fonosfera.org/fon-ng/browser#trunk .
    As Aldo said, it’s time to switch to OpenWRT at least for security fix.
    Specially when you use beta 1 with developper release and then ssh enabled, you can see that you still use an old OpenSSL 0.9.8h (28 May 2008).

    @matthijs, thank you for your your work for the fonera 2.0n device firmware.

  46. JazzyJ Says:

    I’m no longer able to offer support for my plugins.. I updated my website a while ago to only support https and as the version of wget on the Fonera doesn’t like the redirect, my plugins will no longer download and install correctly.. I’ve reduced the security of my site a few times to allow people to reinstall them, but from now on – I’ll no longer be checking the Jazzy-J@outlook.com email address.. It’s a shame they couldn’t have kept a place for the community to share plugins, etc.. It was fun while it lasted :)

    See you all around :)

  47. tman Says:

    I remember the days when I used the fon router to download torrents. Webcam plugin worked nice also. Now it’s time to flash it with OpenWrt.

Leave a Reply

Please read the comment policy before posting a comment.