Automated firmware builds from subversion available

Fon has an internal firmware autobuilder, that builds a new firmware for every revision that is committed to the Fonosfera Subversion repository. During the past time, I’ve been spending some of my time improving this autobuilder, allowing it to publish each of the firmware images it builds to the download server.

You can download these images here:

This means that, if you want to keep on top of the bleeding edge firmware, are troubled by a bug that just got fixed in the SVN repository, or just want to help us out by testing our latest bugfixes and features, you can download one of these firmware versions and flash it into your Fonera.

Some things to take into account:

  • This is only for the fon-ng/fonosfera firmware, which is for the 2.0g and 2.0n devices.
  • These are bleeding edge versions, so there’s always a chance of a firmware containing new bugs or not working at all. It is very unlikely that a bad firmware can really brick your Fonera, though (The firmware recovery methods will almost certainly still work).
  • Sometimes, a revision might be skipped if multiple commits happen shortly after each other or if building failed for that revision.
  • A firmware build usually takes two hours to complete (but this can be more if multiple builds run in parallel) and starts within a minute after a commit.
  • These firmware images are raw images that can be flashed through SSH. They cannot be flashed through the web interface (like .tar.gz images).

If you like this new service, have a question or problem, feel free to leave a comment!

Update: I just realized that using a Transmission version from the autobuilder is actually possible and easy: Just install the regular version of the plugin, download the fmg file (e.g. plugins/torrent_2.52-1_fonera2n.fmg) from auto-builds and then replace the .fmg file on your USB stick (e.g. FoneraApps/torrent. with it. You might need to delete the .var file (e.g., FoneraApps/torrent. file as well to reset the Transmission settings).

35 Responses to “Automated firmware builds from subversion available”

  1. tman Says:

    But there is a changelog available somewhere ? Just to know if it worth to try it, e.g. solves a bug, etc.

  2. tman Says:

    …and another question:
    fon-ng-r2048/ 24-abr-2012 17:32 contains plugin transmission version torrent_2.13-1_fonera2n.fmg
    But what means 2.12-1 ?? I have on my Fonera ransmission 2.33 build 12565 and it’s an old version…

  3. Matthijs Says:

    The svn log provides a full changelog and can be accessed through trac. There’s also a link to the most recent commit included from the download page for each image.

    A slightly less detailed, but easier to read changelog is available as a separate Changelog.txt file. It is only updated every now and then (I guess I should update it again this week).

    I hope this answers your question!

  4. tman Says:

    The first link is good since it shows all changes from Thanks!

  5. steven Says:


  6. Matthijs Says:

    About the transmission version number: I simply forgot to update it in the plugin-torrent metapackage. I just fixed that in svn, that build should show up soon.

    I also updated Changelog.txt just now, which might give a slightly easier-to-read changelog than the SVN log.

  7. shareAir Says:

    Thank you for the automated firmware builds. I look forward to the updated version of the transmission client.
    Have you got any plans, when Beta 3 or the final firmware will be available?

  8. decodecoding Says:

    This is a realy cool thing to see! Thanks

  9. alexb Says:

    Hello fon team,

    I think that it’s a good idea to have a buid automatisation.
    Is it possible to provide the tgz file, which can be used to upgrade the firmware through the web interface ?
    Thanks in advance.

    Alex B.

  10. Matthijs Says:

    @ShareAir, I’ll see about including an updated Transmission version in the beta3 release.

    @alexb, I guess we can do that. These tgz images wouldn’t be signed, so they would only be installable on DEV firmwares, so there’s little risk of non-suspecting users accidentally instalilng an unstable version. Note that this only works when upgrading _from_ beta1 or higher, earlier versions required a signed .tgz file, even in DEV mode. Can you perhaps create a ticket on the trac for this?

  11. JazzyJ Says:

    This is very helpful, it’s a shame Fon has locked the forum and the wiki, I will never buy a fon product again because of this ridiculous step, but, I appreciate everything you’ve done Matthijs… You are a shining star in a dying universe! :)

  12. tman Says:

    I tried to post on but is locked. There was an announcement that it will be moved to, but there is no forum at all. See this page: it’s nothing like “forum” there.
    What’s happening ?

  13. Anonymous Says:

    When will there be at last a”renew ip adress” (without resseting/restarting the whole router) in the fonera menu or at least a html shortcut for resetting the ip adress?

  14. tman Says:

    Probably never if there is no ticket for that. Did you opened one? (

  15. Anonymous Says:


    not yet, but I think Matthijs reads this suggestion and will force the implemention of this neadful feature and also maybe open a ticket himself – if necessary [at least I hope so ;)]

  16. Marco J Says:

    With the new wiki, where can I see the “firmware recovery methods” ? I can’t find it anywhere

  17. tman Says:

    @Marco: Wiki is deleted. But you could open the “FEEDBACK” page in the left side and ask the support where is it copied. I’m curios what they will answer.

  18. Marco J Says:

    @tman done
    I currently have two requests open there (i bricked my fonera 2.0n while reinstalling beta 2 DEV), so as soon as I get any feedback I’ll keep you posted.

  19. Matthijs Says:

    About the closing of the forums and wiki: The idea is to make sure that the information found online can be guaranteed to be correct by Fon, to better help customers to use their products. If you have further questions, this is not the place for them, nor am I the one to answer them, so please contact support through with further questions related to the move.

    @Marco, info about firmware recovery is on the list of stuff to add to the zendesk, probably under a new “Under the hood” or “Advanced” section. In the meanwhile, I’ll send you a private mail with some info to get you started again.

    @Anonymous, your suggestion looks useful, could you create a ticket on the trac for it?

  20. JazzyJ Says:

    I understand this is not the place to post comments on the closure of the forum and wiki…
    Maybe ,if they had made a ‘blog’ explaining their reasoning, we would have somewhere.
    I have left feedback on ‘zendesk’ suggesting their placement of the feedback button is not, well, Zen!
    I worry about the sanity of the person in charge. :)

  21. alan Says:

    last build r2060 has a update for transmission v2.52, how can i install this update, i have installed last build r2060, but when i installed transmission it installed v2.33

  22. Matthijs Says:

    @alan, it’s currently not so easy to install a custom transmission file (since it is downloaded from automatically). However, I’ve just uploaded the new version for all beta users to install. See my recent blogpost about how this works.

  23. alan Says:

    @Matthijs, thank you! :)

  24. JazzyJ Says:

    I just ordered another fonera 2.0n because of the free shipping this week :)
    which I found out about on

  25. Christian Says:

    I think it is since Beta 2 that I get Wifi or Ethernet only Internet access. As soon as I plug in one laptop, the other being connected wirelessly experiences a drop in ping time from 20ms or so to over 7 seconds and a huge increase in package loss, too. This means no more name resolution which means “Internet’s dead” basically. As soon as I pull the Ethernet plug out, the ping time creeps back to normal.

    I like these new daily builds so I can test if the bug has already been fixed but sadly the answer is “no” as of r2102.

  26. Matthijs Says:

    I just realized that installing an update Transmission from the auto-builds is actually possible, I’ve added instructions at the bottom of the post.

    The firmware recovery instructions have also been made available again on Zendesk, so I updated the link in the post as well.

  27. Anonymous Says:

    @Matthijs, May 16th, 2012 at 9:54 am

    Okay, I finally opened a ticket for this useful longed for “renew ip adress” feature, Ticket #1215

  28. Filipe Says:

    Is the telnetd working?

    When I try to connect to my fonera I got automatically disconnected.

  29. Matthijs Says:

    @Filipe, the 2.0 Foneras do not run telnet, they run an SSH daemon instead. You should use an SSH client to connect (like PuTTY on Windows). this wiki page provides some extra instructions.

  30. Filipe Says:


    By the way, any particular reason to do not run telnet?

  31. Matthijs Says:

    Telnet is not quite secure, given that passwords are sent over the wire in plaintext, while SSH does not suffer from this problem.

  32. Filipe Says:


    Just for curiosity.

    When I run the telnetd and I try to connect to fonera I get automatically disconnected. What makes this happen?


  33. Matthijs Says:

    Ah, you started telnetd manually, didn’t realize that. I just tried that as well, and got the message “Login failed. Connection closed by foreign host.”.

    I had a quick look into this, and found out that when you connect to telnetd, it starts the /bin/login program, which is just a script (presumably) created by/for OpenWRT. If I read it correctly, it only allows telnet access when no root password has been set, instructing the user to set a root password so SSH access can be enabled.

    If you really need telnet access, you could simply edit the /bin/login script and remove all the passwd related stuff, leaving just the first line (hashbang) and the last line (where it invokes the actual shell). Note that this will _not_ ask for a password on telnet connections, I’m not sure if the Fonera actually has password checking program on board (other than the one built into the SSH daemon).

    I hope this clarifies things. If you have further questions, perhaps it would be useful to continue the discussion on the mailing list.

  34. Filipe Says:

    Thanks a lot!

  35. Eckart Says:

    webcam fails to start, despite it was working in 2.3.7 beta. Just recognized that Cambozola V0.68-0041 is starting, but give in the information fps: 0

Leave a Reply

Please read the comment policy before posting a comment.