I installed a new Netgear WGR614v6 wireless router in my home. Boy, they sure do dumb these things down! I'm not happy with the utter lack of flexibility in its configuration.
Lacking:
- authenticated SMTP for sending log files
- NTP host/IP setting - In the manual, they say they use a variety of time servers. I looked at the binary config file; in that, there's a single IP for NTP. Liars.
- can't edit numerous settings through the web interface. Nor can you edit the exported config file. The config file has some sort of CRC signing in it, as I can't get it to accept it as a "restore from backup" after I've edited the config file with a hex-editor. This is a major drawback, making this router a royal pain for users who want more control.
- absolutely no configuration of the SPI firewall. It's either on or off.
- no configuration of what gets logged. Note that DHCP events do not get logged. I see this as a major security flaw. It means that I can't keep track of who is joining the network. I guess that limits my legal liability. "Sorry CIA/FBI/Homeland Security, I did my best to keep logs of user activity; go complain to Netgear."
Cool stuff:
- I do like the log email function, although I ran into problems w/ rules my ISP has for SMTP. This shouldn't be a problem for 99% of the other folks. Of course it's a pointless feature, since the logging on this model is so crippled that's it's utterly useless!
- DynDNS (and others) automatic updating. No need to run an updater on your PC! :) (but no value to me at this time)
I set up the wireless router so it broadcasts its SSID. I turned off WEP, so anyone can join. Of course, there needs to be some security.
At this time I'm not giving broadband access to the internet. The wireless just gives access to the LAN and anyone else on the wireless. So if files are shared, that's the users' business. The router's subnet is isolated so it doesn't touch the internet. There is a secure proxy on one machine so my PDA can still get on the inernet. I installed bind so I could serve my own DNS for the WAN subnet. Also, if anyone tried to go to google.com, they get automatically redirected to a web page that explains they are part of a free high-speed WAN that doesn't connect to the internet. It's all pretty cool, and quite transparent to the users.
Why is the lack of NTP (network time protocol) setting in the router a problem? Since the router isn't bridged to connect to the internet, it doesn't know what time it is. (And there isn't even a way to manually set the time!) If Netgear had smartly used hostname(s) for their NTP server list, I wouldn't have a problem. My DNS server would redirect that to my server on the WAN and I could then use a port forwarding tool to direct it to whatever time server on the internet *I* want to use. Unfortunately, I never saw any activity on the webserver's NTP port. I finally tracked down from an exported configuration file that there is a single IP saved for NTP use. The router's manual indicates that a list of nameservers are used. It lies. Since it is using an IP, it's just getting a "no route to host" type of error, as it isn't being redirected by my local DNS.
It sure would be nice if Netgear added a lot more settings options to future WGR616v6 firmware.