I have the DGND3300 and the ethernet ports are indeed 10/100. I'd be rather amused to know exactly what the device does with Wireless-N traffic arriving at 270MBps since it can't go to the ethernet or DSL ports that fast, and if sending to another wireless device then they'd have to share the bandwidth and would be lucky to get 100MBps each.
There may also be some confusion over exactly what this device is. It is first and foremost an expensive plastic box with a large number of coloured LEDs most of which flicker a lot. You can disable the obnoxious centre ones by pressing the button but they come back on again with a reboot/power failure. As a bonus feature it is also a DSL modem and wireless router
It does save on the number of boxes, cables and power adapters. However be aware that the DSL is builtin as the external access - if you dropped DSL for a cable modem then there is no 'Internet' port on it - you would only be able to use it as an access point (ie no NAT, no firewall etc)
In the bad old days these kind of devices used to do a reboot on every settings change. Nowadays they don't but then you find some functionality doesn't work right until a reboot - always a fun problem to diagnose. This device suffers that exact problem with port forwarding (aka "services" in Netgear speak). However after that reboot everything has worked well and none of my services have been messed with (a nasty affliction I found on a Trendnet device).
You can't have services use a different external vs internal port. However you can run a uPNP client to setup and refresh mappings that do use different ports.
It does have denial of service and port scan detection. The latter works in my testing. I am somewhat suspicious of the DOS detection since it is a very fine line between lots of traffic and a DOS attack. Both are on or off together unfortunately.
The DHCP server is the usual basic thing. You can't set extra options such as PXE boot servers.
The device runs Linux and there is only one firmware currently available. If you add
setup.cgi?todo=debug to the URL then you can enable a debug mode which then lets you telnet in to a busybox shell.
Some stats:
- Linux kernel 2.6.21.5
- System Broadcom 6358 (MIPS derivative)
- 300 BogoMIPS (can't tell if processor is 150MHz or 300MHz)
- 32MB of RAM
- 8MB flash
- Broadcom 5325e switch
- Broadcom BCM4318 a/b/g and BCM4322 n wireless controllers
Using a Kill-a-Watt I measured power consumption as 7W with only 2.4GHz on and 8W with both 2.4 and 5GHz on.
The
PDF manual shows all the web interface screens.
