Those of you who’re fairly close know that I’ve been having network problems back at the ranch lately.
A few months back, I was doing a firmware update to my router and it bricked. And, since I’d had it over a year and a half, tech support was NOT going to RMA it. Especially since the device was no longer in production.
So one fairly-well-working 808-HV down the tubes.
So here I was, looking for a router with more than 5 ports again.
Other than the bricking, which I put down to unfortunate happenstance, I’d been fairly happy with D-Link. And since most of the other high-end consumer/prosumer router devices out there usually maxed at 5 ports (and I needed more), I would either have to buy D-Link again, upgrade to a low-end pro router, or go with a router and a second switch.
My setup isn’t so tough that I really NEED a pro-grade router. Plus plunking down several hundred bucks for one isn’t something I can easily justify.
I also would like to avoid sprouting network devices all over the place. Adding a separate router/switch combo adds another possible point of failure to my network and also increases network latency.
So I settled on the DIR-130. Nice little router. 8 ports. Pretty much all the features I had before.
Here, my troubles began.
I was able to duplicate my original setup in relatively short order. And everything was nice. For a while.
Then I noted that the router would periodically “lose” the web interface. The device still functioned, it still router, it still did DHCP and port-forwarding. But the web interface simply stopped functioning (or even being accessible). The only way to get the management interface back was to bounce (power-cycle) the router. A MAJOR pain in the cojones, but not a complete show-stopper. Additionally, I’d seen complaints about this around the web, and the next firmware update was supposed to fix this. Being a somewhat happy D-Link camper, I chose to wait.
Fast forward to September. The new firmware update was out as of August. So I snagged it and, being somewhat leery since I’d bricked my last device this way, flashed the router.
Everything came back up nicely. No headaches. Nothing. Success!
Ha. Ha. Ha.
So, thinking everything was great, I began browsing the interface, looking for updates/changes, making sure my settings were all preserved, etc. Then next thing I know, my network just “goes away”.
Just to be on the safe side, I reboot every device on the network. Then I notice I’m not pulling DHCP. Nor is the LAN working, even with static IP assignments. Worst, I can’t access the router!
One emergency call to D-Link later, and I was faced with yet ANOTHER bricked router.
So I drop the $150 for expedited cross-shipping. A full week goes by and the new device arrives. And guess what, the device isn’t running properly, and the default logon in the manual isn’t working. Unfortunately, with this device I’m only eligible for 9-5 weekday tech support to make sure the device runs, and it’s Friday night 8PM.
So I had the privilege of waiting an entire fscking weekend to get my stuff working. And by the time I got on with D-Link support, I was swearing up and down that if they didn’t get it working, they were getting the RMA unit back in the mail.
Sure enough, the default logon was different from what was in the manual. So I was in. I set the router up on the 1.0 firmware (why the fuck are they shipping new units with the old firmware anyhow?), then held my breath and flashed to the 1.10. I browsed around in the interface for a bit, then pushed my config into the router.
And problems started… again.
Certain ports (ssh, FTP, web) weren’t functioning properly. I had portions of the interface that showed this data, but the sections were grayed out, and duplicating them in “live” sections of the interface didn’t help.
So I bit the bullet and restored the router to default and got ready to manually config.
My setup isn’t much.
Approximately 5 DHCP reservations. Three computers, one NAS device, and one Wireless AP. This way, when I remote in, I don’t have to hunt all over my network for a random address. No problems right? WRONG!
First off, DHCP reservation is FUCKED UP on this device. Initially I’d reset the DHCP assignments to be between 2 and 150 (150 being the default upper limit). So when I tried to assign my first workstation to *.2, I get an error stating “2 must be within the DHCP range”.
Back on the phone with D-Link IMMEDIATELY.
For some reason, the interaction of DHCP and address reservation isn’t working properly. I have to shrink the pool of DHCP addresses down to within 50 addresses (the maximum number of reservations on this device is 50) before it works properly. And the imbecile on the other end of the phone hangs up on me thinking that the problem is solved. It isn’t!
Random addresses within that range STILL don’t auto-assign! I get the “# must be within the DHCP range” bullshit. Literally, I can assign IP addresses 2-5 fine. But then, DHCP’s first address assignment after that is 23! And doing reservation of an IP for anything between 6 and 22 fails!
Yes, I could go ahead and statically assign addresses to my standard network node but why the fuck should I have to? This is what I bought this device for! Now I need to call in to them yet AGAIN. Waste MORE time. All for something that should work out of the box.
Worse still, they have yet to credit the $150 back to my bank account.
Needless to say, in the future, I’m not putting D-Link on my short list of network equipment providers.
Here’s at least some of the systems I own…
I dunno. Maybe I’m not feeling well or something. But yep. Another update.
Took a cruise out to Phil’s casa last night and came back loaded for bear (or at least a really pisssed chihuahua) with computer hardware.
These are three of the four machines I acquired. Two are dual Celeron 500 (don’t laugh, it’s not like I’m gonna game on the damn things). The third is a dual P3 800 system.
System 4 is a decomissioned Dell 2400. Dual P3 1Ghz with 2 gigs of RAM and six 9.1 GB SCSI drives. I currently have Ubuntu Linux installed on it and it’s in the process of updating.