New DGteam Firmware (DG834GT)

Well, the changelog is usually a good place to start...


1014: ADSL DRIVER UPDATED TO VERSION 023k for Annex B Brcm models;
Added ip conntrack clean capatibility on GTB/PN/PNB Zonked Quokka brcm vanilla kernel;
Fixed bug on PN wifi section (wep/wpa encryption modes disabled at kernel stage);
Fixed bug on cgi vpn (access mode cut off);
Enhanced sip alg module capatibility on GTB/PN/PNB;
Code-cleanup on dgteam software improving speed & reducing code size & memory usage.


1012: EWGET ADDED (in addiction to standard wget command with openssl https auth support) (Eric Bishop @Gargoyle);
OPENSSL UPDATED TO VERSION 1.0.0 (with many revisions & security fixes: see respective changelog on its homepage);
BUSYBOX UPDATED TO VERSION 1.16.1 (with embedded udhcp in place of standalone version);
NBTSCAN UPDATED TO VERSION 1.5.2 (in place of namescan with some code speedups & optimizations);
QUAGGA ZEBRA UPDATED TO VERSION 0.99.16 (with some code optimizations);
Added ericstools & ewget shared libraries (in place of those embedded on ddns_updater & ewget) (Eric Bishop @Gargoyle);
Added meta char conversion support to ddns_updater (Eric Bishop @Gargoyle);
Added freedns openssl https support to ddns_updater (Eric Bishop @Gargoyle);
Added tcp forwarding & tunnelling support to dropbear (to mantain retrocompatibility with previous version);
Added adjust kernel time skew support to ntpd;
Added des-ede3-cfb1 & des-ede3-cfb8 ciphers support to vpn (192 bit);
Added TR069 udhcp support on V4/N2000;
Added command manage https getkey instance (possibility of printing the stored pem key);
Added command vpn savekey instance (possibility of saving an externally generated vpn secret key);
Added command vpn getkey instance (possibility of printing the stored vpn secret key);
Added full meta char parsing support to cgi;
Added reverse iso char parsing support to cgi (possibility of inserting special chars on form field editing);
Added nvram settings show & statistics on diagnostic section;
Added loaded kernel modules show list on diagnostic section;
Added vpn secret key text area on vpn webpage section (with key read/post functionality);
Added advanced adsl settings & firewall spi webpage french translations (lucky);
Fixed bug on ddns_updater (password chopped at first @ char encountered on auth string providers) (Eric Bishop @Gargoyle);
Fixed bug on mini_httpd (false failure log event on https auth);
Fixed bug on nbtscan (segmentation fault on void parameters);
Fixed bug on syslogd (log event list clearup caused klogd termination);
Fixed bug on ddns_updater section (| char field separator unusable on ddns settings);
Fixed bug on ddns_updater edit section (field chopped at first quote char encountered);
Fixed bug on snmp section (setting chopped at first quote char encountered on webpage form fields);
Fixed bug on snmp section (meta chars escaped within quotes);
Fixed bug on vpn section (proto tcp option required client/server distinction);
Fixed bug on libdgteam wifischedule (wrong sequential day schedule fetch);
Fixed bug on libdgteam wifischedule (wrong checkout on sequential time interval);
Fixed bug on rc udhcpd instance (udhcp client ip assignement & lease failed on auto udhcpc ipoa connection mode);
Fixed bug on command vpn keytest instance (test not possible if ssl disabled);
Fixed bug on cgi (& query char unproperly parsed);
Fixed bug on cgi wansettings page (unassigned dmz ip fields not updated on post);
Fixed bug on firewall disable im ports instance (unappropriate url string filter applied);
Fixed bug on advanced dhcp settings & custom setup ita/fre/deu webpage sections (bad javascript links);
Removed javascript top close from logout webpage (iso violation: scripts cannot close webpages not open by scripts);
Enlarged https pemkey textbox area on access mode setup webpage for better visualization;
Ddns settings must be filled again due to array field structure change (| char separator replaced by unwrittable one);
Code-cleanup on libdgteam.so, command, cgi, rc improving speed & reducing code size & memory usage.
 
Im going to update mine tonight from 1007 to 1014, hopefully this will resolve my remote access issue but cant see anything mentioning this on the change log.

Maybe time to sign up to the DGTeam forums I think
 
For anyone interested, the move from 1007 > 1014 sorted out my remote access bug, I can now access the router over its WAN IP using HTTP or HTTPS.
 
I've just received a DG834GT, working fine with the firmware it came with. The problem started when I upgraded to DGTeam.

I just get flashing lights on the router and can't connect to it. I've tried using NFTP and the Recovery Utility (which doesn't work properly on W7) multiple times without luck. What can I do? Hope the router hasn't been killed by this firmware....

Thanks
 
Azuse05 said:
Either locate/obtain a pc running xp x86 (and blame netgear for never updating the recovery utility - it's almost like they want you to buy a second router rather than fixing your last one..) or grab a usb pen drive and follow no. 3 http://dgteam.ilbello.com/index.php?pid=16

Oh and remember, only flash using ie :)
Click to expand...

I've tried number 3 but everytime i get a magic hardware header error and it lets me continue by pressing ENTER. Then it says it was successful within a second (seems too quick) but the router is still not working.
 
Lethal` said:
I've tried number 3 but everytime i get a magic hardware header error and it lets me continue by pressing ENTER. Then it says it was successful within a second (seems too quick) but the router is still not working.
Click to expand...

I've managed to fix it now by compiling a modified version of NFTP. It's now running the latest official netgear firmware. I'm not sure whether to bother trying to install the DGTEAM firmware via NFTP or Recovery Utility now, as it took so long to fix.
 
Flashed mine using the web interface on the router itself from the latest Netgear version with no problems on W7 64bit
 
Lethal` said:
I've managed to fix it now by compiling a modified version of NFTP. It's now running the latest official netgear firmware. I'm not sure whether to bother trying to install the DGTEAM firmware via NFTP or Recovery Utility now, as it took so long to fix.
Click to expand...

I never bothered using their recovery utility app, was useless, I only have Windows server 2003 to use, no XP machines. However updating to latest DGTeam firmware through my routers WebUI worked no problems at all both on Server 2003 and the most recent update was done using Windows 7 Ultimate x64
 
i've got a netgear DG834N - and their firmware pack has two options, but they've helpfully neglected to include any sort of documentation at all. :rolleyes:

so, i go to their forums to read their thread about the 834N firmware and i need to register to read it. fine, so i go to register and they need me to answer these two questions to register: :rolleyes:

Is dg834gv2 ar7 chipset:

and

Do netgear routers have fan:

i mean, those don't even make SENSE! :mad:

<edit>
refreshed and finally got a pair of answerable questions and they've disabled registration! :RAAAAAAGE:
 
Last edited:
I had a question about does some N series device have duel something, I answered Yes as a guess, my other question was what is DGTeam, I answered "Firmware"

Both were right, I was in :)
 
Ozymandias said:
I've just set this up (was using ms VPN from WHS).

Config with defaults on the router VPN page.
Enable SSL support
Generate key
Save the key

On the client (mine is Win7)
Download and install openvpn-2.1.1-install.exe from
http://openvpn.net/index.php/open-source/downloads.html

This includes the GUI

Copy your openvpn.key you saved earlier into \program files\openvpn\config

Create a text file called netger.ovpn with

dev tap
proto udp
remote YOUR-IP-HERE 1194
resolv-retry infinite
nobind
persist-key
persist-tun
mute-replay-warnings
secret openvpn.key
cipher DES-EDE3-CBC
comp-lzo
verb 3

Start OpenVPN GUI in admin mode
Double click on tray icon and it should connect
Click to expand...

I keep getting "Options error: Unrecognized option or missing parameter(s) in netger.ovpn:3:" when i try and connect, im assuming the key goes in the same config folder?

I believe the "3" is related to line 3 which is my ip address + port, both of which are correct so I'm a bit confused.
 
Last edited:
As expected, flawless flash using IE, but then I've never managed to brick a router *touches wood*

Now all that's needed is convincing BE to enable PhyR on the network :(
 
So quite often in the evenings I notice my SNR goes down to about 4-5dB. Is this something the router should sort or is it related to my line/ISP?
 
You must log in or register to reply here.
Back
Top Bottom