D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: Ru-Fi-Oh on November 11, 2009, 01:24:42 PM
-
http://forums.dlink.com/index.php?topic=9246.0
Post your feedback here regarding this firmware.
-
What is the reason the "restore from config" file rarely works?
So far not impressed... ???
i'll be back.
-
I set up one of these in the Beta section, you can lock it or merge it around if you wish.
-
I had just upgraded the beta firmware, so far I have seen less in wireless error. I am currently using auto channel and it is on 11/7 right now. I will be monitoring the router. All I can say for now, for it is so far so good. I just hope it stay like this forever and I am crossing my finger. I have all feautures enable at the moment except for securespot which I dont have an account with.
-
I set up one of these in the Beta section, you can lock it or merge it around if you wish.
And in plain English?
-
And in plain English?
There is another feedback thread that I started in the beta section. The mods can lock it or merge the two together if they wish to keep everything in one place. Merging a thread puts 2 threads together into one thread so all information can be in one thread.
-
I installed this version and restore the old config as advised in the thread, so far been so good. But it's only been two hours (needs more testing) and I don't use Shareport or HTTPS web interface, so these things are disabled.
I have a question regarding the new Counter column in the internet sessions page. What does it means and what good does it bring? The help page does not have this info.
-
after the upgrade and restore of configuration my internet would not work until I re-enabled DNS relay.
I had it set off in previous firmwares, but in this firmware under my PPPOE connection, I had not internet access, even though it showed the router had a wan ip, until i checked DNS relay.
So if you cannot uncheck dns relay, you might as well take off the option.
-
I wonder of the people having issues....How many are DSL and how many are cable?
-
I wonder of the people having issues....How many are DSL and how many are cable?
Verizon is serving my FIOS connection through pppoe, its not DSL
-
Verizon is serving my FIOS connection through pppoe, its not DSL
Yes, that is DSL ---> Point-to-Point Protocol over Ethernet (http://en.wikipedia.org/wiki/Point-to-Point_Protocol_over_Ethernet)
It is used mainly with DSL services where individual users connect to the DSL modem over Ethernet and in plain Metro Ethernet networks.
-
This bin has it's problems. If I de-select every option possible, it will work OK for varying lengths of time. Enabling QOS, DNS Relay or Sharepoint seprately or together, the router will recycle at least 5 times per day. I have not been able to isolate the problem, but I have eliminated most variables on the software side, ie, there isn't anything on my or any other computer that would/should cause this. I am a home user with little IT training, so complex testing is out of the question for me. I do have all D-Link nics and and adapters, with the exception of my son's XBOX and a few I-Pod touches.
It does seem a re-boot of the modem and router helps the problem of recycling for a while, but there seems to be no pattern what-so-ever. I have checked the logs every time this occurs and there really is no pattern there.
-
I have enable dns-relay for almost a day. So far the router is functioning without lock-up issue. If this stay like this and all I can say is you did solve the problem with lock-up issue. Can you please work on the wireless signal performance. I have tried position the antennas and the router but it was no help.
-
Hi All,
Color me curious.
Throughout firmware versions, up Firmware 1.21, one could always reflash the older firmware without problems.
The newer firmware brings problems and one can't go back.
Why can't one reflash the older versions, back to Version 1.21?
-
Yes, that is DSL ---> Point-to-Point Protocol over Ethernet (http://en.wikipedia.org/wiki/Point-to-Point_Protocol_over_Ethernet)
I have another location which verizon fios wan is disributed by DHCP, is that dsl as well?
-
I have another location which verizon fios wan is disributed by DHCP, is that dsl as well?
Did you read the article at the link I provided?
Like the part titled: How PPPoE fits in (http://en.wikipedia.org/wiki/Point-to-Point_Protocol_over_Ethernet#How_PPPoE_fits_in)
-
shareport beta client doen't work now? What new client do i need?
Later i reset my router and upload my config the router hangs, then i manually unplug my router and power it back on now shareport works again. Is this another bug?
-
The shareport that was included in this beta firmware:
ftp://ftp.dlink.com/Gateway/dir655/Beta/Firmware/dir655_fw_132b04NA_beta01.zip
-
Well, so much for DNS relay being fixed. This firmware forced me to re-enable the setting, and in less than 24 hours with some lite bittorrent use, this router has frozen, cannot access UI until I disconnect power.
I am going back to 1.32b04 with DNS relay off.
D-link has to give up already on fixing shareport, and concentrate of making this router stable without hangs.
There were plenty of happy d-link customers prior to this whole firmware fiasco from 1.31, the only thing I want is to go back to firmware 1.11, how hard is this to accomplish???
-
@edlivian: How fast is your upload/download and what is the settings of your torrent client # of connections, upload speed...
-
@edlivian: How fast is your upload/download and what is the settings of your torrent client # of connections, upload speed...
I have a verizon Fios 25 Upload / 15 download. I use Utorrent, max connection is set to 200, upload is set to 1.5MB/s
On firmware 1.11 I could have sustained 2.8MB/s download and 1.5MB/s upload for weeks, and no issues, and now with firmware 1.32B09 within 15 minutes the router hangs with DNS relay setting enabled (not able to turn it off, then I would have no internet).
I am going to stop praying for a fix and return this router this weekend to costco, and purchase a new DIR-655 with firmware 1.11
-
I have a verizon Fios 25 Upload / 15 download. I use Utorrent, max connection is set to 200, upload is set to 1.5MB/s
On firmware 1.11 I could have sustained 2.8MB/s download and 1.5MB/s upload for weeks, and no issues, and now with firmware 1.32B09 within 15 minutes the router hangs with DNS relay setting enabled (not able to turn it off, then I would have no internet).
I am going to stop praying for a fix and return this router this weekend to costco, and purchase a new DIR-655 with firmware 1.11
You should still have internet if your DNS relay is turned off. Did you enter in DNS addresses your self in the router?
Then you need to ipconfig /release then /renew your IP
-
shareport beta client doen't work now? What new client do i need?
Later i reset my router and upload my config the router hangs, then i manually unplug my router and power it back on now shareport works again. Is this another bug?
Which Shareport version are you using? The one from the forums or the one from the support site?
-
@edlivian: I see, my internet is not that fast so I can't test at your speed, but well it has been going for 1 and a half day for me with constantly torrent as I try to stress test it. The old 1.32NA final can go for 3 days for me, so I need more time to test though.
@Ru-Fi-Oh: What do the counter x/y in internet sessions page mean? I see y goes linearly but x does not.
-
In my Don Quixote-like quest to make this hunk of junk useful I flashed the new firmware and plugged into my network. I plugged the WAN port to my LAN just to give it a reasonable test and it promptly locked up 10 hours into almost no usage. ::)
Back into the junk drawer this goes.
-
I have a verizon Fios 25 Upload / 15 download. I use Utorrent, max connection is set to 200, upload is set to 1.5MB/s
On firmware 1.11 I could have sustained 2.8MB/s download and 1.5MB/s upload for weeks, and no issues, and now with firmware 1.32B09 within 15 minutes the router hangs with DNS relay setting enabled (not able to turn it off, then I would have no internet).
I am going to stop praying for a fix and return this router this weekend to costco, and purchase a new DIR-655 with firmware 1.11
I have found that in the past, settings such as DHT and PXE (and possibly others) can utilize more connections and therefore cause the router to have problems (however, I had seemingly different behaviour on different versions of the FW).
Most recently, on 1.32NA, I found that I had to map utorrent ports *manually*, rather than letting it use UPNP. I found that this, as a sideffect, cut down on the number of "blocked" entries in the log. And the result was, it stopped rebooting 10 times a day / locking up several times a day.
YMMV
-
I wasn't having lock up issues. I have been having the problem where many things on the advanced tab don't save. Or will save but then at some point reset to default (maybe the router was rebooting even though it wasn't showing this in the logs).
I upgraded to this beta and so far so good, granted its only been a day. But I don't recall the settings sticking for this long on any previous version of 1.3x firmware.
-
Which Shareport version are you using? The one from the forums or the one from the support site?
i used the shareport version what came with the 1.32 build 4 beta 1 version.
-
I have another location which verizon fios wan is disributed by DHCP, is that dsl as well?
DHCP and DSL are completely different things... xDSL is the infrastructure used by the ISP to deliver the WAN connection to your home, just like cable is one of those. Or satellite. DHCP is the mechanism that is used to get you an IP through that infrastructure.
-
DHCP and DSL are completely different things... xDSL is the infrastructure used by the ISP to deliver the WAN connection to your home, just like cable is one of those. Or satellite. DHCP is the mechanism that is used to get you an IP through that infrastructure.
He was being sarcastic heh
-
Router has been up for 3 Day 8 Hour, with constant torrenting (trying to stress it). If it continues like this for another 2 days, I say the DNS Relay issue is fixed for me.
YMMV.
-
Same here! This is the most reliable 1.32 release I've tried so far. 2 days of torrenting without ANY issues.
-
Now I don't have any problems with my router. Big thanks to firmware developers :)
-
uberlag kicked in after 1day and 12 hours uptime. Routers webpage takes 10-15 seconds to load.. Fixed after reboot ;)
-
I'll wait until the final release, hope it solves the 1.32NA problem... =(
-
I'll wait until the final release, hope it solves the 1.32NA problem... =(
You should go ahead and try the beta as you can always roll back to 1.3x again.
Once installed the beta says you have 1.32NA firmware.
I have not had any issues with the beta at all.
-
I'm at 5 Day 7 Hour, still stable. I guess the DNS Relay issue is really fixed for me.
YMMV.
-
I returned my DIR-655 a2 1.32NA to costco, and exchanged it for a DIR-655 A4 with 1.21.
I am back in business now finally with a working router. I will never upgrade my firmware again, what a mistake!!!!!!!!!!!
-
So where is your feedback on the new beta firmware, edlivian? Or are you trying to do something else?
-
So where is your feedback on the new beta firmware, edlivian? Or are you trying to do something else?
my feedback was 1.32b09 is still broken, the router hangs after a decent amount of traffic, and I would have to physically pull the plug on the g-d damn router every 48 hours. Also, wireless N is much slower with these recent revisions/firmwares since they enabled some type of wireless good neighbor that takes a dump on your wireless performance when there are nearby wireless clients detected. So if you live in the boondocks with no other wireless ap's in sight you are fine, but if you live in an urban area then you are f***ed.
And to be honest even though I have a A4 running 1.21, I still wish I could trade this for someone who has A2 with 1.11.
-
I was one of the silent many who suffered when I installed 1.31 and various 1.32 versions. Two wired users with moderate web browsing where I was required to reboot the router approximately every 24 hours, otherwise, I'd freeze up at an inopportune time. Always had DNS relay on.
Using the new 132.09 beta I've been up 6 days, 18 hours , 30 minutes without freeze-up or any other sign of network slowdown.
Two thumbs up......
-
Shareport issue is STILL not fixed. Unbelievable. How many months has it been since 1.30 was released now? At least 5 or 6. This has got to be the worst service I have ever experienced.
-
Shareport still broken here too
-
DIR-655 A3, Using COMCAST Business Gateway with static IP, Running several web servers, I would say above average traffic. My story:
Upgraded from 1.21 to 1.32NA. Started to have router lockups every 2-3 days. Even with DNS relay turned off. The firmware was running slow, some pages were loading noticeably slower than 1.21. I don't use sharepoint (therefore cannot validate this feature).
Installed 1.32b09NA 7 days 11 Hrs ago, running no problem since then, with DNS relay now turned on. And firmware seems to be loading pages quickly. Finally!
-
Shareport still broken here too
You might want to check for OS (TCPIP stck, network connections) issues ...
-
I've got 11 Day 23 Hour 35 Min 39 Sec on this BETA with no issues to date. Over the weekend I downloaded about 11 GIG worth of files as I downloaded the ISO for Windows 7 and the game client for WoW after reloading my machine. Didn't hiccup a bit.
I also don't use SharePoint, so can't verify anything there. No lockups otherwise so far.
-
This new firmware version (beta 9) seems to decide to do some sort of soft reset from time to time.
Anyone else observed this?
I have observed from the alive counter that there were 4 'reboots'. This is what it looks like as the alive timer was reset in all those cases.
On average after about a day (1 time the router lasted for several days)
The log pretty much (this new version does not completely loose the logs after automated reset?) tells the same story:
[INFO] Tue Nov 24 08:14:38 2009 Wireless restart
[INFO] Tue Nov 24 07:01:31 2009 Time synchronized
<------------------- after trying to synchorinse NTP it seems to go wrong -------->
[INFO] Fri Nov 20 19:12:32 2009 Requesting time from 207.232.83.70
[INFO] Fri Nov 20 19:11:35 2009 Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
[INFO] Fri Nov 20 19:11:32 2009 Time synchronization failed (status 2)
[INFO] Fri Nov 20 19:11:30 2009 Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
[INFO] Fri Nov 20 19:11:29 2009 Requesting time from 207.232.83.70
[INFO] Fri Nov 20 19:11:29 2009 Time server ntp1.dlink.com is at IP address 207.232.83.70
After requesting time the router does not log anything anymore. This was the kind of break point all four times. According the current alive time the system was operational for about 10 hours meaning that the entry at about 7:00 am is the first one.
The logs tell me it was not a full reboot as the standard intialisation stuff does not apear at 7:00 ish in the log. Or?
Who can explain this?
I will make a new topic for this
-
Disable the NTP server and see if the unit boots normally?
-
I tried the firmware, it's still been a rocky road.
Can we just get a utility to go back to 1.21? Why drag on like this.
-
I tried the firmware, it's still been a rocky road.
Can we just get a utility to go back to 1.21? Why drag on like this.
And what about to report the problem you're having instead of making posts without any content that can help to solve the problems??
For me, this beta 9 is working just fine
-
And what about to report the problem you're having instead of making posts without any content that can help to solve the problems??
For me, this beta 9 is working just fine
Point, welcome to the forum. But as you noticed there's a bunch of users that do not use the board to get help (and provide the data required). Ranting is their hobby, I wonder what happens when they need to see a doctor in personal life ;)
And for 1.21: That's about the worst FW ever from Dlink :)
BTW: beta09 is working fine with heavy wired and wireless load.
-
I second this Eddiez "BTW: beta09 is working fine with heavy wired and wireless load". However, I still wanted dlink to do something to extend the range of the signal and its about the last thing to make dir-655 a killer router.
-
I second this Eddiez "BTW: beta09 is working fine with heavy wired and wireless load". However, I still wanted dlink to do something to extend the range of the signal and its about the last thing to make dir-655 a killer router.
1. the max amount of 'transmitter power' is legally bound (otherwise you would need a permit (like a radiostation ;)) to use this device)
2. the range is much more influenced by environment than tech solutions inside the router.
So theres just a tech limit on what a router can do.
-
And for 1.21: That's about the worst FW ever from Dlink :)
EddieZ,
not to hijack this thread (don't think this deserves a new topic), but I was wondering what your current recommended FW version was for the DIR655. I am running 1.21 now, but if it is the "worst FW ever" I suppose I should change it. However, I am extremely against the idea of using 1.3+ as I have read many horror stories (here and elsewhere) and am not willing to take that risk. I also do not feel comfortable using Beta firmware, especially when there is no choice to revert once it has been put in place (although from the looks of it, they are doing a fine job with it and it will be 'the one' once it has been vetted and released).
I realize this puts a lot of restrictions and narrows down the choices, but I am all ears :)
-
EddieZ,
not to hijack this thread (don't think this deserves a new topic), but I was wondering what your current recommended FW version was for the DIR655. I am running 1.21 now, but if it is the "worst FW ever" I suppose I should change it. However, I am extremely against the idea of using 1.3+ as I have read many horror stories (here and elsewhere) and am not willing to take that risk. I also do not feel comfortable using Beta firmware, especially when there is no choice to revert once it has been put in place (although from the looks of it, they are doing a fine job with it and it will be 'the one' once it has been vetted and released).
I realize this puts a lot of restrictions and narrows down the choices, but I am all ears :)
Do you have any problem with 1.21?
If you don't, keep it.
-
Running 1.32b09NA with DNS relay on, for 25 days now. Seems like it's a keeper. Again, I'm not using SharePort, therefore cannot validate this feature.
-
I'm getting occasional router crashes with 1.32b09. The cause of the crash is not clear as it seems the log is truncated at the time of the crash, however my guess is that its occuring only when I am VPNed into my company network. Setup: I reset the modem to the factory defaults before uploading b09, and then reset it again to factory defaults after installing. I did not restore settings with a config file, but instead redid the few custom settings manually.
-
Do you have any problem with 1.21?
If you don't, keep it.
Unfortunately, I am having a problem with the router, although I am unclear of the cause and whether it is even the router at all, although all indications seem to be yes. I am just looking for the 'official' word from a Moderator or Tech Support person on what they recommend.
-
Just another quick update Ruf...
So far I gave 8 Day 2 Hour 35 Min 59 Sec on the version of the FW with NO crashes or major issues. While I'm a competent network guy (i do it for a living), i don't stress this router at home all that hard as far as port forwarding, etc. etc....
so whatever you've done here so far seems to have corrected at least the random lockup issues I was having with the internal website becoming non-responsive and suddenly not being able to get to the internet.
-
Running 1.32b09NA with DNS relay on, for 25 days now. Seems like it's a keeper. Again, I'm not using SharePort, therefore cannot validate this feature.
Similar situation here. Though I'm on 27 days :) I think it's the longest this DIR-655 has ever been up.
DNS Relay enabled, NTP enabled using ntp1.dlink.com
-
Was running it for about 2 weeks and no problems what so ever. But as soon as I turned on Dynamic DNS the router is "rebooting" quite often.
-
What I want to know before even attempting an upgrade to a beta firmware is if this fixes the issue with Shareport or not?
Isn't it about time this problem is fixed?
-
You're smart, martok, by asking before action. Lots of people returned their router simply to get firmware back to 1.21. which in my opinion is the best ever firmware from Dlink.
By the way, if 1.21 is the worst, why don't d-link start shipping their dir 655 with firmware 1.3x? which will be fun to see.
EddieZ,
not to hijack this thread (don't think this deserves a new topic), but I was wondering what your current recommended FW version was for the DIR655. I am running 1.21 now, but if it is the "worst FW ever" I suppose I should change it. However, I am extremely against the idea of using 1.3+ as I have read many horror stories (here and elsewhere) and am not willing to take that risk. I also do not feel comfortable using Beta firmware, especially when there is no choice to revert once it has been put in place (although from the looks of it, they are doing a fine job with it and it will be 'the one' once it has been vetted and released).
I realize this puts a lot of restrictions and narrows down the choices, but I am all ears :)
-
Well, just upgraded this morning (12/15/2009 @ 11:20AM EST). I was having the lockups and reboots and dropped connections quite often, as much as 10 times a day. Those all required me to pull the plug to reset the router as you could NOT get to the router's internal setup pages.
Hope this fixes these issues as I really like this router and ever since upgrading to 1.32 it's been less than stellar.
-
You're smart, martok, by asking before action. Lots of people returned their router simply to get firmware back to 1.21. which in my opinion is the best ever firmware from Dlink.
By the way, if 1.21 is the worst, why don't d-link start shipping their dir 655 with firmware 1.3x? which will be fun to see.
I Agree with you, and when will this firmware be fix. Its very quiet by Dlink
-
What I want to know before even attempting an upgrade to a beta firmware is if this fixes the issue with Shareport or not?
Isn't it about time this problem is fixed?
It fixed it for me.
-
So far, no firmware has fixed the MAC filter on = router stucked on save setting. Have to do a hard reset to get it working again. One thing I notice is that I'm getting ton of errors, it start out small and start going up and last I checked was at 90k. Never have this much of an issue with my Netgear WNDR3300, WNR3500 or Asus 520-GU (best router I have ever use). This router is going back into its box until a newer/better firmware come out.
-
So I know I'm probably asking a stupid question. However, I can't get the beta firmware to download for me. The download page won't load, just saying that it cannot find the ftp server. Am I doing something wrong?
-
So far, no firmware has fixed the MAC filter on = router stucked on save setting. Have to do a hard reset to get it working again. One thing I notice is that I'm getting ton of errors, it start out small and start going up and last I checked was at 90k. Never have this much of an issue with my Netgear WNDR3300, WNR3500 or Asus 520-GU (best router I have ever use). This router is going back into its box until a newer/better firmware come out.
I have MAC filter on. Never got that any error, with any firmware version.
-
You're smart, martok, by asking before action. Lots of people returned their router simply to get firmware back to 1.21. which in my opinion is the best ever firmware from Dlink.
By the way, if 1.21 is the worst, why don't d-link start shipping their dir 655 with firmware 1.3x? which will be fun to see.
they are shipping them with 1.32na. i just got one and have been frustrated since i turned it on...
-
they are shipping them with 1.32na. i just got one and have been frustrated since i turned it on...
When you received the router, was it in a brand new SEALED box?
-
yes, shrink wrapped. seemed new to me...
-
I upgraded to 1.32 from the old 1.20 firmware. I wanted the share point so i could share my printer easily with the network. This.. did not go well. I don't blame share port for not being compatible with my printer. [it doesn't recognize it as a printer] but now my router has to be re booted every few days.
I'm hoping they post a new firmware that fixes these issues. Previously my router was rock steady.
I'm hopeing that d-ling find the bug and squashes it and also restores the functions they have removed.
[I'm all for adding new functions but not for removeing existing functionality without a good reason and explaining to the customers whats going on]
-
I upgraded to 1.32 from the old 1.20 firmware. I wanted the share point so i could share my printer easily with the network. This.. did not go well. I don't blame share port for not being compatible with my printer. [it doesn't recognize it as a printer] but now my router has to be re booted every few days.
I'm hoping they post a new firmware that fixes these issues. Previously my router was rock steady.
Try this, it worked for me...
First, I hope you have your original 1.21 configuration stored somewhere. Then -> Downgrade to 1.31 (unlike with 1.21 you can do that)->Restore 1.21 configuration on the top of 1.31->Save the 1.31 configuration->upgrade to 1.32b09-> restore the 1.31 configuration on the top of 1.32b09
Good Luck!
P.S.
I had huge problems with 1.32NA from the day one. But this one was a saver for me. I'm close to 2 month w/o reboot or any major issues, and I run 24/7 production http, https and ftp traffic through my router, about 6 WinXP and Win7 clients with heavy streaming video traffic on the weekends.
-
unhappy with this latest firmware. Wish can downgrade it:
my related posting:
How to connect wireless router with 3G USB Modem?
http://forums.dlink.com/index.php?topic=10027.0
-
Mine had been fine since I updated it on the day the beta was released. However, yesterday I had to make a config change, the first one since I setup it up and did the config the day I flashed it to the beta firmware. I went in made my change/addition. Router said it had to reboot. Let it reboot and now I'm back to my problem where nothing in the advanced tab saves and all settings in the advanced tab were reset.
I've reset the router and reflashed, if I setup everything directly after the flash it's fine. But if I wait a couple hours and go in and make a change the problem occurs again.
-
Does this actually mean that they ship "new routers"(that are on the market for such a long time) with beta firmware installed? ???
they are shipping them with 1.32na. i just got one and have been frustrated since i turned it on...
-
Does this actually mean that they ship "new routers"(that are on the market for such a long time) with beta firmware installed? ???
No, 1.32na is a final firmware.
-
Ok, tnx, I must have missed the final one in between all those beta's ;D
No, 1.32na is a final firmware.
-
Ok, tnx, I must have missed the final one in between all those beta's ;D
Thi final one was released before those betas (b04 and b09).
The betas were released to correct the 1.32na final issues.... ::)
b04 is supose to correct the shareport issue, and b09 the dns relay issue. (don't know why they don't release a new beta build with the two issues solved...)
-
Do I stand corrected?
All the beta I'm talking about starts with 1.32na
They all say they solve issues that, according to posts in this forum, still exist to some matter.
It's f&/+&%+ quite clear that actual buy-ers are user as beta-testers.
NOT EVEN MICROSOFT GOES THIS FAR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! >:(
DE-Link is not to be considered as a serious hardware supplier anymore, in my opinion.
Thi final one was released before those betas (b04 and b09).
The betas were released to correct the 1.32na final issues.... ::)
b04 is supose to correct the shareport issue, and b09 the dns relay issue. (don't know why they don't release a new beta build with the two issues solved...)
-
By the way, I just got a warning in red text that this may get me kicked out! ;D ;D ;D ;D ;D ;D ;D ;D
Do I stand corrected?
All the beta I'm talking about starts with 1.32na
They all say they solve issues that, according to posts in this forum, still exist to some matter.
It's f&/+&%+ quite clear that actual buy-ers are user as beta-testers.
NOT EVEN MICROSOFT GOES THIS FAR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! >:(
DE-Link is not to be considered as a serious hardware supplier anymore, in my opinion.
-
Do I stand corrected?
All the beta I'm talking about starts with 1.32na
They all say they solve issues that, according to posts in this forum, still exist to some matter.
It's f&/+&%+ quite clear that actual buy-ers are user as beta-testers.
NOT EVEN MICROSOFT GOES THIS FAR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! >:(
DE-Link is not to be considered as a serious hardware supplier anymore, in my opinion.
why? because they released a final version with some bugs? s*** happens everywhere.
The routers are being shiped with a production firmware. Not a test one.
The error here is calling those betas 1.32... they should call them 1.33, since they where released to fix bugs of the 1.32 final.