• June 03, 2025, 10:00:48 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Pages: 1 2 3 [4] 5 6 ... 9

Author Topic: 1.31 Offical Release  (Read 94623 times)

lotacus

  • Level 4 Member
  • ****
  • Posts: 450
Re: 1.31 Offical Release
« Reply #45 on: May 01, 2009, 04:52:42 AM »

Enable QoS. Reserve the up adress of the voip box. Enter static entry in QoS, voice high.

If you run torrents you may want to give those boxes lower priority than 128, which is the default. I would be more discriptive but I hate replying on my blackberry. I'm afraid I may walk into on coming traffic, or most embarrasing into a pole.   
Logged

DaveH

  • Level 1 Member
  • *
  • Posts: 10
Re: 1.31 Offical Release
« Reply #46 on: May 01, 2009, 09:34:24 AM »

You're sure the router drops connection ? Did you look into the LOG ? What are the messages when connection drops ?

What kind of connection is in use ? Cable or DSL ?
Which Modem do you use ?

You reset the device to factory defaults after upgrade and configured it manually ?
Did you already try to set the WAN-Port speed to 100Mbps - not Auto ?
Logged

DaveH

  • Level 1 Member
  • *
  • Posts: 10
Re: 1.31 Offical Release
« Reply #47 on: May 01, 2009, 09:36:58 AM »

Lizzie555, thank you for your help. I checked the log. The last entry is from Feb 28th and it is an IP being assigned. Am I sure it is the router? No. This problem just began shortly after the firmware upgrade to 1.31NA.  I did check with my internet provider and they do show my modem dropping off. My next door neighbor with the same service is not having similar problems.
 
To answer your questions, my service is cable. I have a Motorola S85101 cable modem. No I did not, but will, reset the device to factory defaults after upgrade and configured it manually. I will set the WAN-Port speed to 100Mbps - not Auto.

As a side note, in the few minutes I typed this, the connection has dropped six times…
Not sure if this helps but here are my Statistics. They are current. I reset them two days ago.

Sent :155278
TX Packets Dropped :1
Collisions :0   Received :174339
RX Packets Dropped :0
Errors :0
WAN Statistics
Sent :167097
TX Packets Dropped :0
Collisions :0   Received :252426
RX Packets Dropped :0
Errors :0
Wireless Statistics
Sent :81454
TX Packets Dropped :1362   Received :29918
RX Packets Dropped :62
Errors :445
Logged

bobbyl

  • Level 1 Member
  • *
  • Posts: 5
Re: 1.31 Offical Release
« Reply #48 on: May 01, 2009, 10:48:37 AM »

Wow...I was ready to make the leap from 1.21 (which has worked well) to 1.31...until I saw DavH's problems.  Not being able to roll back if there are problems is really a killer.  Will wait until more feedback comes in on the 1.31.
Logged

lizzi555

  • Level 5 Member
  • *****
  • Posts: 605
Re: 1.31 Offical Release
« Reply #49 on: May 01, 2009, 10:57:24 AM »

your statistics looks OK there are no errors.

With a cable modem try to connect directly after the reset with manufacturer settings.. It should work.
If your modem still drops connection try the settings I mentioned above.

Perhaps coincidentally the modem broke at the same time you updated the router  ;)

Logged

TommyLee

  • Level 1 Member
  • *
  • Posts: 8
Re: 1.31 Offical Release
« Reply #50 on: May 01, 2009, 11:23:07 AM »

The bottom line is simply that more than enough erroneous error's exist with customers regarding this firmware update to prevent the rest of us from upgrading to v1.31.

I was excited to find out about the update, especially with a version of the SharePort software for the Mac platform. However, after reading all of the existing threads for this post, I have no interest in upgrading/breaking my currently working Non-SecureSpot v1.21 firmware.

In my humble opinion, my recommendation having 20+ years in IT, and holding nearly two dozen industry certifications would be to allow qualified testers who do not need their router for a primary internet connection to more thoroughly test the firmware and provide ample feedback before the rest of you upgrade.

If you are not currently experiencing a problem, or the new firmware does not provide a requested upgrade feature, then there is truly no need to update your firmware version.

Having the latest and the greatest firmware is only okay for those that do not rely on it for there sole internet connection. All the threads in this post are a perfect example of that.

And in closing, we all appreciate the engineers hard work, but bugs in the code are inevitable. Hence, ...allow for appropriate testing and feedback before upgrading. And what I mean by that, is feedback here in the forums. Don't rely solely on D-Link's QA department to find all the bugs. They only look for major failures, as there is no way to duplicate every persons use and or setup outside of D-Link.

Respectfully,

Tommy Lee...
Logged

DaveH

  • Level 1 Member
  • *
  • Posts: 10
Re: 1.31 Offical Release
« Reply #51 on: May 01, 2009, 12:59:46 PM »

Ok Lizzie555. I did a reset to manufacturer settings then manually configured wireless security. Although it has only been 10 minutes or so, all is well.

I am going to be positive and say this did the trick! If not, I will be sure to post. Thanks again for you help.

Are there any settings you guys suggest a nontechnical person like myself (but not afraid to learn and try) do to enhance this router's performance and capabilities?
Logged

desides

  • Level 1 Member
  • *
  • Posts: 9
Re: 1.31 Offical Release
« Reply #52 on: May 01, 2009, 01:06:14 PM »

I applied 1.31 to my DIR-655 A3, upgrading from firmware 1.21 in the process, and now my router reboots every single time it establishes a connection to my ISP. My DIR-655 goes through a 2wire 2701HG-B DSL modem which is set in bridge mode. I've had to remove my DIR-655 from the network entirely, and I'm using the DSL modem's wireless feature in the interim.

Did 1.31 screw my DIR-655?
Logged

unickz

  • Level 1 Member
  • *
  • Posts: 5
Re: 1.31 Offical Release
« Reply #53 on: May 01, 2009, 01:39:40 PM »

I am a novice user just looking for consistency. I have noticed since upgrading to 1.31NA my connection drops often. I checked with my Internet provider and they are not showing my modem dropping off. When it does it is for a few seconds and comes back quickly. It is most noticeable on my VoIP which is wired. It is constantly breaking up and has become unusable. My desktop is wired and drops out as well. This is noticeable while streaming Sirius.

Are there settings I need to adjust? Keep in my I am very inexperienced with this. Unless I can get help I will be forced to get a new router. That would be frustrating considering problems were brought on by a firmware upgrade. If I understand correctly, I cannot go back to an earlier firmware version?

WARNING TO THE DEAR READER:  OK, long post here so I can include some background details for you. I'm hoping this helps point out there are some issues in this firmware and compatibility with speed negotiation.

I understand exactly what DaveH has mentioned here.  The same thing happened to me with the upgrade.  I was actually a couple revisions behind on my 655 router (1.20) when I noticed my logs indicated DLink had firmware upgrades.  For now, I'm wired directly and have the wireless disabled.   I was very concerned about making the jump to 1.31 when it said "not reversible" (How dumb on my part for moving forward.  How REALLY dumb of Dlink for putting such a mess out there - debate this later).  

Something kept me from being able to hit the Net yesterday, so I had to reboot everything (modem, router, voip, computer) and started combing the logs of my router when it came back.  I found nothing indicating the trouble and attributed it to a lost modem carrier link from upstream.  (We had strong winds the previous evening, so maybe something happened to the lines along the way.)  I could see a message indicating there were firmware upgrades waiting from Dlink.  I was finally able to get thru to the Net and DLed both 1.21 (dir655_firmware_121_no_securespot.bin) and 1.31 (dir655_firmware_131.bin).  

I applied 1.21 first and no issues showed up, so I moved on.  My problem started immediately after the upgrade to 1.31.  My browser (firefox)  kept dropping back to a page telling me the router was testing the speed and that I should wait to avoid impacting the test.  Well, there was nothing I could do to it anyway and was forced to wait.  The login screen appeared for getting back into the router and I had a really hard time getting the correct letters/numbers on the new GUI addition before the "testing" page would come back up.  Each time the testing began, I would actually see the router reboot/reset itself (all the lights on the front panel would blink off and come back like a reboot).  I had my setting saved on my computer for the router, so I thought I needed to hit the "reset" button and get a clean start.  It didn't make a difference.  I finally had to disconnect the router from the modem to stop the testing so that I had a chance to get into the router interface.  

I looked for all the spots I could find to disable automatic speed testing.  I disabled the new security GUI feature first.  I ended up turning off the traffic shaping and automatic upllink speed testing and set a LOW manual uplink speed.  I'm using Road Runners Turbo package that is supposed to be 15M down/ 1-2 up, but I set the speed to really low (384Kbps).  I searched for other things I could turn off and think I even tried turning off the QOS engine completely.  This seemed to stop the problem, for now, and I could get back online.  It was important to get connection as my only phone right now is VOIP.  :-)

Finally got thru the extremely annoying front line RR support and got a 3rd leve guy to the phone.  We verified that my cable modem was the one model they had in the field that did NOT support turbo speeds (nice!! - never told me this 6 months ago when I upgraded to turbo) and I should return it for an upgrade.  Everything else tested fine along the line and they did not have any reported outages or issues for my area.  Hmmm.  Well, SOMETHING happened somewhere as I was dead Thursday.  Moving on, I was able to use the Net and VOIP for the rest of the evening and switched the modem out today.  

Intially I left the setting alone on the router and just tried to hit the Net.  Connections to a few sites worked ok.  Then I went back to using the traffic shaping and automatic uplink speed testing and I had my connections between the router and modem start acting up again.  The router wasn't restarting this time but I could see my network icon in the tray indicating I lost network connectivty to the modem.  Nothing would resolve in DNS for the websites (page not found) until I changed these settings and rebooted the router.  I am running now with the QOS engine back on, traffic shaping allowed,  but have manually set my uplink speed.

I know this was a long post, but I wanted to get this information out there so others can possibly explore the same thing.  Better yet, I hope Dlink admits they still have issues out there and need to address immediately.

Good luck, gang.

« Last Edit: May 01, 2009, 04:10:54 PM by unickz »
Logged
unix - it's what's for dinner

Lycan

  • Administrator
  • Level 15 Member
  • *
  • Posts: 5335
Re: 1.31 Offical Release
« Reply #54 on: May 01, 2009, 02:02:31 PM »

Unicks,
 You must understand that the problem that you're seeing is unique to you or even a small number of people and not likely a problem with the firmware.
If it was a problem with the firmware everyone that was using it, with RR-Turbo would see this issue, right?

As for your problem, I suggest resetting the unit to factory adn configuring it from scratch. If that doen't help contact technical support.
Logged

point

  • Level 2 Member
  • **
  • Posts: 47
Re: 1.31 Offical Release
« Reply #55 on: May 01, 2009, 02:54:47 PM »

just installed on my A3, and works fine.

But i have 2 questions:

- Does anyone know if the 3g suport will be 'recovered' (maybe on a EU version of this firmware, i'm in Portugal, and 3G Internet, is very used around here. I think is a bad decision to remove the support, at least on Europe)

- 1.1x firmware is related to A3 revision. 1.2x is related to A4 revision. With 1.3x are we expecting a A5 revision?
Logged

Toilet-Duck

  • Level 2 Member
  • **
  • Posts: 41
Re: 1.31 Offical Release
« Reply #56 on: May 01, 2009, 03:01:14 PM »

Im hoping the 3g option will be added back later too with the next firmware update, I sometimes take my router with me when I go away and use the t-mobile usb dongle to connect.


But this latest firmware for this is really stable havent had 1 crash and reboot since I updated it, use to keep needing a reboot every few days after I used it for a week but this latest firmware seems to fix it  :)
Logged

FrostyMelon

  • Level 1 Member
  • *
  • Posts: 9
Re: 1.31 Offical Release
« Reply #57 on: May 01, 2009, 03:17:56 PM »

^LOL! I guess you should have gone with 'USB Doohickey'.  ;)
Logged

unickz

  • Level 1 Member
  • *
  • Posts: 5
Re: 1.31 Offical Release
« Reply #58 on: May 01, 2009, 04:04:16 PM »

Unicks,
 You must understand that the problem that you're seeing is unique to you or even a small number of people and not likely a problem with the firmware.
If it was a problem with the firmware everyone that was using it, with RR-Turbo would see this issue, right?

As for your problem, I suggest resetting the unit to factory adn configuring it from scratch. If that doen't help contact technical support.


I guess u missed my point, Lycan, that was written above (even if it was lllllloooooonnnnnggggg):

I DID RESET and also reloaded my settings.  It had NO impact.  I had NO problem until I went to 1.31. This did not surface in the other versions.  Repeat:  I never saw anything like this until I uploaded 1.31. Is it a settings issue? Great, then school everyone on where we have it wrong.  No shame there.   It is not the fault of the modem as it was replaced (different model even) and the problem stayed. I got the problem to repeat with settings that were just fine before.   ???

I know this isn't just my issue as I see others here have described the SAME behavior.  Technical support has no interest in my case as I have no warranty / contract with them.  (Their position on the probelm, not mine).

This isn't the case of a "lost" user and single case just because not everyone hasn't see it (yet).  There are others who are reporting the problem and I know we are not all using the identical ISP and hardware.    :o  Break, coffee, discuss amongst yourselves.
Logged
unix - it's what's for dinner

desides

  • Level 1 Member
  • *
  • Posts: 9
Re: 1.31 Offical Release
« Reply #59 on: May 01, 2009, 04:12:52 PM »

I'm having almost the exact same issue as unicks is experiencing. This is not an isolated or unique issue.
Logged
Pages: 1 2 3 [4] 5 6 ... 9