› UKTH forums › 🛜 Wireless Routers & Modems › AVM & Wireless › AVM Fritz!OS 7.50 (FW release-cycle MOVE21) First modem got the new firmware version 7.50 just in time for Xmas. Fritz!Box 7590: https://download.avm.de/fritzbox/fritzbox-7590/other/ **New features:** ———————————————————— – FRITZ!OS 7.50 – with over 150 new functions and useful... › Reply To: AVM Fritz!OS 7.50 (FW release-cycle MOVE21) First modem got the new firmware version 7.50 just in time for Xmas. Fritz!Box 7590: https://download.avm.de/fritzbox/fritzbox-7590/other/ **New features:** ———————————————————— – FRITZ!OS 7.50 – with over 150 new functions and useful…
OS 7.55 final released for Fritz!Box 7530: https://download.avm.de/fritzbox/fritzbox-7530/other/
OS 7.55 final released for Fritz!Box 7590: https://download.avm.de/fritzbox/fritzbox-7590/other/
# New functions of FRITZ!OS 7.55
## System:
– **NEW** In the new energy-saving mode, Wi-Fi, LAN and USB use even less power for slightly reduced performance
– **NEW** New wizard transfers all important Internet, telephony, and WLAN settings as well as connections to mesh, telephony, and smart home devices to a new FRITZ!Box <for more, see [7]>
# Further Improvements of FRITZ!OS 7.55
## Internet:
– **Improved** Clarified wording when configuring WireGuard VPN connections
– **Improved** NTP interoperability improved through better estimation of the hardware clock’s deviation
– **Improved** Optimization of bandwidth reservation in the home network through adjustment to transmitted downstream rate
– **Improved** Optimized switching from public DSN servers to provider-side DNS servers
– **Improved** The setting to send all IPv4 data traffic of the FRITZ!Box via the WireGuard VPN connection to (!) a single device is no longer supported
– **Fixed** “Reserve bandwidth in the home network” did not work with IPv6
– **Fixed** During preparation of the first WireGuard connection via remote dial-in the FRITZ!Box ended up in permanent wait mode
– **Fixed** In certain scenarios, switching the type of internet connection led to the WAN interface being switched to LAN
– **Fixed** Interoperability of IPSec VPN connections to LANCOM remote sites including usage of VNC and RDP with active packet acceleration not available
– **Fixed** MyFRITZ! access permission (device sharing) could sometimes only be terminated via IPv4
– **Fixed** Occasionally an IPv6 prefix sharing of a previous “outdated” prefix for a downstream router was not deleted
– **Fixed** On DS Lite connections, switching off IPv6 manually (incorrect configuration) could result in repeated dial-in attempts by the FRITZ!Box
– **Fixed** On TIM connections (Telecom Italia), configuration of a WireGuard connection led to repeated clearing of the internet connection
– **Fixed** Parental controls: Tickets for devices with the standard profile could not be redeemed
– **Fixed** Problems with functionality and/or display of the parental controls in certain application scenarios
– **Fixed** Repeaters sometimes used external NTP servers for initial time determination even if the upstreamFRITZ!Box offered an NTP server
– **Fixed** Under certain circumstances a switch to public DNS servers occurred although the current DNS server could be reached
– **Fixed** Under certain circumstances a switch to public DNS servers took place too early
– **Fixed** VPN: When configuring an IPSec-LAN-LAN connection, the address of the FRITZ!Box was not proposed
– **Fixed** When all IPv4 data traffic was routed over a WireGuard VPN connection, incoming calls were not always signaled
– **Fixed** When packet acceleration was enabled during longer LAN-LAN linkups to CISCO remote sites via IPSec, occasional connection losses occurred
## Wi-Fi:
– **Fixed** Mesh Repeater operating mode: The “Select Wi-Fi Network” list did not display invalid Wi-Fi network names (SSID)
## Mesh:
– **Fixed** After changing the connection of a repeater, the connection display on the “Home Network > Mesh” page of the user interface was wrong
– **Fixed** When using certain powerline adapters together with a network switch, the connection display on the “Home Network > Mesh” page of the user interface was wrong
## Telephony:
– **Improved** Robuster handling of inconsistent data in Apple telephone contacts
– **Improved** Support for using up to 10 individual telephone numbers (MSNs) with the “Telekom CompanyFlex” rate
– **Change** Outdated entries removed from the list of telephone providers
## DECT:
– **Improved** Support for DECT headsets from the Sennheiser EPOS series for outgoing calls and picking up calls via the headset button
## Home Network:
– **Fixed** Devices with a dot in their name could no longer be renamed
– **Fixed** Display for search for updates for devices in the Mesh was not suitable in certain cases
– **Fixed** Possibly lacking rendering of IP addresses could cause subsequent defects
## System:
– **Fixed** “Change notice” push service sent too often information on supposedly new port sharing
– **Fixed** Repeater events were occasionally listed twice in the Event Log
– **Fixed** There were too many events on changed settings in the Event Log
## Mobile Network:
– **Improved** Internet connection with username/password supported for Alcatel IK41VE1 IoT/M2M 4G (MBIM) mobile network dongle
## USB:
– **Fixed** No network drive function (SMB) could be established to Rclone
– **Fixed** WebDAV online storage could not be used when the country was set to “Spain”
————————————————————
You need to login in order to vote
