AVM is a German company, and their hardware is mainly sold on the German market, where it is very popular and generally the German-language (and German telecoms-system) versions of their products are the first to be released. It is therefore not surprising that the project started in Germany and most of the developers are German. There are some current ideas of how to better integrate internationalization support, and although most development discussions take place in German, contributions in English are most welcome (and will usually be answered in English).
It is possible to edit some special files (character devices) under /var/flash where the contents still exist after reboot, but this is not true for the rest of the filesystem. The content of these character devices is located in its own rather tiny flash partition. Most data is stored on a read-only SquashFS filesystem which can only be modified during a firmware update, using a SquashFS filesystem image. To permanently include (larger) files into the firmware, they must be put into the SqashFS image, which is implemented in Freetz.
The short answer is no, and this is never likely to be possible. Freetz works by taking the original firmware and applying patches to it. Since the original firmwares contain software which is non-free, as well as some which is free, that means we are not able to distribute finished binary versions. Also, given the number of permutations of modules and hardware then it would be impossible to meet all needs with a limited number of binaries and so it is actually of advantage to have users build their own firmware, tailored to their individual needs.
See the Getting Started page for how to check out the source code and get started with Freetz . Note that this requires a working Linux installation (a Live-CD or Virtual Machine version will do if you do not want to fully install Linux on your computer). Please make sure that you have basic Linux skills before requesting help as this will make your, and our, lives easier.
Still, a rough plan for new releases does exist: 3-4 months after a stable release we declare a "Feature-Freeze" for the following release. From that time on, only bugs are being fixed. The feature-freeze dates are announced in the roadmap . After the feature-freeze you can expect the final release to be released in about 1 to 1,5 months. Between the stable feature-releases there can be some maintenance-releases provided to support newer firmware versions by AVM or some error-fixes.
The trunk is the current development tree. A branch is a tree which is separated from the trunk at a specific time (e.g. r2759 ). Currently the following branches are available: freetz-stable-1.0 and freetz-stable-1.1 . All release versions are tagged (e.g. freetz-1.1.4 )
Attention! The development version (trunk) is only recommended to novice users with basic Linux knowledge who can troubleshoot elementary errors and can give proper feedback to the developers. Because the trunk is an ongoing development version, it won't be as stable as the branched and tagged versions.
Packages tagged with "binary only" do not supply any web frontend, init script or anything similar. They provide only the binaries themselves, which means you have to take care of the configuration, initialization etc. yourself. (Note: Other than the name (maybe) suggests, these packages are - along with every other package in Freetz - built from source.)
Check the advanced option Enforce urlader environment and put avm in Patches > Enforce firmware_version variable to build German firmware for an international box. If you want to do this (or the other way around with avme for English firmware on a non-international box), read about recovery and have a working/recovery image ready.
If the build process was interrupted by this message, maybe some packages providing the needed library are missing. This can be caused by selecting some options or packages in menuconfig. Please install the needed libraries by installing the packages and restart the build process.
This happens every time AVM releases a new firmware version. Normally only the newest file is available on the AVM FTP server. Freetz can only support the version that's current at the release date. Due to license restrictions, we cannot provide these images. Possible solutions (prioritized by difficulty):
Please use the last 2 possibilities at your own risk. If it's just a "bugfix release" (like the update from .57 to .59) it should work without errors. However, if major changes were done by AVM at the latest firmware release, use it carefully!!
The image is small enough to fit on flash memory, but you have not enough free space left for the answering machine, or non space left. The firmare should work in spite of this message, but to ensure a fully functional answering machine or fax service, you should use an FAT-formatted USB-Stick to use this space for the answering machine, fax service and other services.
The default password for freetz (both for console and web login) is "freetz". Login name for console is "root", and for the web interface it is admin. When you first log in using telnet or ssh, you have to change your password.
The whole configuration on the Fritzbox can be found under /tmp/flash. This is important if you build a Freetz firmware, because the configuration is not located in the static firmware part of the image. All files located under /tmp/flash were not be edited during a firmware update, so the configuration files will be keeped after a firmware update. Important, always execute "modsave" after making changes on the configuration files under /tmp/flash, to save them in the flash. More information about that see below.
ATTENTION: Between x and > there must be at least a single blank space. If there isn't, the file will be empty. (echo will redirect to stdout. The output would be empty then. Alternatively, you could also write "x">security.
Background: The script /tmp/flash/webcfg_conf will be preferred compared to /etc/default.webcfg/webcfg_conf to create the configuration file. An empty script /tmp/flash/webcfg_conf will create an empty configuration file without a password.
Please consider, that this change will NOT persist across reboots. So after a reboot, you still have the old unknown password.
Therefore, you should change the password of the Box in the freetz-menu under Settings before you reboot your Fritzbox.
The default limit set by Freetz for the maximum size of the configuration was exceeded. This limit is a protection to prevent an unintended full TFFS. This limit can be increased, but you should keep an eye on the current fill level:
The images for ar7 with kernel 4.9 build fine in a virtual build environment. Unfortunately the EVA image isn't running with the Fritz!Box. Maybe someone else had better luck after all or got some tips.
Freetz is a firmware EXTENSION and modification for Fritz!Box routers and compatible devices. The original firmware of the manufacturer is expanded with additional functions and supplemented with an individual compilation of programs. More about the name "Freetz" and the history see FAQ.
Freetz is free software and is developed by Oliver Metz, Alexander Kriegisch and Team.
since the 7170 and 7270 boxes are very solid robust hardware without firmware updates form vendor and also do not speak latest DSL protocols, so tons of those boxes went into recycling... what a shame.
Now we start VirtualBox and select the correspondingnd VM-image.Freetz-Linux will then start and you can login using: freetz andfreetz as username and password followed by the enter key eachtime.
The next step is to find out which ip is assigned to our Freetz-Linuxsince we need it to get access via putty in the next step. To check,type in: ifconfig. This should bring up the following text.
The access data for PuTTy are login: freetz password: freetz
Please be aware that the password is not shown while typing. Afterconnecting to the Freetz-VM you should update it by entering thefollowing commands:
Confirm each command by entering the administrator password freetz.(If there should be a special inquiry for a certain update, activate thesystem advisors packages and activate by hitting ok).
This will download the newest stable Freetz source code (in this case:version 2.0) from the subversion repository. Here you can find out if anewer version has been released: tags/.After the download has finished you will see this message: Checked outrevision xxxx, e.g. xxxx=6526. Please look into FIRMWARES file forsupported firmwares. The release version can be out of date.Change directory by entering cd freetz-stable into your Freetzdirectory and enter make menuconfig.
This is the acutal Freetz interface where you select your router. Forthis tutorial we selected the 7270-V3. After selecting the router type,exit menuconfig by selecting exit and hitting enter and confirm thequestion with Yes. Then enter make and hit enter. Now you shouldsee this:
The creation process will start. For the first time it might take a verylong time depending on your computer and internet connection since allinital packages have to be downloaded. Once this is done the creationprocess will be a lot faster if you make only small modifications. Therehave been many warnings during the process but in the end there will bea message that an image has been created. The corresponding image willbe created in the subfolder images of your Freetz directory. Thiswill be the final message:
Once the image is on your computer you may start. But you need to makesure to be prepared for the most unusual things to happen, e.g. that thebox does not function correctly after flashing. Therefore we urge you totake precautions:
7fc3f7cf58