Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Schmye Bubbula]

Yeah, I think I need to return the refurb DIR-655/RE for a brand new one. Amazon says I have until Jan 31, 2013 to make a return. Since my last post, I've discovered yet another anomaly: I reserved IP addresses in Setup > Network Settings > Add DHCP Reservation, but if one of my clients (my iPod touch) is turned-off when rebooting the DIR-655, it doesn't honor my reservation and assigns my Roku box the first unused IP address of my iPod touch. That's not normal, is it? Shouldn't it have skipped the turned-off device's address and still assigned my Roku the higher address I reserved? If so, then that clinches it — I've got a bad unit.

[FurryNutz]

Ya, lets get that back to Amazon and get you into something NEW.
Make sure you let Amazon know that this unit NEEDS to go directly back to DLink for Repairs.

Let us know what you get.

[Schmye Bubbula]

Well, I contacted Amazon yesterday and linked them to this thread for the details of what's wrong with my unit, and they promptly sent me a replacement — overnight shipping without even asking, to boot — and I just set it up.

I know that you strongly suggested getting a new one, but I'm unemployed and it would be a burden to shell out more, so I just let them exchange it for another refurb, and we'll see how that goes. (I very well may end-up going with a new one before this is all over.)

This one came with firmware 2.04, so it was a little newer than my first one with 2.00. I promptly updated to 2.07 with the proper procedure described in my earlier post. Is my hardware version at B1 the latest & greatest with the currently still-live shipping DIR-655?

– So far I haven't had any trouble with the WLAN LED.
– But the Internet LED still stays solid blue like my first box, whereas it blinked under firmware 2.00 on my first box when the corresponding light on my cable modem blinked, and the user manual says it's supposed to. You said that your recollection is that yours blinks; are you sure? If they're going to change this kind of thing, they ought to include it among the other changes in the firmware revision list, especially for something that departs from what the user manual says. (But I actually like it better this way.)
– The DNS reservations work now, but I think I've picked-up on a pattern not mentioned in the documentation. After setting DNS reservations and rebooting the router, it apparently tries to preserve the existing IP address for a given device notwithstanding the reservation. Only after the client device itself is rebooted is the reservation honored. Does that sound right to you?
– Something new I don't understand: I had to set two separate Network Filters for my computer reflecting its two separate MAC addresses for hard-wired Ethernet and AirPort. Ditto for DNS Reservations: a separate IP address for the different Ethernet and Wi-Fi MAC addresses. But I didn't have to do those two settings with two separate MAC addresses last time. Both just worked with single settings. I don't get it.

Two more things I don't understand:
– Why do I have to "fool" my ISP into thinking the router's MAC address is the same as my computer's by first plugging my computer directly into the cable modem and acquiring a DHCP IP address, before quickly swapping the router into the cable modem and clicking the "Clone Your PC's MAC Address" button in the Internet Setup? I don't have to do that with my old AirPort Extreme base station; "It Just Works™."
– To get Wi-Fi working (I kept getting "invalid password" in my client), why do I have to go into the router's:
Setup > Wireless Settings > Wireless Network Setup Wizard
...and click the "Wireless Connection Setup Wizard" button, then choose "Manually assign a network key" (since I otherwise configure manually)? My question is, why doesn't this setting appear among the manual settings? It's confusing because my natural expectation is that if I choose not to use a wizard, then all settings should be among the manual settings.

[FurryNutz]

Well, I contacted Amazon yesterday and linked them to this thread for the details of what's wrong with my unit, and they promptly sent me a replacement — overnight shipping without even asking, to boot — and I just set it up. NICE!

I know that you strongly suggested getting a new one, but I'm unemployed and it would be a burden to shell out more, so I just let them exchange it for another refurb, and we'll see how that goes. (I very well may end-up going with a new one before this is all over.)

This one came with firmware 2.04, so it was a little newer than my first one with 2.00. I promptly updated to 2.07 with the proper procedure described in my earlier post. Is my hardware version at B1 the latest & greatest with the currently still-live shipping DIR-655?  It's highly recommended that people use what is loaded on the router before upgrading. Routers usally work ot of the box and what they come loaded with. It's not always necessary to load the latest and greatest as they might introduce other problems or not fix anything at all. I always recommend that people try the router first for a while and see how it works before concidering updating. The most recent version is v2.10 however we believe there is a bug in it dealing with Guest Zone. So I don't recommend anyone use it at this time.

– So far I haven't had any trouble with the WLAN LED.
– But the Internet LED still stays solid blue like my first box, whereas it blinked under firmware 2.00 on my first box when the corresponding light on my cable modem blinked, and the user manual says it's supposed to. You said that your recollection is that yours blinks; are you sure? If they're going to change this kind of thing, they ought to include it among the other changes in the firmware revision list, especially for something that departs from what the user manual says. (But I actually like it better this way.) I'll re-check my routers behavior this weekend and report back. I downgraded to to the v2.10 issue to v2.07 so I an confirm what I see for you.

– The DNS reservations work now, but I think I've picked-up on a pattern not mentioned in the documentation. After setting DNS reservations and rebooting the router, it apparently tries to preserve the existing IP address for a given device notwithstanding the reservation. Only after the client device itself is rebooted is the reservation honored. Does that sound right to you? Are you talking about DHCP reservations? DNS is completely different.

– Something new I don't understand: I had to set two separate Network Filters for my computer reflecting its two separate MAC addresses for hard-wired Ethernet and AirPort. Ditto for DNS Reservations: a separate IP address for the different Ethernet and Wi-Fi MAC addresses. But I didn't have to do those two settings with two separate MAC addresses last time. Both just worked with single settings. I don't get it. Each actual network device connection will have separate MAC addresses. On my Mac Book Pro, I have LAN and WiFi, each one has a different MAC address. When I do a IP Reservation, I have to reserve for 2 separate IPs for each MAC address. Thus each rule or filter you use, can or might be used for each MAC address entry. Not sure how your devices are configured. Also could have been a issue that you though was correct behavior with the old 655 which wasn't probably working correctly so now that you have a good working one, the behavior may have changed and it just looks different.

Two more things I don't understand:
– Why do I have to "fool" my ISP into thinking the router's MAC address is the same as my computer's by first plugging my computer directly into the cable modem and acquiring a DHCP IP address, before quickly swapping the router into the cable modem and clicking the "Clone Your PC's MAC Address" button in the Internet Setup? I don't have to do that with my old AirPort Extreme base station; "It Just Works™."Some ISP Call for MAC assignments and recognition. Usally most don't and only are concerned with the ISP modem connection and it's MAC address. Everything else behind the modem they usually don't care about. I would ask your ISP if there is a MAC Clone requirement for there ISP system or should the ISP modem and external router be all DHCP. Mine is and don't need to Mac Clone. I did experience this at my fathers place in KY with his ISP.

– To get Wi-Fi working (I kept getting "invalid password" in my client), why do I have to go into the router's:
Setup > Wireless Settings > Wireless Network Setup Wizard
...and click the "Wireless Connection Setup Wizard" button, then choose "Manually assign a network key" (since I otherwise configure manually)? My question is, why doesn't this setting appear among the manual settings? It's confusing because my natural expectation is that if I choose not to use a wizard, then all settings should be among the manual settings. I only use the manual settings when setting up a router. Usually the wizard will work and sets up the basic funtion and you should be able to give a new SSID name and PW. I always use the following for manual settings. Try single mode Mixed G and N?
Channel Width set for Auto 20/40Mhz or try 20Mhz only.
Setting a manual channel to a open or unused channel. 1, 6 or 11. 11 for single mode N if the channel is clear.
Preferred security is WPA-Personal. WPA2/AES Only. Some WiFi adapters don't support AES, so you might want to try TPIK only or Auto.

[Schmye Bubbula]

> Are you talking about DHCP reservations?
> DNS is completely different.

Yepper, this Dr. Malaprop meant DHCP reservations. (I know the difference — brain fart!) So do you think I'm right that DHCP Reservations are honored only when the client is rebooted, but when just the router is rebooted, it will preferentially try to preserve the existing IP address of the client device notwithstanding the reservation (until such time as the client is rebooted)? Or do you think this second refurb DIR-655 is hosed, too?

Edit: I just made a change in DHCP Reservations to my MacBook Pro, then rebooted the router without rebooting the MacBook Pro, and the MacBook Pro's IP address got changed, honoring the reservation. Go figure! ... You know what? I think there's something funky with my Roku box's DHCP client, 'cause it's whose IP address didn't change when changing its reservation and rebooting only the router, but only after rebooting the Roku.... Yeah, that's the ticket.... Never mind!


Glad I'm not going crazy, and you also have to set two separate rules or filters with separate IP addresses, reflecting the two separate MAC addresses of wired & wireless. Now I'm fuzzy about what I thought I was doing with the first DIR-655, so let's just forget it.

I was just complaining that there was something in the wizard that wasn't in the manual setup. Oh well, live and learn. (Still seems just wrong!)

Hey, a big thanks and tip o' the hat for all your generous assistance, FurryNutz!

[FurryNutz]

Ya once you make the reservations on the router, at that point you can make the IP number anything. Once it's saved it's recommended after the reboot of the router that devices also get rebooted so the changes take effect.

I think you just need some time with this new one and see how it work out for you.

Maybe someone can review the router settings with you at a later date using Teamviewer and make sure the router is set up well.

Enjoy.

[FurryNutz]

FYI, my WAN LED is bllinkin on my 655. Mine is connected to a Motorola SB 6120 Cable modem. WIFI Blinks too.

[Schmye Bubbula]

Curious that your WLAN LED blinks and mine doesn't. Like I said, I actually like it better that way, but I wonder if some other setting I've made could have caused that. You will recall from my first post that my first unit's blinked, too, until right after I added some MAC addresses to my Network Filter (possibly sheer coincidence), and making your recommended update from 2.00 to 2.07 didn't help, and now my second unit is the same way, both under 2.04 and 2.07.

You mentioned having someone look at my settings with Teamviewer — would my saved config do?

[FurryNutz]

Please do not post your config file info in the forums. Has some private information. Review of the config file will not help here.

If your interested, lets review your router settings with you using Teamviewer.

[Schmye Bubbula]

Well, blow me down! Hey, FurryNutz, guess what? Just now I changed two settings according to this post: "Read this if you wanna break your DIR-655. [BUT DON'T JUST YET!]," and after reboot, my WAN LED started blinking again! (called "Internet LED" in the user manual)

The only two changes I made among all the post called for — that I didn't already have set his way — were these:

6. Advanced > QOS Engine > Disable or uncheck Traffic Shaping
7. Advanced > Firewall > UDP Endpoint Filtering = Endpoint Independant /
                                      TCP Endpoint Filtering = Endpoint Independant

I know for sure that I never messed with those settings during the whole time of this thread, with either of the two DIR-655s I went through, and presumably until now the two reflected the stock factory settings (QOS Traffic Shaping on, UDP & TCP Endpoint Filtering both set to either Address Restricted or Port And Address Restricted — I've already forgotten which), so I wonder which of them got my WAN LED flashing again. But it still doesn't make sense because, like I said, I never messed with them before.

What do you make of this? After all we've been through during this thread, I'm really curious about reconciling these curiosities.

– –
Edit, Fri, Dec 21, 2012, 11:24AM EST:
Woops, I said "WLAN LED"; I meant "WAN LED" (Internet LED). I have changed it in the above text. This thread started with the WLAN LED not blinking, but we got it fixed in Reply #6, whereupon the WAN LED in turn stopped blinking at the same time, and the rest of this thread has concerned the WAN LED.  Sorry for the confusion.

[Schmye Bubbula]

You know what? I'm starting to think that maybe these two LEDs that stopped blinking has nothing to do with the particular settings that got changed just at the same time as the blinking stopped after the accompanying requisite reboot.

To recap, the settings changes involved that seemed to trigger the LED blinking cessations were:
Advanced > Network Filter
Advanced > QOS Engine > Traffic Shaping
Advanced > Firewall > UDP & TCP Endpoint Filtering

Perhaps it was just a coincidence. Maybe there has been a latent, intermittent bug all along through at least firmware 2.07 that randomly causes those LEDs' blinking/solid states to toggle when the whole configuration gets saved, not the settings changes per se. Recall that even a factory restore didn't help. (But if this hypothesis is true, then a sequence of successive save configs ought to eventually toggle the blinking status.)

What do you think? Have you encountered similar anomalies with the LEDs elsewhere? Wanna' run this up the flagpole with the D-Link people?

[FurryNutz]

The internet LED should blink regardless of any user changes on the router. It should blink regarless and only if it gets a proper internet connection from the ISP modem or services.

You might want to phone contact DLink support, level 2 or higher and ask about this behavior. Keep us posted on how it goes.