I couldn't get the factory-to-ddwrt image to program through the stock Netgear firmware upgrade page. It said that it was an invalid file. Googling revealed that the router may require newer Netgear firmware to allow programming DD-WRT over stock. I downloaded R7800-V1.0.2.90.zip from Netgear, extracted the zip and tried to upgrade using that img file, the router also said that file was an invalid file. That's why I ugpraded using the factory-to-ddwrt through tftp. It was never real clear to me if using a webupgrade.bin file was necessary after a factory-to-ddwrt.bin upgrade, but I did it because the web pages were acting so weird. It didn't help. Then, I too though it was related to browser cache so I cleared the Firefox cache, which didn't help. I changd browsers to Edge which shouldn't have had any cached pages from this router, which didn't help. I then downloaded and installed Chrome, so there was no Chrome cache, and that didn't help.
I'm not real sure what a portable browser is, I'll have to do some reasearch.
It doesn't seem to matter anymore, it's working OK now.
Take note I think the free configuration from Proton is only valid for one or two days.
But with the import utility it is easy to add another one.
Been up for about 72 hours now.
If/When it dies I will try the "Extend" button in the account configuration settings, see where that leads.
I think that the selling point for Proton is that the premium(paid) servers are faster because they are less loaded. I use Proton and I really like it. Especially now that they have rolled out Wireguard. @egc has done a bang-up job implementing it and it so easy to use now. _________________ Netgear XR500 - Gateway
R6700 v3 - Station Bridge
For S&Gs I just did Administration -> Factory Defaults -> Yes -> Apply Settings and Reboot. It's still fine. Be it browser cache or whatever, it seems good to go. Thanks again everyone.
Issue: Wifi doesn't turn on according to schedule.
Not new to this release, and I cannot tell when this started since I've only made use of the scheduling functionality recently.
Steps:
1) Disable 2.4GHZ network
2) Set schedule for 5 GHz network
3) Apply and reboot
4) While Wifi is turned off (according to schedule), make changes to schedule or enable/disable auto reboot functionality, apply settings.
5) Wifi will not turn back on according to schedule.
It will take 2-3 restarts for the scheduler to turn on Wifi again according to schedule. Once the the schedule does work, then it will work reliably, given that no changes are made (see step 4).
Router/Version: Netgear R7800
File: dd-wrt-webupgrade.bin
Firmware: DD-WRT v3.0-r49626 std (08/03/22) (prev. DD-WRT v3.0-r49599 std (07/30/22))
Kernel: Linux 4.9.325 #1097 SMP Wed Aug 3 02:01:36 +07 2022 armv7l
Mode: Gateway, SFE disabled, 2.4G and 5G wifi, Wireguard for external access, WAN to 4G (DHCP Client), Keep Alive reboot 6:02 in the morning
Reset: No
Status: Installed at release, ok. One observation: The device wasn't reachable via wire after keep alive reboot, only via wireless. This happend one time. Wasn't able to provoke this behaviour.
This happened three days ago. Maybe it was related to a 4G ISP outtage on its WAN port?
AND
If you don't scroll all way down on a multi page screen before you print to PDF the lil bugger will block whatever is at bottom of page 1
partial pic of PDF I just done without scrolling down to bottom of page
NO, it ain't any big deal just sompin I have to remember before print to PDF ...just like have to remember to disable 'Dracula' theme before print to PDF or will NOT show any highlighted buttons enabled/disabled
Router/Version: Netgear R7800
File: dd-wrt-webupgrade.bin
Firmware: DD-WRT v3.0-r49626 std (08/03/22) (prev. DD-WRT v3.0-r49599 std (07/30/22))
Kernel: Linux 4.9.325 #1097 SMP Wed Aug 3 02:01:36 +07 2022 armv7l
Mode: Gateway, SFE disabled, 2.4G and 5G wifi, Wireguard for external access, WAN to 4G (DHCP Client), Keep Alive reboot 6:02 in the morning
Reset: No
Status: Installed at release, ok. One observation: The device wasn't reachable via wire after keep alive reboot, only via wireless. This happend one time. Wasn't able to provoke this behaviour.
This happened three days ago. Maybe it was related to a 4G ISP outtage on its WAN port?
Hey! I'm having this exact problem right now on build 49492 also R7800. Except I've had it running fine for weeks before it seemed to happen. Reboot has not fixed it. I'm going to try and upgrade to r49599 via web and see if it fixes it. It was strange to fish out my laptop in order to start tinkering with network.