Archive for the 'Uncategorized' Category

Debugging 3G dongle support

Thursday, October 9th, 2014

In our latest firmware release for the 2.0n and 2.0g, beta1, we introduced completely rewritten support for 3G devices. This new code should work with more devices out of the box, but the main feature is improved debugging support. This means there are some knobs and switches that allow you to tweak how the Fonera talks to your 3G device.

If you want to make your 3G device work with the Fonera, be sure to read this post carefully. It contains a lot of info, so it’s easy to miss a detail or skip over some important instructions. Especially if you file a bug report, read carefully to prevent duplicate reports and a lot of extra work…

This post will detail these knobs and switches and documents when to use which. It’s not guaranteed that you can actually make any 3G device work using these instructions, but they should help you make it work if possible and if not, collect enough information for us to have a look at it. But first, I’ll provide a bit of background on how a 3G device typically works.

3G devices background
When you connect a 3G device, it will tell the Fonera what kind of device it is so the Fonera can load the appropriate drivers for it. However, most 3G devices will initially lie and say they are a a read-only storage device (like a USB cd-rom player). This storage devices then contains the Windows drivers for the 3G device, so Windows users can easily install those.

After installing the driver on Windows, it will send a special command to the 3G device, telling it to switch into modem mode. In response to this command, the modem will (virtually) disconnect and then represent itself to the Fonera as a brand new device that supports a number of modem ports. On Linux (and on the Fonera), this part is handled by the USB modeswitch software automatically.

Each of the modem ports exposed by the 3G device have some specific function. Commonly there is one control port, over which commands can be sent to set up the device and get status information and one data port, over which the actual data transfer happens. Sometimes there are additional ports, used for diagnostics or different modes of operation). Unfortunately, there is no universal automatic way to find out which port is which. Some manufacturers offer some way to detect this, but these ways usually don’t work with all devices.

Even though there some standards for (3G) modem devices, not all devices and manufacturers implement them in exactly the same way and some devices have specific quirks in the order they need to receive commands, etc. For doing the modeswitch, every device needs some magic command for which there are no standards at all. On Windows, these quirks are handled by giving each device its own driver (or some manufacturers uses a single driver that knows about all the quirks for its own devices). On the Linux desktop, there is software available (modem-manager) that knows about a lot of these quirks and can talk to most 3G devices. However, this software (and mostly its dependencies) is way too complex and big to run on the Fonera, it wasn’t written with embedded devices in mind. Instead, we’ve written a new piece of software, called udiald (and made the source available under the GPL license), which aims to support as much devices as possible using only a small bit of code.

Debug application
To assist in debugging (3G) issues, we’ve created a small debug application that makes it easier to collect debuging info through the webinterface (instead of having to run commands through SSH). Right now, it allows collecting log output and USB device info.

You can install this debug application through the “Applications” page on your dashboard. For now, it’s only available for this beta release. After a bit more testing, we will probably make it available for the 2.3.7.x stable release as well.

Configure provider info
Before you click the “connect” button for your device, you’ll have to tell the Fonera about your 3G provider. You can do this by clicking the “Configure” icon below the list of devices.

For the connection to be made, your device needs to know the “access point name” (apn) to connect to. Using the wrong or no apn usually breaks the connection, or can cause the wrong payment plan to be activated, so be sure not to skip this step. Additionally, some providers require login credentials for the connection, though these are often not a personal login, but some generic one.

The other options on this page can usually be left at the default values.

Attaching your device
When you attach a 3G device, the Fonera will autodetect it and it will be listed on the “3G/UMTS” page on your Fonera Dashboard. This page lists all devices that look like a 3G device (i.e. that have modem ports), not just those which the Fonera explicitely knows about.

However, it is still possible that your device is not listed on this page, most likely because the USB modeswitch software didn’t know about it or the mode switch failed for some reason. If this happens, please file a bug report so we can have a look at what is wrong.

If your device is shown in this list, the column “Device configuration” will show which configuration the Fonera has decided to use with your device (based on the USB identifiers of the device). Looking at this configuration profile, there a few cases:

  1. It shows the brand and model number of your 3G device. This means that someone has actually tested your device model before and the Fonera has a configuration profile specifically for your device. It’s highly likely that it will work right away, so best to just try it (but don’t forget to look at the “preparing to connect” section below). If it doesn’t work, skip to the next section.
  2. It shows the right brand, but the wrong model number. This means that the device’s manufacturer has used the same USB identification numbers for two different device models. This isn’t supposed to happen, but unfortunately it does. However, it’s likely that the same profile will actually work for both devices, so just try it. If it doesn’t work, skip to the next section.
  3. It shows “Huawei 12d1:1001″ or some other number. This is a special case that occurs only for Huawei devices. Your device has not actually been tested with the Fonera, but we managed to get at least some of the settings (control and data port) out of a Linux driver created by Huawei. In this case, it’s likely that your device will work right away, so just try it (but don’t forget to look at the “preparing to connect” section below). If it doesn’t work, skip to the next section. If it works, please file a bug report to let us know.
  4. It shows “Generic ZTE”, or something else starting with “Generic”. This means that the Fonera doesn’t really know anything about your device, except the manufacturer. It selected a profile that contains some generic settings, but it’s likely that those won’t work. You could try connecting, but you’re probably better of going to the next section to look for the right settings. Whatever the outcome be sure to file a bug report with your findings.

Finding out the modem port numbers
So, if your device doesn’t work yet, you’ll have to find the proper settings for the device. As mentioned above, each modem has a number of ports (numbered starting with 0), of which one is the “data” port and one is the “control” port. To find out which is which, we’ll have to do a bit of trial and error.

To make changes to the configuration profile for your modem, click the “Modify” link in the “Device configuration” column. The page shown will allow you to change various modem settings. The “Based on” dropdown allows you to copy settings from another profile (which could help if your unsupported device is similar to another device that is supported), but you can also just specify the settings manually.

To fnd out the correct port numbers:

  1. Find out what ports respond to AT commands. 3G modems use “AT commands” (like oldschool dialup modems) to communicate through the data and control port. Since the other ports don’t usually respond to AT commands, we can quickly rule them out as candidates for the data and control ports.

    To do this, set the control port to 0, click “Save” and then click the “Probe” button for your device. This will try to probe the device on its configured control port and show you the output. If you get a lot of output, including a “Identified as …” line near the top, this port is a candidate (even if the output also shows some errors further on, since not all devices respond to all probe commands). If it shows only a few lines like “Poll timed out” and “Unable to identify modem”, then it is not a candidate port.

    Repeat this process for every supported port (e.g., every port number in the dropdown). Don’t stop when you found two candidates, since sometimes there are more than two candidates (and the first two might not be the ones you need…).

  2. Now you know which ports are candidates, you need to figure out which is which. In general, any of the candidate ports will probably work as the control port, sometimes not all of them will work as the data port. You’ll have to just try different combinations to find out which one works. Often, the data port is the lowest numbered candidate, so you’ll likely want to start with that. Also, it does not make sense to use the same port as data and control port. The interface does not forbid it currently, but it will probably not work…

The dial command
When the modem is all set and ready to make a connection, the dial command is used. Unlike the old school modems, the 3G modem doesn’t actually dial a number (I think), but it’s more a magic command to let the modem know to set up a connection.

The default dialcommand should work for most modems (in fact, it worked for all the modems we tested with), but some modems (or providers?) might require different dialing commands. In particular, EVDO or LTE modems are rumoured to need one of the other commands in the dropdown, though we haven’t had any of these to test with.

The mode commands
The last five commands are used to set a preference or force the use of the UMTS or GPRS networks. The values you set here are the commands to use for this modem, to change the actual mode used, click the “Configure” icon below the list of 3G devices.

If you test other modes than “auto” and these commands don’t work, please file a bug report about this. There’s no ready-made instructions of other commands to try, but perhaps we can figure something out for your specific device.

Filing a bug report
If your 3G device doesn’t work out of the box or at all, or the instructions above tell you to file a bug report, you’ll need to take some steps to make a proper bug report on the Fonosfera trac. Here’s how this works:

  1. Do a search on the trac to see if someone else has already filed a report about your device. It’s best to search for the model number of your device (without the brand name) here.

    If you find a report about your device, you can leave a comment to let us know you also have this device. If you fill in your e-mail address, you’ll get notified of any followup comments on the bug report as well.

  2. Collect information for your bug report. We’ll need:
    • The make and model of your device
    • A description of what is working and what is not and what you have already done to debug
    • The log output shortly after plugging in the device and doing a connection attempt (can be retrieved using the debug application, see above).
    • The detailed list of USB devices (can be retrieved using the debug application, see above)
  3. File a new report. Be sure to include your e-mail address in the “reporter” field so you get notified about comments. To include the info collected above, use the {{{...}}}” trac syntax to keep the info readable (hint: Use the preview button to see if you got it right).

    Paco Jr: small bugfix release

    Thursday, December 26th, 2013

    While we keep working on revamed 3G support for the next feature release, we also found some small but important bugs or regressions. To make sure you have the most stable firmware possible, we’ve collected the most important bugfixes and put them in the Paco Jr. release.

    What changed?
    Here’s the (exhaustive) list of changes:

    • Prevent a brute-force attack on the private wifi signal when WPS is enabled.
    • Make the “Media” share work again.
    • Make file sharing on 2.0g work with Windows Vista and up without having to change the LMCompatibilityLevel registry setting.
    • Update the Twitter to the most recent Twitter API.

    Overall, we recommend all users to install this update.

    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.

    In the coming weeks, we will also offer this firmware upgrade directly from the dashboard, making the upgrade even easier, but this procedure needs a bit of testing before we enable 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).

    The above links point to the end user’s versions of the firmware. For different versions, like the developer’s version (which allows SSH access and custom plugins) and the .img version (which can be installed through SSH), you can look in the PacoJr directory on the download server.

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

    Have fun! release candidate released!

    Friday, October 5th, 2012

    We’re nearly there! The first release candidate is available, which contains all the changes we’ve planned for the final release. We’ll now enter a period of more extensive testing, to find any remaining critical bugs or regressions. In the best case, we’ll not find any and the final release will be identical to to this release candidate.

    What changed?
    This release brings mostly bugfixes and a pile of Here’s a few highlights:

    • The Transmission torrent client was updated to version 2.71.
    • Wifi channels 12 and 13 are now available in countries they are allowed in
    • OpenVPN is a lot more configurable (many thanks to Jon Spriggs for contributing patches for most of these changes!).
    • USB audio devices work again (this got broken in beta3).
    • USB disk support improvements

    For the complete list of changes, see the changelog.

    What about my feedback?
    We welcome more feedback about this release, so go ahead and comment or post away. This does not just mean issues or problems: If you test a new or fixed feature and it works for you, we’d like to know as well. Feedback is welcome through various channels: comments on this blogpost, the development mailing list, IRC or by creating a ticket on our trac.

    Note that at this point, we might not fix all bugs reported, but limit to critical bugs or regressions that were introduced by the recent releases. The goal here is to make as few changes as possible, to minimize the chance of introducing new bugs again.

    So, how do I upgrade?
    To install this release candidate, download the web upgrade tarball here, navigate to your Fonera’s dashboard through “Settings” and then “System” and upload the downloaded file 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).

    The following versions are available. Note that because this is release candidate, only the developer’s version is available, not the end user’s version (but you can freely switch between versions without problems). 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).

    It seems that in some cases, the 2.0g fails to flash a new firmware through the webinterface due to insufficient free RAM. 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.

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

    Have fun!

    Update: This release contains a bug breaking PPPoE mode when set to use the automatic DNS server address. If you have this configuration, either switch to a static DNS server (like Google DNS), or see ticket #1229 for a fix.

    Update: This release contains a bug breaking the 3G settings page in all cases. See ticket #1228 for a fix for this problem. release plans

    Wednesday, October 13th, 2010

    I’ve announced this post a long time ago, but I’ve finally gotten around to write a bit about our plans for the next release. I’ll try to be as specific as I can in this post, but of course I’m not 100% sure about how will look or when it will be released either. So, expect some things to change from what I say here :-)

    The primary goal for is supporting 2.0g again. It’s been a long while without updates for 2.0g owners. Each time there was some important argument to get out the 2.0n update sooner and leave 2.0g for a while longer, but we really should get the latest fixes and features working for 2.0g again. So the plan is to release for both 2.0g and 2.0n. Having the same version working on both Foneras will also make our life a bit easier, since investigating bugs is easier when we only need to check a single firmware version :-)

    In addition to this, we’re trying to squeeze in some actual bugfixes and features as well. A good indication of these plans is the milestone in trac, which lists the tickets we hope to get closed for (or have already closed). Note the word “hope” here: We’d like to close as much of these tickets as possible, but if fixing them takes too much time, we might release without them.

    Some highlights:

    • Updating some upstream software: Transmission, usb_modeswitch and OpenVPN.
    • Fixing the twitter plugin (which is broken because Twitter changed its authentication scheme).
    • Some fixes related to special characters in filenames on USB disks.
    • Some improvements for developers (more usable opkg, easier plugin building, etc.)
    • Fixing the music plugin again
    • Enabling wifi repeater / wifi-wan mode again. This needs an update to the wifi driver for 2.0n so it hopefully becomes stable enough to enable in the non-dev as well.
    • Bridge mode for 2.0g. This wasn’t actually planned, but when thinking about it a bit more closely a few weeks back, this appeared to be easier to implement than I had originally thought. I’ve since worked on this and found out that it wasn’t so easy after all, but it is nearly working now, so will probably be included after all.

    To get an idea of the fixes committed already, you can look at the closed tickets above, but also at the
    revision log for trunk. Anything that is commited to trunk right now, will be included in th release (though we might create a 2.3.7 branch later on).

    One issue that needs some attention as well is firmware size: The main firmware has slowly grown a bit over the last year (mainly due to the addition of OpenVPN and OpenSSL). This works fine on 2.0n, but 2.0g has slightly less Flash space available, leaving only a few hundred KiB for plugins. Perhaps we can save some space here and there, or perhaps we’ll release a firmware version without OpenVPN included. We’re not sure yet.

    As for the actual release process: There will probably be a beta release first. Since there’s quite some changes, particularly for 2.0g, I expect some new problems to emerge when people start testing. After the issues in the beta release are fixed, there will be one or more release candidates (RC) and finally the actual release.

    Comment policy & asking questions

    Tuesday, June 29th, 2010

    In my previous post, I promised to say a bit more about the policy regarding blog comments. In the past, we’ve seen a lot of blog comments that were either spam (no relevant content and links to other sites), off-topic (questions or statements related to the Fonera, but not relevant to the particular post) or simply inappropriate (containing swearing or insults).

    As of now, the Fon policy regarding user feedback is the following:

    • Stay on-topic. The blog is not a place for general questions or remarks, so please only respond with comments relevant to the post in question. Off-topic comments might be deleted.
    • Stay polite. It is ok to criticize in a constructive way, it is not ok to use inappropriate language or make derogatory remarks. Inappropriate comments will be deleted without exception.

    In short, don’t be a troll!

    When you post a comment, it will be spamchecked using Akismet, spam is deleted right away. If it is your first post to the blog, it will be held for moderation. We’ll try to frequently approve posts, but it might take a few days. After your first comment is approved, any subsequent comment should be published right away.

    Where do I post my off-topic questions, then?
    A lot of users have been using the blog to ask a myriad of questions about the Fonera and its development. Since the blog isn’t quite the right place for this, here’s a few places you can ask your questions instead:

    • The forums are appropriate for most questions. Here you will get answers for other users, FON support staff and sometimes developers.
      The forums are good for questions like “Has someone tried installing jdownloader on his Fonera?”, or “What’s the difference between the Fonera firmware and OpenWRT?”
    • FON support has some FAQs, a knowledge base and you can contact them in case you’re having problems with your Fonera, your various Fon accounts or accessing the FON wifi networks (use the “Contact Us” link at the top right).
      FON support is good for questions like “How do I register my router?”, or “What ports do I need to open to use torrent downloads?”.
    • The IRC channel is appropriate for short development questions or to get help collecting information for a bug report. Here you will get answers from other users and developers. You can also try to ask more general questions, but remember that we’re busy with developing the firmware as well!
      If you use the IRC channel, don’t wait for someone to show up first, just ask the question you have and be patient (rule #1 on IRC: don’t ask to ask, just ask!). Don’t be surprised if it takes a few hours or even a day or two to get an answer: We’re not online 24/7, but do usually read back what we’ve missed.
      The IRC channel is good for questions like “What file handles the 3G connection setup” or “I think that DDNS is not working in bridge mode, what info do you need?”
    • The Fonosfera development mailing list is a good place for (longer) development questions. This list is read by the developers and the more advanced users, so there’s a good chance you get an answer to your complicated questions here. This is probably also the best place to ask about the development roadmap.
      The mailing list is good for questions like “I tried to create a plugin to do [something], but I’ve encountered three problems: [long description]”, or “Would anybody be interested in having a plugin for [some program]?”
    • The fonosfera Trac is the place to report bugs or request features. Do take care to search for existing reports first. Please read this wiki page before reporting a bug.

    And finally, whenever you ask a question be sure to think about it and phrase it properly!

    Update: Added a paragraph explaining how the moderation system works.

    Some said it’s better… let’s see if all think the same!

    Thursday, March 18th, 2010

    Hi guys, new firmware around the corner.

    But we need more testing now. We have done tests with some volunteers that we are so thankful for, but now we need more feedback. We are releasing a Release Candidate for soon.

    It is not a final image: We don’t consider it stable and it has bugs that we expect to fix when the final is released. However we feel it is now ready for some field testing.

    So, what should you expect from this test firmware?

    • The FON Hotspot feature has been fixed. You can share your WiFi again at your will.
    • We have fixed the WiFi issues that the Fonera was having with the BCM4325 chipset from broadcom. This WiFi chipset is used by the iPhone 3Gs, many last generation iPods, some Apple laptops and desktops and other brands (Dell etc).
    • We have been in close touch with RaLink, our chipset vendor, to make sure the WiFi configuration is the best possible. In previous versions we had a couple of values that were not completely optimized. Now the WiFi conf should be the best.
    • Improvements in the 3G system: we have made some internal cleanups so the 3G configuration is cleaner. For instance, you can now reset the 3G configuration when it’s dialing, in case it seems to be stuck.
    • We have replaced the software that controlled the 3G dongles with “usb_modeswitch”: a software that will allow us support many more 3G dongles and will make it easier as well. This doesn’t mean all units will work out of the box but many will and others will be easy to fix in the near future.

    These are the things you might miss:

    • We have removed the “Repeater Mode” or WiFi-WAN mode. It was unstable and until we find out why, if ever, it will be switched off.
    • Torrent, DLManager, Samba etc. have had no changes. As we said many times, we will first try to make the base system (mainly connectivity) as stable and reliable as possible.

    These are things we know are wrong:

    • MAC OSX 10.6 seems to have issues with the 802.11d protocol (country code exchange protocol) over 802.11n. What does it entail: when WiFi is enabled in OSX, it will listen to any APs around. The first one that sends a message containing a country code, will determine the country selection of OSX. Once a country is selected, OSX will refuse to connect to APs advertising different country codes.
      How does this affect users? The Fonera is broadcasting US as the country code. If you live in Europe and your OSX gets a frame from a different AP saying it’s in Spain, for instance, then it will refuse to connect to the Fonera since it is in a different country (US).
      This bug is not Fonera exclusive, (seeĀ it happens to OSX with any AP that has a ‘wrong’ country code. We will very likely add a dropdown menu so the user can chose what country the AP is in.
    • MAC OSX (other OSes not confirmed yet) seems to get micro-disconnections from time to time. We are still studying this issue.

    When can you expect to test this new test firmware?

    Well… we are aiming for next week. Can’t promise yet but it looks like we might be able to have it cleaned up and ready for you guys to test. Please, bear in mind it will be a test version and only those who feel confident (or desperate enough) should try it :)

    Thanks for reading all the way down to here!

    One more short update about the Fonera 2.0n

    Tuesday, March 9th, 2010

    Hi all,

    We have successfully tested some of the fixes today (or so we think so) and have an image almost ready for user testing. We have selected a set of users that have been reporting FON bugs consistently and in a comprehensible way in the last months to us. Also, they have experienced most of the important bugs that have been reported, so are good candidates to represent most of the rest.

    Those users will be helping us test the firmware in the field. If you are not in that list, please forgive us and be patient. More users means more feedback (better), we know, but also much more coordination work. So, please understand we wanted a kind of reduced and well selected set of testers.

    We still are working on some fixes, so what they will test is not meant to be a pre-final firmware, but an advanced stage firmware, with some important fixes. We can advance there is no major changes, don’t expect a cool super-fancy firmware, but just what we considered the most critical bugs (wifi connectivity, fonspot, stability, some 3g dongles support…) fixed.

    How long will they be testing? Well, that depends on how good we made our work till now. Hopefully one week approximately should do it. Meanwhile we will keep working on the still open bugs and hopefully have a ‘final-to-be’ firmware ready for them by next week. Let’s cross fingers!

    These users are, of course, free to talk about their findings about this new firmware with the rest of the community. They can blog, post, twit, comment, share on IRC… whatever they want.

    Stay tuned and thanks again for your patience and trust!!

    So, what is the status now?

    Monday, February 22nd, 2010

    Hi all,

    I am here to let you know a little bit about our current status of work, especially regarding the fonera 2.0n but also some other things.
    As promised, now that the Fonera Simpl has been announced, we can communicate a bit more about what we’re working on. Sometimes, it might be that we are not working on your specific device, but we hope you will forgive us.

    The Fonera 2.0n is already seeing some progress:
    – We have reused the wifi driver of the firmware RC1 which made the fonera more stable and also made all throughput problems with broadcom chipsets (some iphones, ipods, macs and other laptops) vanish.
    – The FON funcionality that we broke in the RC1 has, of course, been fixed ;)
    – We have added the mode_switch driver: this will permit us to support more 3G dongles and do it in a easier way. We expect to test about 10 models by ourselves and probably will support many more out of the box!!!

    These are our biggest focus right now. We are still at the firmware team testing process but will soon get into QA and we also plan to get some of you involved in the testing. We already have a list of people that are willing to test it: either to help us or for the hope of having their bug fixed :)

    So, stay tuned, we are already moving little by little.

    As for the fonera 2.0g, we don’t forget about you, just these changes are fonera 2.0n specific. The only common part is the 3G dongle support and that improvement, we will try to add some day when it is confirmed it works fine in the fonera 2.0n.

    In parallel, we are also continuing with the development and testing of the coming fonera Simpl. We will soon make some code public and will publish everything probably before the official launch in Europe. It is a nice and small device, you will see.

    Thanks again for your patience and help, we hope to get you a good firmware soon!

    Long time without updates…

    Friday, February 12th, 2010

    Hi all,

    First of all, my personal apologies for not having posted anything in such a looooooooooooong (not enough ‘o’-s, I know). I know many are expectant, many angry and some bored. I can’t blame them.

    It’s been a huge load of work since my last post in December. Out of a sudden, everything had to be restructured and rescheduled due to an upcoming new product. Whatever the reason for the decision was, I could do nothing but follow it. I do understand the feeling many might have, of being left behind, especially for the lack of comunication: I want to say that it was 90% because of lack of time (informing is not only posting an entry but following up on it and IRC and forums etc) and 10% because I could not talk about why a new firmware was being delayed and I didn’t want to lie. So I thought it was to better shut up than liying.
    As many of you know, we are launching a new product soonish and we need to work a lot on it. However we have not stopped developing for the Fonera 2.0n. The new product is based on the same Ralink chipset family, so some of the fixed bugs and improvements we have done for the new device will also be present on the next firmware release for the Fonera 2.0n.

    We have been working on the Fonera 2.0n on a best effort basis and we expect to very soon be able to focus on it with the following target in mind: release a stable firmware that does all the WiFi router funcitonalities well. We are now reschedulling projects but I can already say we are aiming to release it on mid March. We mostly want to make sure we do proper QA this time and not rush, it just doesn’t pay.

    This is our short term aim. For the long term, we expect to merge both firmwares, the one of the Fonera 2.0n and that of the new Fonera SIMPL, with the hope that it will be a robust and stable, feature-rich firmware.

    Please, accept my apologies, again, and try the new firmware when we release it: I believe it will satisfy most of you.



    PS: there are some unpublished comments on the previous posts and some on this one might remain unpublished too. It’s not censorship (which I’m not against in some cases): you can see we publish very critizicing comments. It’s lack of time to go over all of them to see if they cross the line or not. Somee good ones are unpublished as well. Sorry about that :( They might eventually be published.

    Young Rudolph passed away…

    Tuesday, December 22nd, 2009

    Hi all,

    Some of you might have noticed that Rudolph has been removed from the location it was made publicly available at. Many wonder why… well, Rudolph had a congenital illness: the FON Hotspot did not work and also, it registered a wrong MAC address on FON’s system.
    Anyway, you can still compile the image from svn if you want to use the rest of the benefits.
    We are working hard, even if it is Christmas and will try to release a new fixed RC asap.

    Also, will be available for the Fonera 2.0g too. A bit later than for the 2.0n, but it will come.

    Thanks for understanding.