There is new firmware out and I'm going to test! Hopefully someone will be kind enough to help me get access to the DGTeam forum. Well I have just waisted 1 hour of my day signing up..
Finally signed up but it won't let me login from work or home. The joys. Little bit more info on the different file for anyone reading this thread. I have enabled phyre on o and all seems stable so far in the UK. HPsauce Helpful Kitizen Posts: SMF 2. Support this site. Rate your ISP. Neither Netgear nor DGTeam will support these firmwares.
I will aim to provide "best effort" support. This makes it possible to tell whether the DHCP lease is being renewed rather than a new lease being obtained. Restarting the firewall certainly looks to be the cause of the brief network outage. The scripts don't update the default route if it hasn't changed since removing and replacing the default route will cause a tiny WAN outage. Some models reject any MAC address which doesn't start "", some other models reject any MAC address of the form x1:xx:xx:xx:xx:xx or 1x:xx:xx:xx:xx:xx.
Email me for details of automating installation of the key file and poisoning the password file. DGTeam were Italians. I've been using my firmware images on my DGGT since the morning of 9th July , and it's working fine. Feedback welcome. It appears that Netgear's own firmwares and the original DGTeam firmwares all do an internal restart when the DHCP client's lease is renewed, which I think is the wrong thing to do. I don't have a DG G v4, but I have created new images for that model. I've received three reports from BE members that this firmware is working OK for them on the new network, and further report from another BE member that the firmware has fixed the previous DGTeam DHCP client issue on the old network, but more reports are welcome - so if you try it please let me know whether or not it works for you.
I've received a couple of reports from BE members that this firmware is working OK for them on the new network, but more reports are welcome. I don't have a DGN, and I initially had a spot of bother with the DGN because my tools to unpack the squashfs filesystem didn't work properly with this model - the block size is different from that used in the DG models, and large files get corrupted when being unpacked. I've tried rebuilding the DGTeam firmware for the DGN with no changes but so far I've only produced a build which bricks the router :- fortunately the firmware recovery software unbricks it.
If I manage to rebuild the DGTeam firmware, then I'll be able to build a modified version with my changes. You can use this to replace the DHCP client support scripts with modified versions from my web site. Of course, if you've done this modification while the ADSL is already up then you'll see no change: you'll have to telnet to the DGN and enter the above commands manually I know there's an "Execute Script" button, but I've not had much luck with it - or reboot the router, or unplug the router from the phone line for a short while.
These models the v1 and v2 take the same firmware don't have later DGTeam firmware available, and so don't suffer from the change of DHCP client firmware. However they have the same DHCP support scripts, and so exhibit the brief network outage - which this build fixes.
As these models have slower CPUs than later models, the brief network outage might be slightly longer - and thus more noticeable. I was asked to build a modified firmware for this model, but I've not heard back from that user oh, perhaps he no longer has a working router So I have candidate firmware but it's completely untested, so I won't provide a link to it just yet.
0コメント