D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: dirkpitt on March 30, 2010, 09:13:07 AM
-
Let's see how many users are interested to see a release of firmware without the beast known as SecureSpot.
SecureSpot can be accredited for, or is somehow causing (and this list is not even intended to be all-inclusive):
-sporadic and unpredictable hi-jacking of some routers to dir-655.bsecure.com Fixed in 1.34 beta!
http://forums.dlink.com/index.php?topic=11791.0 (http://forums.dlink.com/index.php?topic=11791.0)
-users having trouble saving port forwarding and other settings to flash without first enabling SecureSpot
http://forums.dlink.com/index.php?topic=12037.0 (http://forums.dlink.com/index.php?topic=12037.0)
-some looping issues attempting to redirect all internet traffic through dir-655.bsecure.com Fixed in 1.34 beta!
http://forums.dlink.com/index.php?topic=11994.0 (http://forums.dlink.com/index.php?topic=11994.0)
-SecureSpot website security concerns from paying subscribers Unconfirmed
http://forums.dlink.com/index.php?topic=12313.0 (http://forums.dlink.com/index.php?topic=12313.0)
-SecureSpot repeatedly re-enabling itself Fixed in 1.34 beta!
http://forums.dlink.com/index.php?topic=11739.0 (http://forums.dlink.com/index.php?topic=11739.0)
http://forums.dlink.com/index.php?topic=11746.0 (http://forums.dlink.com/index.php?topic=11746.0)
-Access Control does not work unless SecureSpot is enabled Fixed by disabling Dynamic Fragmentation
http://forums.dlink.com/index.php?topic=11994.msg73979#msg73979 (http://forums.dlink.com/index.php?topic=11994.msg73979#msg73979)
From what I have read on these forums the last few weeks is that there are two avenues to rid yourself of the SecureSpot headache:
1. Downgrade the firmware to an ancient, but SecureSpot-free release of firmware: http://forums.dlink.com/index.php?topic=10668.0 (http://forums.dlink.com/index.php?topic=10668.0) I reject this as a hack and not a real solution to remedy these problems; there have been enhancements to the firmware to improve the performance of the router that will not be included in 1.2X firmware. SecureSpot excluded.
2. Buy a new router.
-
I'm in.
When Dlink issues a SecureSpotless firmware I might even get the 655 out of the closet and use it again.
Until then this network runs via DD-WRT.
-
I'm in.
When Dlink issues a SecureSpotless firmware I might even get the 655 out of the closet and use it again.
Until then this network runs via DD-WRT.
Same here, in the meantime I am back with my "good old" Netgear! :)
-
I've been wondering if maybe 1.32EUB02 may be the updated release that we've been craving--mayhaps the EU has rules that have saved them from SecureSpot.
Looking at the release notes, it also appears that they are way more diligent about responding to reported issues!
Has anyone tried this flavour?
-
Count me in.. I wish they would spend more time fixing problems that have existed for years and forget about this crappy add-ons, i understand it's extra income but still. Why not make separate download and explain people the hazards of installing stuff like Bsecure.
-
Never had this problem on any of the 655 routers I administer.
-
Never had this problem on any of the 655 routers I administer.
I didn't either, until I did, and there has been absolutely no solution. Crummiest router I've ever had the misfortune of purchasing.
-
Never had this problem on any of the 655 routers I administer.
Which one? I listed six.
-
I was thinking more along the lines of a class action lawsuit for this damn malware they loaded onto my system with a firmware update that has been hindering my company's productivity.
-
Which one? I listed six.
None of them....all the 655's I take care of work perfectly.
-
None of them....all the 655's I take care of work perfectly.
Well isn't that nice for you!!
Are you trying to convey something meaningful or are you just gloating?
-
Well isn't that nice for you!!
Are you trying to convey something meaningful or are you just gloating?
You asked a question so I answered it.
-
Well isn't that nice for you!!
Are you trying to convey something meaningful or are you just gloating?
I think it's best to just ignore the "I don't have a problem with my DIR-655" posts.
-
I think it's best to just ignore the "I don't have a problem with my DIR-655" posts.
Why, some people don't have any problems. Mine has been running without any issues for over 2 years now. I have used every Beta firmware that has been put out and have not once had an issue.
-
Why, some people don't have any problems. Mine has been running without any issues for over 2 years now. I have used every Beta firmware that has been put out and have not once had an issue.
Same here,
disabled SecureSpot directly after flashing the firmware and never had problems with it.
I see there are a lot of you having problems with it - but you should acknowledge there are also a lot user without SecureSpot issues.
My Rev A2 is running absolutely reliably with latest 1.33NA and in the meantime I also flashed m Rev A5 with it as I experienced wireless restarts with the latest EU version. Now they both are running the last 10 days without a drop of connection.
I'm working a lot from home and need multiple VPN connections without drops.
DIR-655 is my best friend for this.
But as I don't need SecureSpot : Yes I'm very interested in a firmware without this code. Perhaps it frees some Bytes in the memory and perhaps it prevents me from getting the same problems sometime in the future as some of you already have .
-
... I see there are a lot of you having problems with it - but you should acknowledge there are also a lot user without SecureSpot issues. ...
Why? It does nothing to solve the problems some people are having.
-
thumbs up for a securespot-disabled firmware
-
Somebody told me that the original firmware came without this Secure Spot. Seems to me if it did once, it can again. What's the big problem with simply extracting it entirely? Seems to me this is really the only proper answer to this huge huge problem. I had thunderstorms that rebooted everything and once again I got hijacked to bsecure.com.
Is anyone at D-Link actually listening to us? It really isn't fair that I bought something with this many problems. I'm getting a real bad feeling about all this.
-
D-Link take a look at all of the unsatisfied end users because some moron decided that everyone needed protection. Take a little time and offer a SS free firmware upgrade. You most likely already have it developed, just put it out there and then ask your customers how they feel. This Securespot problem is a cluster...
-
Yes please get rid of the freaking Secure Spot P o S. I hate having to come home from work and enable disable reset reboot to be able to access the freaking internet. You are just luck that no one else has made a comparable router yet. Because as soon as they do, all these buyers are going to see this and jump ship.
-
linksys has a new unit... E3000 I think it is... A/B/G/N both 2.4 and 5 GHz simultaneous...I think maybe only thing is no USB printer support and it has 4 gigabit LAN ports.... $149 on newegg
-
I've been using the DIR-655 for a few months now and just within the last few days this BS SecureSpot has been hijacking my router. I don't have it turned on within my router's settings and I canceled my SecureSpot account
Why is this issue not being addressed by DLink? The Dir-655 is my first experience with DLink and if this isn't resolved fast, it will be my last.
I knew I should have gone with a Linksys!
-
Hi,
Don't just blast at DLink.... If you do some deeper probing, you will very likely find that all the consumer makers have had at times major issues with units here and there..... I personally went thru some heck a few years back with a netgear wgt-624 wireless router that had LOTS of folks up in arms....
The problem for these makers is whether or not it makes financial sense to try and uncover what are quirks to them, but are REAL issues for some folks.....but most others have no issues worth mentioning if any. I have been fortunate enuff to fall into the latter category with my 655.
If you are saying there should be no NO ISSUES EVER with a router or its firmware, well then, I would like to agree with you 100%, but in real world, it probably isn't gonna ever be that way.
Blame DLink for selecting the Ubicom chipset that this router uses. Ubicom sets the fee's for licensing which has kept the 655 out of the world of DD-WRT development from the reading I have done in the recent past. If Ubicom would drop their fee schedule for this chipset, I bet the DD-WRT coders could have a working firmware in short order....but they don't want or need the hassles of fighting lawyers and such for infringment.....and I don't blame them.
-
What is the deal with this hijacking? It happened again this morning. This is really really becoming annoying. Mornings are not the time for things like this when I'm trying to get out the door.
I was trawling down the forum last night and found a thread about exactly this problem with a gazillion replies and it had been locked. The good news is that this isn't a "quirk" but a real issue obviously, and it seems like what kicked it off was the changeover to daylight savings/summer time. I know looking back, that's just about where my problems began. The bad news is that we haven't heard any news on a fix from the person who locked that topic.
I've got a bad feeling about this whole thing. I wonder if I can sell this brick to some poor unknowing sap? But then again, do I want that kind of bad karma?
So frustrating. Argggh!
-
Sammydad1 - I'd agree with most of what you say except in this case, this issue has been reported over a month ago and there is a sever lack of inaction on DLink's part to rectify the issue. Now, I'm no business major, but I would think that not fixing (ignoring) a very public issue will cost them more in lost future business that it would to address the problem.
Their lack of customer support is appalling.
-
Oh my goodness! I trawled down further and found another locked topic about Secure Spot exposing credit card numbers! The moderator or whoever said it was locked because of "security reasons."
But that only piques my concern more. If it was closed for security reasons, what were they? Is this something to be concerned about? Talk about unnerving. No explanation. It's just left dangling out there.
Now I'm glad even more than ever that I never ever remotely considered Secure Spot.
All the more reason to eliminate this obviously faulty and now very scary "feature."
This just gets worse and worse. Sheesh.
-
This thread is a re-post of another that I started back on March 30... http://forums.dlink.com/index.php?topic=12315.0 (http://forums.dlink.com/index.php?topic=12315.0)
This just reinforces two things: that many of us are feeling the same way with the problems that SecureSpot repeatedly is associated with, and that the mods here aren't paying much attention to the members or these threads.
I have personally had it with De-link and being ignored by the mods (never heard back from Lycan regarding packet capture), tech support (the bsecure servers have been reset and there is no more problem) and the unreliability of the basic firmware functionality on my DIR-655.
-
If De-link's firmware has been built using any half decently formalized code development environment it should be possible to make a new build in a matter of minutes.
I assume that either it has not been built in that kind of environment (which would explain some of the undeniable faults in the code) or that they are much too busy programming for whatever bug-ridden router is to be their next cash cow.
Either way, De-link customers lose.
-
I do not have the option of "securespot" here in good old England. The router tells me it has the latest firmware. I am using - - Firmware Version : 1.21EU, 2008/11/03 , erm note the EU.
The firmware from the European web site of D-Link is DIR655A4_FW121EUb05 on my DIR-655 version A3
I think I was offered the dubious delights of this securespot but declined that update some time ago and kept the EU version and its updates.
Take it from there. Don't blame me if you change the firmware and it screws up. I just stated what we have over this side of the planet. ::)
-
My personal experience - problems that seem related to firmware after the introduction of SecureSpot into 655. I have opened a case number with tech support for my problem and I suggest that you all do so to, if you haven't done so by now.
I would also like to respond to an earlier comment about what seems like a defense of poor product support. When a company sells a product, it warrants that it works. So, it does not matter the cost of the product or the cost of ongoing support (to the company) or whether the company thinks that a problem is just a quirk. I don't know whether I will get better support from one of Dlink's competitors, but I am certainly a lot more likely to consider a competitor's product when what seems to be a relatively simple issue to fix is ignored.
-
Thanks for the heads up. The "check to see if I have the latest firmware" button doesn't work. The most current release for the EU is 1.31EUB02.
This version would include the HNAP security fix, which is one of the fixes that I would like to keep on my router.
-
Just added Access Control as being another victim of SecureSpot in the first post.
-
Today after having my dir-655 working with securespot disabled all my http requests were being redirected to bsecure.com add device by mac address page which would refresh indefinitely without ever loading anything useful of getting me to my destination url.
I did mistakenly sign up for securespot when i setup my router since I thought it was part of the router authentication. I disabled securespot and canceled my account the same day.
Today I double checked that securespot was disabled in my router admin. It was. I had to enable securespot, click save, then disable and click save before I could browse the web. Please add me to the list of users who would like firmware without securespot included.
I'm on firmware 1.32NA (check button says no updates available), hardware version A4.
-
Look in the beta section people as a new firmware has been released.
http://forums.dlink.com/index.php?topic=12504.0
-
Look in the beta section people as a new firmware has been released.
http://forums.dlink.com/index.php?topic=12504.0
But it's yet another beta. Anyway, I bit and figured with things as bad as they are, it couldn't make things any worse.
I installed this beta exactly as instructed. I was connected by Ethernet. After the thing rebooted, the same firmware was still indicated 1.33NA, not 1.34b02NA_beta.
You'd also think that with all that beta testing going on, all the goofs would be weeded out.
I guess I'm asking, ''when can we have something that works?''
-
The flash did no complete or had some other problem.
After installing the beta my router page shows 1.34NA firmware version.
I would suggest you reset the router with the reset button on the back and then wait for the router to fully initialize before performing the flash.
-
But it's yet another beta. Anyway, I bit and figured with things as bad as they are, it couldn't make things any worse.
I installed this beta exactly as instructed. I was connected by Ethernet. After the thing rebooted, the same firmware was still indicated 1.33NA, not 1.34b02NA_beta.
You'd also think that with all that beta testing going on, all the goofs would be weeded out.
I guess I'm asking, ''when can we have something that works?''
I'll try it cause at this point I've got nothing to loose, my system is un-stable and un-secure thanks to B-Secure anyway. If it breaks the unit I'll just toss it in garbage and go buy some other brand cause D-Link brand at this time isn't one I wish to deal with anymore when it comes to routers because it just makes me frustrated and very angry.
-
But it's yet another beta. Anyway, I bit and figured with things as bad as they are, it couldn't make things any worse.
I installed this beta exactly as instructed. I was connected by Ethernet. After the thing rebooted, the same firmware was still indicated 1.33NA, not 1.34b02NA_beta.
You'd also think that with all that beta testing going on, all the goofs would be weeded out.
I guess I'm asking, ''when can we have something that works?''
After reset mine says 1.34NA, 2010/04/08 but to be honest the fact that BSecure is still in it at this point makes me feel un-easy, after the problems I have had I have reached a certain level of paranoia and I do not wish to have anything to do with that service I certainly do not wish to have it even as an option in my router. If this solves the problem I won't ditch DIR-655 immediately but as long as D-Link insists on having this service in their routers my future router won't be D-Link and if they don't release BSecure free firmware within this year I'll be replacing my DIR-655 by the end of the year with another brand that doesn't force this horrible service on their users.
-
I'm relieved to see that there has been some attempt to repair the firmware for the DIR-655.
Love the disclaimer: "Warning: This code is used at your own risk. D-Link is not responsible for damage caused to your router or network through its use."
I think this is tongue-in-cheek... the official release should have carried the same note! ;-)
Well... here goes...
-
i came across a minor bug with the beta firmware. under the status tab --> statistics -- there is a high number of sent and received packets under the LAN statistics category. I tried clearing the statics and it would not clear. as for being free of securespot functionality, i don't know. i don't have a problem with securespot under 1.33NA firmware.
-
First attempt: tried backup up settings, plain uploading the firmware--still indicates 1.33NA. Reboot via firmware. Same thing. Hit the reset button on the back. Cycle power. Password has been blanked, so assuming that settings have been restored to factory defaults... starting over...
Upload 1.34 beta... reboot... success! It indicates 1.34NA. Restore settings from backup... more success!
Check that Access Control is enabled... check! Check Website access... bsecure.com is blocked... enter dir-655.bsecure.com... Not blocked! Checking SecureSpot enabled/disabled... not checked. Disappointing. Enable Securespot, save settings. Disable Securespot, save settings. Still not blocked. Grr.
Let's see if a reset between enable/disable helps... Enable SecureSpot, reboot... disable SecureSpot, reboot. Attempt to browse to blocked URL... Nope.
Is this fix only for the hijacking issue?
-
Okay, so the hard reset, the firmware update and then the restore settings worked. The router now reports the proper 1.34.
Everything else looks the same though. I see that Secure Spot is still there, although it is de-selected.
Any chance of fixing the DST (Daylight Savings Time) feature so that the correct time is pinged?
CORRECTION: DST does indeed seem to be working. I also changed my NTP by manually typing in time.apple.com, altered the DST settings for 2010 (DST begins 2nd Sunday in March and ends 1st Sunday in November. No crash-reboot. Settings saved and time now correctly displayed.
-
i don't have a problem with securespot under 1.33NA firmware.
Dir-655 router I have at work doesn't have a problem with securespot either, the only difference between the one I have at home and the one at work is that I have actually registered with bsecure on my home router and tried it for a year then decided not to renew the service because of problems I had with it I simply let the subscription run out then the blocking problem started. I am actually surprised that you have upgraded to this new beta if you don't have any hijacking issues with bsecure because that is the only fix in this update.
I won't be upgrading the router at work until there is a final build, because of the issues I've been having on my home router I really had no choice. I am still not happy about the fact that D-Link doesn't provide bsecure free firmware they did that with version 1.22, I simply don't trust that service. I've been planning to keep my router for another year or two before I upgrade and I've been looking at newer dual band routers from D-Link but if D-Link doesn't provide bsecure free versions of firmware for their routers after the bad experience I've had with the hijacking I won't even touch their routers.
-
Is this fix only for the hijacking issue?
I think that's the only fix.
-
Voting for a new securespot free firmware as well.
I had a look at its functionality when I bought the router way back in time. Disabled it and canceled my account within an hour. Haven't heard from them since. Until today.
Had my home pc up via my wired LAN, running my favorite internet radio channel in the background. Started up my company laptop, having it connect to the net via wireless as usual when suddenly the internet radio stoped playing. Trying to reload the channel's home page on my home pc I was re-routed to bsecure's homepage telling me "Invalid Arguments. One or more MAC Addresses not found.". Same thing on the company PC. You know the rest....
Shut everything down except my company laptop and worked off-line for two-three hours. Restarted the router and home pc and everything worked fine. But for how long? Having my browsing trial being saved where? Having my routers performance spent on what?
Edit: FWIW having firmware 1.32NA, 2009/07/09 and home pc running Win 7 64 and company pc Win XP SP2.
-
swehjo: try the new 1.34 beta--see if it will cure the issue...
-
There is a new beta release 1.34 which may address some of these concerns. SecureSpot is still present, but the Enable/Disable checkbox is reportedly working!
-
SecureSpot is still present, but the Enable/Disable checkbox is reportedly working!
Agree with you it seems to be working. But as for myself my trust with D-LINK is now broken and it will take more than a Beta Firmware to restore it! >:(
-
As of right now the SecureSpot feature will not be removed from the firmware of the DIR-655. The beta code, http://forums.dlink.com/index.php?topic=12504.0 (http://forums.dlink.com/index.php?topic=12504.0), will correct the troubles with the SecureSpot service even when it is disabled.
Oh my goodness! I trawled down further and found another locked topic about Secure Spot exposing credit card numbers! The moderator or whoever said it was locked because of "security reasons."
The topic was removed and locked while we investigated a possible security threat. We do not want to encourage any malicious behavior towards our users whether or not the threat is valid.
-
sesca, any comment how this SecureSpot change will impact any of the other issues listed in this thread: http://forums.dlink.com/index.php?topic=12315.0 (http://forums.dlink.com/index.php?topic=12315.0)
(It should likely be merged with this thread too: same subject)
-
sesca, any comment how this SecureSpot change will impact any of the other issues listed in this thread: http://forums.dlink.com/index.php?topic=12315.0 (http://forums.dlink.com/index.php?topic=12315.0)
I'll take a look at the Access Control feature more closely. As far as having trouble loading the firmware, PM me if your upgrade is not successful. There shouldn't be any trouble but I will look at the individual instance and try to find the common factor.
-
As of right now the SecureSpot feature will not be removed from the firmware of the DIR-655.
Why? Honestly, and it's just me speaking, but when you buy a computer, you get a lot of "extra stuff" installed but you're more than free to uninstall it.
Secure Spot just doesn't really belong in my opinion, but at least it should be an "added" option installed separately by customer choice, not embedded. How about a "back to basics" firmware where we lose all but the core functionality that is time tested and secure?
I know that's a novel approach.
-
swehjo: try the new 1.34 beta--see if it will cure the issue...
Today I logged on with another company laptop via Wifi and again bsecure stepped into action and I had to shut everything down. Two things are interesting with this:
- I've also logged on with my sisters laptop on this network during these last days but via wire and that has not initiated this problem
- all traffic on the company laptop I used today that went through the company's VPN-tunnel-sort-of-thing, for example company mail and our intranet, worked but no other sites, like reaching this forum.
Well, after this I installed the new firmware. Hope the problem goes away...
-
As of right now the SecureSpot feature will not be removed from the firmware of the DIR-655.
That's a shame. It sounds to me that your customers want this removed and last I checked, it's usually the paying customers that should have a say in what features should/shouldn't go into a product.
-
Updated the status of some of the original issues driving this thread to reflect the benefits of 1.34 beta. ;D
-
Oh contraire....end users having a say as to what features are added to a product ? That is so 20th century..... Here now the Marketing people decide what we end-users want....And they are happy to tell us what those features are too !!
Securespot was an iffy product when it was standalone.... MAYBE a reasonable idea....but not so sure about the execution part.... NOW with embedded securespot in our firmware...its even more iffy.
-
That's a shame. It sounds to me that your customers want this removed and last I checked, it's usually the paying customers that should have a say in what features should/shouldn't go into a product.
While we understand that you would like it have it removed, there are many other customers that would like to keep the feature. What we're attempting to do is come up with a solution that doesn't require D-link to maintain two firmware sets.
-
While we understand that you would like it have it removed, there are many other customers that would like to keep the feature. What we're attempting to do is come up with a solution that doesn't require D-link to maintain two firmware sets.
Thanks Lycan for keeping us updated, it'appreciate. :) Any idea how long before D-Link will be able to come up with a final decision?
-
Our family are appreciative of the SecureSpot service. Just to let you know we're glad for it!
-
personally I question the expense of securspot versus whats available for free with a little research....
-
While we understand that you would like it have it removed, there are many other customers that would like to keep the feature. What we're attempting to do is come up with a solution that doesn't require D-link to maintain two firmware sets.
I think, and I know this is just my opinion, but I think you should make this Secure Spot a separate option, just like you have the separate printing via USB option. My argument for this is as follows:
I, for example, use OpenDNS to filter out a wide variety of "bad stuff" out there, and it is highly customizable. I have been using it for almost three years now and I really don't foresee any switch in my future. It is wholly separate from the router/gateway and if there are problems, I can simply "turn it off" or disallow it without having to wait for a firmware fix.
The fact that the very real potential exists for another Secure Spot/bsecure.com problem, judging by what just happened, why "throw out the baby with the bathwater?" Why allow for a third party feature, proven problematic, to potentially hamstring the entire firmware sometime down the road?
I think wisdom, aside from all the griping (deservedly so I believe) by those affected, should rule the day. Prune down the final firmware to basics so that we can really "bsecure."
-
I became Securespot afflicted earlier this week. I had never used the thing before in my life. Was using 1.32NA. You could enable/save/disable/save and it would work for a day then would have to do it again. This is not a viable option when you have people working from home and need instant on connectivity.
I did the downgrade to the 1.21 firmware that was discussed on one of these many Securespot threads and have not had a problem since of any kind. And I believe it is faster now too!
It's a little bit of a process but totally worth the 30 minutes or so it took me to do it and reconfigure the router.
I registered on this forum just to tell anyone with the Securespot issues how happy I am now using 1.21.
-
While we understand that you would like it have it removed, there are many other customers that would like to keep the feature. What we're attempting to do is come up with a solution that doesn't require D-link to maintain two firmware sets.
Coming from a software development background I do share compassion for the desire to maintain a single firmware set, but I disagree that this is the correct decision for the issues that come with SecureSpot.
Access Control does not seem to be working. It sounds to me that the viability of Shareport is iffy (I do not use this but it sounds as if there are some issues with it). Disabling QoS and other features is a solution repeatedly recommended on these forums. There are numerous threads of people proclaiming that they have become SecureSpot free by purchasing a competitor's product, or even regressing to using their old equipment. Securespot was not an advertised feature of the DIR-655 at the time of my purchase, whereas the inoperable features mentioned above were and still are.
It would seem that more emphasis is being placed on keeping subscribing SecureSpot clientele (which are an obvious minority among the users on this forum) than repairing some of the advertised features of the router.
Using the Russian firmware downgrade path to regain stability provided by 1.2X or even 1.1X firmware is very common. Others have opted to use the EU flavoured firmware rather than use a version with SecureSpot present. I do not believe that technical support would support these firmware releases, and the first recommendation from them would be to update to the latest official release of firmware, correct?
The "single firmware set" mentality is driving technically proficient users away from the most current released firmware and the D-Link name itself in droves. For each person who posts their grievances with SecureSpot there are dozens who will simply lurk and watch for results or solutions.
The problem with SecureSpot hijacking the basic ability of the router to the bsecure website is a huge breach of trust for people who understand the implications of the problem. Personally I want the ability to block all traffic between my router and bsecure as a guarantee that SecureSpot has been contained.
Don't get me wrong--I am a big fan of the 1.34 beta firmware and have not seen any further hijacking problems since I have had it installed. Let's keep moving in the right direction to get a solid version with everything working. Does SecureSpot need to be temporarily removed to simplify the process, as it obviously has some conflicts with Access Control?
Can we have some more information of why the enable/disable SecureSpot checkbox wasn't working prior to 1.34NA?
-
They should remove SecureSpot and add PPTP VPN endpoint capability (like in dd-wrt) that would make me so happy :D
-
This message is for D-link. I NEVER enabled the securespot option but for the last six months I've been having the same problem as everyone else and I'm fed up with it. I don't know which is more frustrating; having to enable-disable the option and reset the router, the interuptions for other members of the family and inconvenience for them when I'm not here to fix it, or the fact that this problem is due to programming incompetence.
I cannot teach every member of the family how to perform that rediculous work-around and installing that beta firmware seems like a waste of time since you have a disclaimer about it in large red letters. Such a disclaimer indicates that you expect the beta firmware to cause other problems.
I took the time to register for this forum only to let you know that I am going out now to by another router, NOT d-link. Also, my sister has a need for a new router and so does a friend of my wife's. Guess which router I will NOT be buying for them? I realize that this is only three customers which you have lost however, I will be sure to spread the word to everyone that I know to stay away from D-Link. I work in technical support for a large enterprise so as the oportunity comes up, I'll be sure to warn all of the people we support.
The problem should never have happened and your response to the issue has been unacceptable. This message is all that I have to say on the topic. I will waste no more time on this.
Sincerely,
A former loyal customer
-
This message is for D-link. I NEVER enabled the securespot option but for the last six months I've been having the same problem as everyone else and I'm fed up with it. I don't know which is more frustrating; having to enable-disable the option and reset the router, the interuptions for other members of the family and inconvenience for them when I'm not here to fix it, or the fact that this problem is due to programming incompetence.
I cannot teach every member of the family how to perform that rediculous work-around and installing that beta firmware seems like a waste of time since you have a disclaimer about it in large red letters. Such a disclaimer indicates that you expect the beta firmware to cause other problems.
I took the time to register for this forum only to let you know that I am going out now to by another router, NOT d-link. Also, my sister has a need for a new router and so does a friend of my wife's. Guess which router I will NOT be buying for them? I realize that this is only three customers which you have lost however, I will be sure to spread the word to everyone that I know to stay away from D-Link. I work in technical support for a large enterprise so as the oportunity comes up, I'll be sure to warn all of the people we support.
The problem should never have happened and your response to the issue has been unacceptable. This message is all that I have to say on the topic. I will waste no more time on this.
Sincerely,
A former loyal customer
Well said!
-
Well, finally updated from 1.21 to 1.34 week or so ago, and just finished ordering a new NetGear Router tonight, i had enough. Port Fowarding still not working, Virtual server still not working correctly, router keeps disconnecting every day, sometimes more than once daily, i have tried disabling some of the features, nothing seems to help. After the secure spot fiasco; that it for me and Dlink products, it's frustating to not have one single post from a Dlink Mod or whatever they're called and explain what exactly happened and if our information was being sent over to securespot even with secure spot disabled.. Seems like new paying features are the priority not fixing the existing features we all paid for, i won't even mention the features they have slowly removed or never cared to fix from the start. Enough venting, i wish you all good luck.
-
Well, I was finally able to fix the last of the issues that have plagued my network since upgrading to 1.3X.
I've included the updates and fixes in the first post of this thread. Thanks to you all for your help and suggestions or I would never have made it to this point!
-
I wonder if the issue with this crappy secure spot is only noticed by folks that tried it out?
My problem happens when i reboot the router.. It then somehow enables secure spot (even though i have stopped using it). The only way i can use any system that is connected to the route is to login to the router, enable secure spot via check box-save, then uncheck-save.. that fixes it and all my hosts/computers can get to the internet again.. I wrote to and call support.. Thats a laugh.. Their as helpful as a knife in a gun fight.
So has anyone else had the issue with secure spot but never actually configured secure spot?
This will be the last dlink router i ever buy or recommend to my customers. I think blowing the firmware away and installing wrt or something else might be called for.. until these idiots at dlink fix it.. (yeah right)
-
alaskan, have you tried the very latest release?
I am running 1.34b02 and haven't had any more occurrences of SecureSpot hijacking my Internet.
Now that I have the Access Control working, I have even blocked "bsecure" to ensure that nothing is routed through their server.
-
alaskan, have you tried the very latest release?
I am running 1.34b02 and haven't had any more occurrences of SecureSpot hijacking my Internet.
Latest is 1.34 final or 1.34build03