DLink_Tech2
join:2002-12-23
Fountain Valley, CA
| DI-624 rev. C firmware 2.42 has been released.
Firmware 2.42 for the DI-624 revision C has been released and is available for download from D-Link's support and ftp sites.
»support.dlink.com
»ftp://ftp.dlink.com
This firmware:
- Resolved reboot issue when set to Super G with Dynamic turbo mode
- Resolved slow performance issue on WAN port |
|
SoCal99
join:2004-01-22
1 edit | WOW, dlink first to annouce new fw on their site, maybe pro-active information is on the horizen?
Ok here goes, Dlink_Tech2 are any of the bugs reported in 2.37 fixed in 2.42? Please respond with a yes or no. And if yes, which ones?
Thanks
»Known Issues with 2.37 Firmware and DI-624 |
|
SoCal99
join:2004-01-22
| reply to DLink_Tech2
Ok, just installed it using the crash recovery method. Too soon to give a complete report but at least all computers on the network have internet access and can access each other on my LAN (something that hasn't always been the case after a fw upgrade).
When I played my phone messages, the 624 did not reboot. But only time will time as other fw upgrades have stopped the reboots (caused by the phone) temporarily only to have them come back within a few hours.
Will keep you posted. |
|
Anthony2816
join:2003-12-04
Oakdale, CA
| I just installed the new firmware, and the first thing I noticed was that it erased all my settings. Would I be correct in assuming that using my configuration backup file, made with firmware 2.28, would not be a good idea? I just need to re-enter all my settings and rules? |
|
peepoop
join:2004-02-27
Anaheim, CA | reply to DLink_Tech2
Wow dude.
Whether it fixes the problem or not, it sure is nice to see a line in the changelog that starts out with "- Resolved reboot issue..." for a change.
Can't wait to try it tonight! |
|
Anthony2816
join:2003-12-04
Oakdale, CA | 1. Well, it seems like you can't reload a configuration file made from the 2.28 firmware. It just says "bad checksum".
2. Thus far, the updater for dynamic dns (dyndns.org) doesn't seem to work, although it did under 2.28. |
|
bcronin
Premium
join:2004-03-27
Hyde Park, NY
| reply to DLink_Tech2
Installed fine. Settings were not cleared. But the uPnP problem introduced in 2.41 is still there. Router no longer accessible via My Network Places. But thats minor. Will watch for reboots, etc.
Any hope of this ever working properly with the G800AP? |
|
Anthony2816
join:2003-12-04
Oakdale, CA | Hey, not fair...how come my settings were cleared, and yours weren't?
Maybe because I was updating from an older firmware (2.28)? |
|
rrfirst
join:2002-05-18
Apache Junction, AZ | I just upgraded from 241 and all my setting stayed |
|
rp_guy
join:2001-06-19
Canada | reply to DLink_Tech2
seems from 2.36 up the settings will stay |
|
Anthony2816
join:2003-12-04
Oakdale, CA
| Oh well, no biggie....they're all typed in again.
AND the dyndns updated suddenly started working, so that's cool.
Question, though: I noticed that since upgrading to 2.42, under the Firewall settings, there are two settings that I didn't add, and don't particularly want:
Name: msmsgs (192.168.0.6:13661) 6245
Action: Allow
Source: WAN,*
Destination: LAN,192.168.0.6
Protocol: UDP,13661-62453
Name: msmsgs (192.168.0.6:13661) 6245
Action: Allow
Source: WAN,*
Destination: LAN,192.168.0.6
Protocol: TCP,8961-45027
These two entries can't be deleted or edited. Anybody know what they are, where they came from, and how (or whether) to get rid of 'em? |
|
DLink_Tech2
join:2002-12-23
Fountain Valley, CA
| Those firewall entries are generated by the UPNP settings being enabled. If you use MSN Messenger with UPNP enabled, the router will automatically open the ports MSN Messenger needs to work properly. You can disable UPNP on the Tools>Misc. page of the router. |
|
jatman
join:2004-01-29
Seattle, WA
| reply to Anthony2816
Try turning UPNP off and then deleting these firewall settings. I think that 'tweaks' to the firewall which are created via UPNP are protected against inadvertent deletion by everyone. So tell the router you don't want UPNP-enabled applications and you can rid yourself of the ones that crept in while the door was left unlocked.... |
|
jonazen
Be Like Water My Friend
Premium
join:2004-02-18
Princeton Junction, NJ
 ·T-Mobile VoIP
| OK - closed my eyes and went for it. Just loaded 2.42 on top of 2.41 (didn't bother with the "crash recovery" routine first, and didn't have to do it with 2.41 either - last time I did it was with 2.37).
Loaded up fine, kept my settings from 2.41. All machines and printers on the LAN are visible and can happily browse each other - all reconnected just about instantly when the router rebooted itself after the upgrade. Internet access is fine - just did a download test via CNET's bandwidth meter, and appear to be getting about 2.7 mbps via Comcast cable through the DI-624. Consistent speed on wired and wireless pc's to CNET's test site.
So far, so good. 2.41 was working pretty well for me - prior to the upgrade tonight, it had been up and running without a reboot for 5 days straight. We'll see how 2.42 does over the next week.
- Jon
--
-- Jonazen -- |
|
Anthony2816
join:2003-12-04
Oakdale, CA | Thanks for the uPNP info. Will go play with it. |
|
Anthony2816
join:2003-12-04
Oakdale, CA
| reply to DLink_Tech2
So far in the last couple of hours I've had two random disconnects/reconnects under the new 2.42 firmware (I guess these are called DHCP disconnects, since all the computers on the LAN popped up warning balloons from their WinXP network icons in the system tray).
Never had any with the Netgear router the DI-624 replaced. |
|
Pla
join:2004-02-25
Sunnyvale, CA
| reply to Anthony2816
I already posted in the first thread but will post here again.
Updated ok.
I tried dynamic-turbo since something in it was fixed...
And guess what my phone doesn't reboot the router anymore!
Have to wait to be sure...
Another thing. Dynamic-turbo works more like a turbo now.
When connected the G650 stays at 54 mbps but when I try to copy large file in the net the connection automatically goes up to 108 mbps - on demand which is great. |
|
avakil
join:2003-03-10
Flushing, NY
| reply to DLink_Tech2
I'm on 2.41 right now and I'm too scared to upgrade to 2.42. I'll wait till I feel a little more daring to upgrade. Or wait till I'm bored and want a problem to fix, maybe then i'll upgrade. For now, I'm happy with 2.41, works pretty damn well.
-Arash |
|
Pla
join:2004-02-25
Sunnyvale, CA
| Well it still reboots on phone calls just not as often - before it was every 6-7 seconds and now it reboots 3-4 times on every 7 seconds and then it works for 30-40 seconds... and then it reboots again... and so on...
Switched back to no turbo. |
|
tcho1
@adelphia.net | same thing happens to me... it didn;t happen with 2.37... but neither did wireless... turning turbo off... |
|
