It should be completely safe. Just make sure you have a backup of your config. I had two licenses for the x86 version about 14 years ago. Both worked excellent. One was an internal router for about 400 nodes and the other an Internet gateway. They were both replaced with Mikrotik routers whenever the company got bought out, but imo, the x86 dd-wrt routers were better for many reasons.
One "trick" I did back then (and probably would not work today) was use a USB network adaptor to register the license with, so I could move the license to new HW if needed. Kinda like a dongle. This was not a secret and was even recommended at the time, but things change. YMMV _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r58662
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk - r58662
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r58662
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r58662
- Linksys MR7350: Testing r58662
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 39, 9 RPis (2,3,4,5), 20 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
It should be completely safe. Just make sure you have a backup of your config. I had two licenses for the x86 version about 14 years ago. Both worked excellent. One was an internal router for about 400 nodes and the other an Internet gateway. They were both replaced with Mikrotik routers whenever the company got bought out, but imo, the x86 dd-wrt routers were better for many reasons.
One "trick" I did back then (and probably would not work today) was use a USB network adaptor to register the license with, so I could move the license to new HW if needed. Kinda like a dongle. This was not a secret and was even recommended at the time, but things change. YMMV
I'm planning to to buy two licences, but will do a fresh installation as I'm planning to use the 2GB-Version.
But I wait until the issue with "CPU in 24/7 Turbo-Mode" is solved.
Then I will test WLAN via M.2-WLAN-Module, and if that works I buy the licences.
Thanks much appreciated.
The CPU stuck in turbo is fixed by putting this in the startup command in the Webgui.
for CPUFREQ in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do [ -f $CPUFREQ ] || continue; echo -n ondemand > $CPUFREQ; done
Yes that includes the words for and done. Just copy and paste this.
Save settings then reboot the system to run this command to fix the CPU stuck in Turbo frequencies.
Just to let you know. The full version is really locked out until you do the activation process. The samba will not work. Ipv6 doesn't save right either. Once you activate it all the functions work including wireless if you have a wifi adapter installed. I suggest making sure all the NIC's are installed before do the activation since the license is locked to the Mac addresses of the NIC adapters.
I'm planning to to buy two licences, but will do a fresh installation as I'm planning to use the 2GB-Version.
But I wait until the issue with "CPU in 24/7 Turbo-Mode" is solved.
Then I will test WLAN via M.2-WLAN-Module, and if that works I buy the licences.
Thanks much appreciated.
The CPU stuck in turbo is fixed by putting this in the startup command in the Webgui.
for CPUFREQ in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do [ -f $CPUFREQ ] || continue; echo -n ondemand > $CPUFREQ; done
Yes that includes the words for and done. Just copy and paste this.
Save settings then reboot the system to run this command to fix the CPU stuck in Turbo frequencies.
Just to let you know. The full version is really locked out until you do the activation process. The samba will not work. Ipv6 doesn't save right either. Once you activate it all the functions work including wireless if you have a wifi adapter installed. I suggest making sure all the NIC's are installed before do the activation since the license is locked to the Mac addresses of the NIC adapters.
Posted: Wed Aug 28, 2024 22:30 Post subject: Updating from free to pro version?
lexridge wrote:
It should be completely safe. Just make sure you have a backup of your config. I had two licenses for the x86 version about 14 years ago. Both worked excellent. One was an internal router for about 400 nodes and the other an Internet gateway. They were both replaced with Mikrotik routers whenever the company got bought out, but imo, the x86 dd-wrt routers were better for many reasons.
One "trick" I did back then (and probably would not work today) was use a USB network adaptor to register the license with, so I could move the license to new HW if needed. Kinda like a dongle. This was not a secret and was even recommended at the time, but things change. YMMV
I have a question the update process went smooth as you said but i thought the max connection were suppose to go to 65000 or so but i'm only seeing 32768?
Just go to the Administration tab and change the Max Connections to 65535. Done. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r58662
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk - r58662
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r58662
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r58662
- Linksys MR7350: Testing r58662
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 39, 9 RPis (2,3,4,5), 20 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
Joined: 16 Jun 2006 Posts: 224 Location: Germany, BW
Posted: Tue Sep 03, 2024 18:23 Post subject:
I now tested the M.2-Wifi-Card based on ATH10k on Build 58283 - 2GB Version.
The ATH10k-Card is working, but without SSH, Administration/Commands aso a real test was at least not possible.
EDIT: No Option to switch to Vanilla-FW.
My biggest issue was the not working USB-Network-Adapter, to make it run i need a few commands on terminal or in Commands-GUI.
So, if one of the DEVELOPERS read this, please fix this issue. Details --> here <--.
