I may be wrong here, but from memory, once telnet access has been enabled, it stays enabled until the router is rebooted. Of course it will do no harm to trigger the url each time but I think you actually only need to do it the once.
I thought that too, but it seems that some users run other programs such as DMT Tool & so on that maight "grab control" of Telnet access, so this was an effort to find a way round that.
Also, it seemed the quickest way to automate things & not need to bother with checking for reboots etc.
FWIW, I have this running 24/7 on another PC, using DGTeam firmware.
As it isn't a live connection, not much is actually gathered in the way of stats, but it seems O.K.
I have also tried it with official Netgear firmware in another DG834GT.
Once Telnet is enabled, the Netgear firmware doesn't need additional login & password details, but they don't need removing from the batch file(s) as they are simply ignored.
rem *************************************************************
rem ***** This is the real code to use on a live connection *****
rem *************************************************************
rem ***** Quietly enable Telnet access *****
rem ***** Seems to need running twice to ensure login *****
wget -q httP://admin:password@192.168.0.1/setup.cgi?todo=debug
wget -q httP://admin:password@192.168.0.1/setup.cgi?todo=debug
rem ***** This one USES LOGIN FILES - needed if DGTeam firmware is installed *****
(echo *1>CON & sleep 1^
& type C:\ADSL_Stats\Apps\LOGIN1.TXT & echo **2>CON & sleep 1^
& type C:\ADSL_Stats\Apps\LOGIN2.TXT & echo ***3>CON & sleep 1^
& echo adslctl info --stats & echo ****4>CON & sleep 1 & echo exit & echo *****5>CON & sleep 1^
& echo ******6>CON & sleep 2 & echo *******7>CON ) ^| Plink -telnet -P 23 192.168.0.1 >> %WORKING_FOLDER%\data$$
rem ***** Quietly Logout of Telnet access *****
rem ***** THis is also run twice to ensure logout *****
wget -q httP://admin:password@192.168.0.1/setup.cgi?todo=logout
wget -q httP://admin:password@192.168.0.1/setup.cgi?todo=logout
rem ***** remove any of the enabling and disabling output files
del setup.cgi*.*
rem ************************************************************************
rem ***** This is the end of the real code to use on a live connection *****
rem ************************************************************************