Skip to main content

Netgear D6300 Review

After my poor little TPlink Router bit the dust with a recent power fluctuation I was keen to get something with a solid WiFi capability. The TPlink router I was using didn't have the greatest coverage around the house, and certainly not outside the house, and with the recent installation of a Chromecast I was keen to find something with a bit more zing. Also, due to my dodgy cabling set up, I have half my machines on one side of the house, and the other half on the other side. The cabling between the two goes through the router and I wanted a gigabit link between the two halves.

So a router with 5GHz wireless and gigabit networking? My local nerd supplier handed over the $399 Netgear D6300 and told me it was the best he had. He noted my sceptical look, but assured me that it was good to go. OK I'll have a crack at it and see how it goes.

It took about 45 minutes to configure it - I've got a fairly complex network with a lot of crap all over the place, all sorts of forwards and Dynamic DNS configured. I also have a large number of static DHCP entries - nightmare. Once I got it all across, plugged in and set up and away we went. I quite like the Netgear method of showing what's happening on the network. That's one of the very few things I do like about this router.

Here are the other things:

  • the wireless is good
  • throughput on the gigabit network is very high, so that's good
  • Dynamic DNS works out of the box and has some nice reporting
  • it's not a bad looking bit of gear:

OK so here are the things that suck about this router:
  • the interface is slow. I tested it under:
    • Safari
    • Chrome
    • IE
      • and it was pish under all of them. Slow to refresh and slow to respond.
  • update stopped part way through and I had to restart it - thought I'd bricked the thing
  • updates to DHCP require a reboot of the damn router! What the hell?! All I'm doing is changing a MAC address or an IP and the whole thing has to reboot to update it. This makes me very unhappy and annoyed.
  • it wouldn't initially talk to one side of the network - I ended up having to install a gigabit switch to get the thing to work properly. This isn't optimal, although it does take the network link between the network sides away from the router for when it restarts every time I perform a basic function. 
All in all, for the price, I'm a bit ambivalent towards the D6300. My dirty old TPlink, with no frills, worked pretty well and I wasn't hating on it too much when it died. Now that it is gone, this Netgear has a bit to do before I'm impressed. We will see how it goes over time, however I wouldn't rush out to buy this one.


  1. i was thinking about buying a Netgear R6300 or ASUS RT-AC66U 802.11ac, and i have a few questions, first off, if i buy this overseas (I live in Australia) will any Netgear Power cable/adapter work with this, we have a different sockets over here in Australia (Australian standard AS 3112, 240V) will any Netgear power adapter work with the model? and second of all i was wondering what you think of the two? Oh and will it give me a new IPv4 adress? And how to configure vpn on router?

  2. Hi Willie. I can't answer the questions with regards to the ASUS RT router. Most of the adaptors you buy with these routers will be supply the same power to the router - it's just the power point end that changes. No, any Netgear power adaptor will not work with this model - it has a specific volt / amp requirement.
    I haven't really played with the ASUS so I can't comment on it, but I will say that the Netgear is doing its job well at the moment.
    Regarding the IPv4 address - are you referring to internal or external? Internal is configurable and external is up to your ISP. What sort of VPN are you talking about?
    Thanks for taking the time to write.


Post a Comment

Popular posts from this blog

Plone - the open source Content Management System - a review

One of my clients, a non-profit, has a lot of files on it's clients. They need a way to digitally store these files, securely and with availability for certain people. They also need these files to expire and be deleted after a given length of time - usually about 7 years. These were the parameters I was given to search for a Document Management System (DMS) or more commonly a Content Management System (CMS). There are quite a lot of them, but most are designed for front facing information delivery - that is, to write something, put it up for review, have it reviewed and then published. We do not want this data published ever - and some CMS's make that a bit tricky to manage. So at the end of the day, I looked into several CMS systems that looked like they could be useful. The first one to be reviewed was OpenKM ( ). It looked OK, was open source which is preferable and seemed to have solid security and publishing options. Backing up the database and upgradin

Musings on System Administration

I was reading an article discussing forensic preparation for computer systems. Some of the stuff in there I knew the general theory of, but not the specifics of how to perform. As I thought about it, it occurred to me that Systems Administration is such a vast field. There is no way I can know all of this stuff. I made a list of the software and operating systems I currently manage. They include: - Windows Server 2003, Standard and Enterprise - Exchange 2003 - Windows XP - Windows Vista - Windows 2000 - Ubuntu Linux - OpenSuSE Linux - Mac OSX (10.3 and 10.4) - Solaris 8 - SQL 2005 - Various specialised software for the transport industry I have specific knowledge on some of this, broad knowledge on all of it, and always think "There's so much I *don't* know". It gets a bit down heartening sometimes. For one thing - I have no clue about SQL 2005 and I need to make it work with another bit of software. All complicated and nothing straightforward. Irritating doesn&

Traffic Monitoring using Ubuntu Linux, ntop, iftop and bridging

This is an update of an older post, as the utilities change, so has this concept of a cheap network spike - I use it to troubleshoot network issues, usually between a router and the network to understand what traffic is going where. The concept involves a transparent bridge between two network interface cards, and then looking at that traffic with a variety of tools to determine network traffic specifics. Most recently I used one to determine if a 4MB SDSL connection was saturated or not. It turned out the router was incorrectly configured and the connection had a maximum usage under 100Kb/s (!) At $1600 / month it's probably important to get this right - especially when the client was considering upgrading to a faster (and more expensive) link based on their DSL provider's advice. Hardware requirements: I'm using an old Dell Vostro desktop PC with a dual gigabit NIC in it - low profile and fits into the box nicely. Added a bit of extra RAM and a decent disk and that&