Print

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

[lindros2]

I thought I was losing my mind - thank you for posting.

[FurryNutz]

For anyone interested in trying new beta:
v2.08NAB01 Beta

[Mark_KF8RV]

I'll be interested in that release when it becomes non-beta, i.e., it becomes official. 

I'll stick with 2.00NA until I know for sure that version 2.08 is tried, true, tested, bug-free, and perfect in every way. 

I demand perfection for my trusty DIR-655 router.

Mark KF8RV.

[FurryNutz]

I'm sure others will give it a go and report back. 

[Mark_KF8RV]

I want the version to be rock solid having quality firmware that can be shipped with the product.   

The trusty DIR-655 requires the quality best firmware available without any exception.

Fireware bugs aren't acceptable.

I like D-Link and I don't want to switch to Linksys.

I hope that version 2.08 is good stuff.

Regards from Mark KF8RV.

[FurryNutz]

We get it. 

[sm00thpapa]

Furrynutz is there a release date for the 2.08NA? Sorry if this has been asked before. I just got back on this forum today after a 2 month layoff. I reverted back to 2.03NA as 2.07NA also gave me trouble with the shareport. My only gripe about this router is it seems slow wireless and wired. And the range is not what I expected from an N router. Plus it wont stay in 40GHZ mode and give me the 300Mbps speed. Just for today I went back to my tried and tested and proven WRT54G which has a significantly better wireless range and is actually faster wired go figure.

[FurryNutz]

I have no such knowledge or privey to any information on release dates. I'm currently testing v2.08 Beta now on my Rev B1. I've verified that Shareport is fixed with this version.

[sm00thpapa]

Thanks for the reply Furry. I think I'll stick with 2.03NA until 2.08NA becomes official.

[sm00thpapa]

Anyone know if the upcoming firmware gonna have a Channel Width 40 MHz only instead of the Auto 20/40 MHz?

[FurryNutz]

Stay away from the Beta 2.08, causing some odd behavior.
Auto 20/40 is the standard for DLink routers.

[FurryNutz]

I see for the DIR-655 Rev B that v2.07 has a date of 7/12/12 on the FTP site. I distinctly remember getting this version and testing it months ago. Release date on the web site the date is 2/29/12. I checked my file server and I got it back in March and the actual .bin file date is 1/14/12.  The one I see from 7/12 the .bin file is dated 3/5/12.

I wonder if they fixed SP and just over wrote the older .bin file dated 1/14/12.

1. Can someone interested in testing, download the v2.07 from the web and check to see if the Modified date on the .bin file reads 3/5/12 to verify? I just verified it and the date is 3/5/12 on the .bin file.

2. Load it and see if it works? Does it fix Shareport and does the router work normally? All network LEDs should not be constantly blinking either like we saw in beta v2.08.
http://forums.dlink.com/index.php?topic=48026.0

3. Does the IPv6 Route window still have the typographical errors?

I'll try this when I get home from work today. Let us know what you see.

[FurryNutz]

So I loaded v2.07 dated 3/5/12 and it seems pretty good. Shareport is working with my printer and I played for about 3 hours on XBL with 2.4Ghz 300Mb connection. Had a good time. Will work it some more.
There is still a misspelling under IPv6 Routing.  

I feel this is going to be a good version for those interested in using it.

Again, if your Rev B router is working well with whats currently loaded, then probably no need to upgrade.

Let us know what you experience with it.

[nicknml]

I'll have to load it and check to see if they fixed the ARP request issue.

UPDATE: The problem still exists.

I'm also still getting "/rootDesc.xml not found, responding ERROR 404 " in the log

[FurryNutz]

Do you see this after a factory reset  with only one PC and the syslog server going? I did notice that there was still activity on the LEDS however it seemed to settle out and go back to normal activity after a short period of time. I presume it might be due to all the devices I have connected and some were not powered off after I updated and just all the networking getting settled in and configured by the router. I didn't get a chance to check the sys log for any message.