  Peter in NJ
@optonline.net
| [Firmware] 2 hr fix???? N1 Vision firmware for US v2000 availabl
Has anyone tried the new firmware (2.00.04) for the US N1 Vision hardware v. 2000 that came out recently? The UK version 2.00.04 supposedly fixes the 2 hour disconnect, so if we're lucky the US version of the same number may do the same thing. The US 2.00.04 download page (just saw today it has the new firmware) has no release notes!
Maybe the long-awaited firmware is here, but curious if anyone has tried it or asked Belkin whether it fixes the 2 hour disconnect?
Mine has been very stable with 2.00.03. Since the last restart (months ago) it has not disconnected (after killing the ntp task in the secret page on the console - the trick that is posted all over the net). It would be nice not to have to kill the task after power outages or other things that force a reboot. Other than that the router is remarkably stable and consistent. I hardly ever use the LCD features, but for performance alone I am happy for the price I paid (used a $30 coupon).
Anyway, looking forward to feedback from anyone who has tried the newest firmware (2.00.04) for the US v.2000 N1 Vision |
|
  PeterinNJ
@optonline.net | Re: [Firmware] 2 hr fix???? N1 Vision firmware for US v2000 avai
Judging by the lack of responses, I assume nobody (or at least nobody who has read this thread) has tried this new firmware (2.00.04) for the US N1 Vision hardware v.2000 yet? |
|
 mikeypas5
join:2005-05-07 Westmount, QC | reply to Peter in NJ Also curious to know anyone's experience or any release notes for the 2.00.04 firmware. things for me are working fine, so im hesitant to update. also, when i go to router's interface and check for new firmware, it says no new firmware.. weird |
|
  PeterinNJ
@optonline.net
| reply to Peter in NJ BAD NEWS: It appears this firmware (v. 2.00.04 for hardware v. 2000)) may NOT fix the 2 hour timeout issue: A gentleman over the phone a week or two ago told me it reportedly did fix it, but he may have misunderstood or been reciting a fix for the specific issue I mentioned, although one would wonder why. I got a written confirmation of the fixes the firmware has. There is a reference to a 2 hour disconnect fix, but it is for pptp (type of VPN I believe) - see below. I then asked if the ntp server issue was fixed and he replied that in that regard just the pptp issue was fixed.
"Fixed below bugs:
1. pptp session will drop after 2 hours
2. nvram conflict issue."
Too bad that they still didn't fix the 2 hour disconnect issue considering it affects all owners of v.2000! I suspect that many users don't notice it since it reconnects automatically and you have to be actively using the connection to even notice it... Still can't understand how they can just leave this issue unresolved for this long.
That being said, I have not had one wireless disconnect in what seems like a few months (after applying the workaround - killing the ntp task via the hidden page that is documented). So other than this one issue, I am very happy with the router and plan to keep it for a while to come. |
|
  PeterinNJ
@citicorp.com
| reply to Peter in NJ Interestingly someone (see second to last post on page 3 of the thread linked below) tested firmware v2.00.04 for the UK version of this router a while ago and says it fixes the issue. Hmmm. Not sure whether v2.00.04 for the UK version is the same as the US one.
»[Problem]Belkin N1 Vision: disconnects on a 2-hour intereval
If anyone has a copy of v.2.00.03 lying around and IF one can revert to older versions, I would be inclined to test v.2.00.04 to see if it resolves the issue. The caveat is that mine has worked so well (with the ntp task killed manually) and for so long that I am very hesitant to upgrade if I can't go back - I have literally not had a single wireless drop (I play online games - poker to be more specific - where it is virtually impossible to miss a wireless connection drop even it it reconnects automatically within a minute) in well over a month. In that sense, applying the workaround once or twice a year is not a big deal, even if they really should fix it... |
|