Obviously . If enabling "Software flow offloading" also fixes the instability issue, then you might be lucky and this feature works around the buggy code executed otherwise.
Note that the general instability (in my case) occurred randomly. Sometimes things worked fine for several days and I couldn't reproduce it by navigating to a specific YouTube video. So keep watching. And if possible, confirm your finding here when your box has been running a month without problems.
Hello from Germany too,
I am going to try to do the same.
My first speed medicine test was better for me, I hope it is stable.
This command is well executed:
# Put your custom commands here that should be executed once
# the system init finished. By default this file does nothing.
echo performance > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor
exit 0
Hi there. I'm desperately trying to install the latest OpenWrt on my new Fritz!box 4040 but no luck so far sadly. The instructions on the device page don't need seem to work for me, neither the fritz-tools route not the manual FTP route. The fritz-tools never completes the autodiscovery phase, and via the manual FTP route I can't seem to get an FTP connection established. For the latter, I'm aware of the limited time window during boot when the connection needs to be initiated. On Ubuntu, I let a ping command run during the booting of the Fritz!box and as soon as I get a reply I run "ftp -n -v -p 192.168.178.1" in a separate terminal but unfortunately "Connection refused".
I found another thread ( Fritzbox 4040 flash: FTP connection refused ) where I think the same problem was discussed, and there it was suggested that this is due to more recent firmware requiring a special UDP packet containing the IP address from which the FTP connection will be initiated to be sent first. There is a link to a bash file which should be doing that: https://github.com/PeterPawn/YourFritz/blob/master/eva_tools/eva_discover . I thought I would first run it just to see if it reports finding the EVA, and if that works then run it again with the HOLD parameter of the script set to 1 which apprantly keeps the EVA open after which an FTP connection can be established.
However despite a number of tries running that bash file immediately after powering on the Fritz!box it never seems to be able to find a running EVA bootloader...
Does anybody here have any suggestions what I'm doing wrong or alternative approaches?
You could try the AVM (Windows) Recovery Tool for another (wrong) Fritzbox.
I've done this successfully with the recovery tool for a Fritzbox 4020.
The tool will tell you, that it's not the correct one and finish, but now the bootloader is ready for you ftp in.
On Windows you need a ftp client that supports passive mode (the builtin doesn't)
I used this one: https://ftp.gnu.org/old-gnu/emacs/windows/contrib/ftp-for-win32.zip
Thanks Thomas! Unfortunately I don't have any Windows machines (and it's been a while since I really used one) -- would you happen to know whether that recovery tool and a subsequent FTP connection could in principle be done via Wine for instance?
As I only run Debian without desktop (openmediavault) it don't know if wine would be working.
If wine does not work, my next idea would be Virtual box and a full windows installation.
I fully agree with tomtom. Switch back to stock firmware with a full Windows installation and Fritz recovery tool and try to reflash with manual ftp method as discribed on the OpenWRT Fritzbox 4040 Mainpage. I upgraded successfully with these steps to 21.02. I opened two terminals. One with ping and another with ftp connect. No problem so far.
Thanks frtizl () -- there's in my case no switching back as it is a new device with still the vendor OS on. Interesting that the standard method works for you while I can't seem to get it to work and that's not for a lack of trying/tinkering. Anyhow, as soon as I have another moment I'll try the AVM recorvery tool for a different device method via Wine -- found an entry in WineDB from quite a while ago somebody else had used this setup successfully so that seems my best shot at the moment.
Hey folks! I have a weird issue with freshly bought 4040. I'm on the latest stable (21.02.1). I have 1gbps uplink connected to the fritzbox. When I connect my laptop with ethernet to the ethernet switch port, my download speed is around 850-900 Mbps - pretty impressive. Still, when I connect through 5 GHz ac wifi, the speed in the same test drops to ~300 Mbps. I've already installed irqbalanced, what else might be causing such a huge gap between wired and wireless speed? The same laptop (and other clients) easily reach > 500 Mbps on my old AP.
2x2 802.11ac/ wave2 results in a gross link rate of 866 MBit/s, the usable net rate of that will be around half of that at most. 300-350 MBit/s in practice is about the most you can expect from hardware like this (the interrupt handling alone will keep the CPU pretty busy; actually your wired speedtest results are already beyond my experiences with this hardware) - for (considerably) more you'd need 802.11ax/ wifi6 hardware (and/ or at least 3x3 or 4x4 clients (and APs)).
Hello, I am trying to upgrade the firmware in my router from 22.03 to 23.05
Attended sysupgrade does not work for this major upgrade, so I downloaded the firmware from the device page (compatible with sysupgrade).
But when I attempt to flash the image (from the attended sysupgrade page) I receive this error:
Image check failed:
Thu Jan 4 20:48:17 CET 2024 upgrade: The device is supported, but the config is incompatible to the new image (1.0->1.1). Please upgrade without keeping config (sysupgrade -n). Thu Jan 4 20:48:17 CET 2024 upgrade: Config cannot be migrated from swconfig to DSA Image check failed.
It seem that I cannot keep the configuration settings due to some kind of change.
How should I deal with this in order to get the device working with the same settings?
Which are the changes that the message refers that make the config file incompatible?
I have made a backup of all the mtd blocks (16) and the configuration file, just in case.
The FB4040 has switched from swconfig (22.03) to DSA (23.05).
Backup your 22.03-settings (for reference only), sysupgrade without keeping settings and reconfigure from scratch.
I will have to take it easy, as there is time since I configured it and there are many changes to standard install (VLANS and other things).
Is there a way to have a list of installed apps that later you can send to the luci software install interface in order to reinstall them?
I have read there is te option to rename the etc/config/system and etc/config/network files and force the upgrade.
It seems that the standard files are created during boot and so you can have it running earlier, one you configured your interfaces and system options...
May be it worths try if the system does not brick.
luci-app-attendedsysupgrade in advanced mode should offer you the choice of downloading the sysupgrade image with all the currently installed packages. Then sysupgrade w/o keeping settings.
. If enabling "Software flow offloading" also fixes the instability issue, then you might be lucky and this feature works around the buggy code executed otherwise.
) -- there's in my case no switching back as it is a new device with still the vendor OS on. Interesting that the standard method works for you while I can't seem to get it to work and that's not for a lack of trying/tinkering. Anyhow, as soon as I have another moment I'll try the AVM recorvery tool for a different device method via Wine -- found an entry in WineDB from quite a while ago somebody else had used this setup successfully so that seems my best shot at the moment.