 peter_mPremium
join:2005-07-13
Canada, QC
1 edit | DI-624 c - NEW FIRMWARE 2.75b2 »support.dlink.com/products/view.···4%5FrevC
It's got a big BETA warning so they are not responsible for it trashing your router.... Has anyone tried it? 
Was it only to fix this: »Remotely Exploitable Vulnerability In All D-Link Gateways ? |
|
|
|
 Talon88 The One
join:2003-08-13
Toronto | :::
Want to try, but the Config.bin setting file of
the last few version is not compatible
with this version. Back to v2.71B10 again....!
Anyone tried please post feed back....!
::: |
|
1 edit | reply to peter_m
I pulled out the old 624 yesterday just to test this firmware... I gave up on it because of the random reboots with all previous firmwares. I've only used it with one PC so far (don't want the whole house to kill me if the internet gets flaky), but it hasn't rebooted yet. Running with WEP and WMM and no superg. Maybe after all these years, they got it right?? The menus are also cleaner (no html errors or spacing where it shouldn't be).
F/W = 2.75, Build:0002 Date = Thu, 29 Jun 2006 CPU BSP: ar531x_wmm, 4.0.0.58, Apr, 25, 2006, build 0011 DRIVER: 1.0.0.0126, Jun, 28, 2006, build 0126 STACK: 1.0.0.1692, Jun, 27, 2006, Build 1692 AR5 WLAN MAC = ff-ff-ff-ff-ff-ff AR5 F/W = ar531x_wmm, 4.1.2.56, 12:00, 28 Jun, 2006, Build 1083 AR5 Domain = 0x10, FCC1_FCCA AR5 SSID = adlkjiosd Watch Dog = 1 Restore Default = 0 Checksum = 0x06332fe4
As you can see, everything is at least a half year newer than the previous firmware... it's definitely better than anything else before it, give it a try.
-- I just tested and the exploit is now gone. Jumpstart is gone (thank God). Automatic NTP appears to want a customized server (time.windows.com worked fine). Default SSID is now dlink. It's like an updated 2.59 firmware more or less (wmm on wireless page, no jumpstart, ddns works, more stable). |
|
| Wireless Settings is full of bug.  |
|
| said by di-624 :Wireless Settings is full of bug. Can you explain this a little better? |
|
| It is totally unconfigurable. I have reset the router. I have to disable the wireless function. Maybe I should try the Crash Recovery procedure. |
|
peter_mPremium
join:2005-07-13
Canada, QC
2 edits | reply to effortless
Any idea if the Intel and Broadcom client problems of the 2.70 firmware was fixed?
Can we now disable UPnP as well? |
|
| reply to di-624
said by di-624 :
It is totally unconfigurable. I have reset the router. I have to disable the wireless function. Maybe I should try the Crash Recovery procedure.
It seems mine reset the config settings to default after I loaded it. I was using 2.71b11 firmware, so maybe that's why I didn't have any problems.
At the very least, reset the router to defaults.
--
M$ WinXP Pro SP2 + WPA2
D-Link DI-624 revC3 Fw 2.71b11
D-Link DWL-G520 revB3
D-Link DWL-G650 revB5
NETGEAR WGT624v2 Fw 4.2.10
NETGEAR WG511T
NETGEAR WG311T |
|
| reply to peter_m
said by peter_m:Any idea if the Intel and Broadcom client problems of the 2.70 firmware was fixed? Can we now disable UPnP as well? My Intel 2915ABG with driver package v10.1.1.3 connects fine using WPA or WPA2 (both with AES; untested with TKIP but I assume that works fine).
It seems the WPA2-Auto mode is no longer and option...and it doesn't work as a hidden feature of WPA2. The clients need to support WPA2 if you have that selected. Before with WPA2-Auto you could connect using WPA, but maybe that was causing the problems I had.
I'll have to disconnect my laptop for a few days to see if my WPA2 connection problems resurface. If you don't recall, after like 2+ days of not using the wireless, my laptop would authenticate, but would never get a DHCP IP address unless I manually rebooted the router.
Also I haven't disabled UPnP yet.
--
M$ WinXP Pro SP2 + WPA2
D-Link DI-624 revC3 Fw 2.71b11
D-Link DWL-G520 revB3
D-Link DWL-G650 revB5
NETGEAR WGT624v2 Fw 4.2.10
NETGEAR WG511T
NETGEAR WG311T |
|
| I applied the latest Beta and it seems both stable and I swear faster?
However, version 1.7.95 of the Connection Monitor seems to have a problem with it...
----------
Up Time: 0:55:52 Boot: Thursday 7/6/2006 3:49:50 PM
Network: {2} (Could not get other router info: 401 Unauthorized)
----------
I do have a P/W and I need it to get into the web page, but it doesn't work with the monitor?
Irv
--
Irv Spalten |
|
| The Connection monitor is working correctly, I didn't set the correct P/W which was wiped out by the flash.
The flash is NOT stable for me. I've been having constant reboots. I'm suspect about some settings, under TOOLS, MISC. I've got
=========
Block WAN Ping Disabled
UPNP Settings Disabled
Gaming Mode Disabled
VPN Pass-Through
PPTP Disabled
IPSec Disabled
Multicast Streams Enabled
==========
Don't use VPN so I'm pretty sure the last 2 shouldn't be an issue.
I have the DNS Relay on, and that should be I think?
I didn't check what I had before I flashed however, so it could be different.
I'm hard wired right now, and these are the settings for Wireless
=======
Super G Mode : SuperG with Dynamic Turbo
Extended Range Mode : Disabled
WMM Function (Wireless Qos): Disabled
802.11g Only Mode : Enabled
SSID Broadcast : Enabled
Security : WPA
Cipher Type: TKIP
PSK / EAP: PSK
========
Anything I should change or that might effect stability?
Here is my latest UPTIME
=====
Up Time: 0:25:22 Boot: Thursday 7/6/2006 8:48:27 PM
WAN IP: 70.121.179.80 DNS: 65.32.5.74, 65.32.5.75 Network: {2}
Model: DI-624 Firmware: 2.75, Thu, 29 Jun 2006 Address: 192.168.0.1
======
I only get about 1 hour max between reboots.
--
Irv Spalten |
|
| said by ispalten:UPNP Settings Disabled Gaming Mode Disabled Enable both of these settings. In particular, disabling UPnP causes reboots in previous firmware versions for many DI-624 Rev. C3 owners. I was hoping this would be fixed in this new firmware, but I guess not? |
|
2 edits | I just updated from 2.71b11 to 2.75b2
I noticed that SSID Broadcast can't be disabled...it'll always revert to enabled. Anyone else notice this?
My current wireless settings: SuperG without Turbo, Channel Auto Select off, Extended Range Mode disabled, WMM disabled, 802.11g only Mode enabled, WPA2-AES |
|
1 edit | reply to effortless
said by effortless:I just tested and the exploit is now gone. Which DI-624 firmware version were you able to take advantage of the exploit?
I thought someone else had posted that they weren't able to do the exploit on their DI-624. |
|
| reply to JTS33
said by JTS33:I just updated from 2.71b11 to 2.75b2 I noticed that SSID Broadcast can't be disabled...it'll always revert to enabled. Anyone else notice this? Just tried this, you are right. Stays on. Was this little warning, "*Enabling Extended Range Mode will not allow to disable SSID Broadcast mode." there on prior firmware?
--
Irv Spalten |
|
| reply to JTS33
said by JTS33:said by ispalten:UPNP Settings Disabled Gaming Mode Disabled Enable both of these settings. In particular, disabling UPnP causes reboots in previous firmware versions for many DI-624 Rev. C3 owners. I was hoping this would be fixed in this new firmware, but I guess not? I did have these ON before and was continually rebooting. I reset them to ON again and I'll keep track.
-------
Up Time: 0:01:22 Boot: Friday 7/7/2006 6:16:31 AM
WAN IP: 70.121.179.80 DNS: 65.32.5.74, 65.32.5.75 Network: {1}
Model: DI-624 Firmware: 2.75, Thu, 29 Jun 2006 Address: 192.168.0.1
-------
We'll see how long it stays up I guess.
--
Irv Spalten |
|
| reply to ispalten
said by ispalten:said by JTS33:I just updated from 2.71b11 to 2.75b2 I noticed that SSID Broadcast can't be disabled...it'll always revert to enabled. Anyone else notice this? Just tried this, you are right. Stays on. Was this little warning, "*Enabling Extended Range Mode will not allow to disable SSID Broadcast mode." there on prior firmware? Yes it was. There must be another setting that forces SSID Broadcast mode to be enabled in this new firmware. |
|
| reply to ispalten
said by ispalten:said by JTS33:said by ispalten:UPNP Settings Disabled Gaming Mode Disabled Enable both of these settings. In particular, disabling UPnP causes reboots in previous firmware versions for many DI-624 Rev. C3 owners. I was hoping this would be fixed in this new firmware, but I guess not? I did have these ON before and was continually rebooting. I reset them to ON again and I'll keep track. Let us know how it goes. I've been up 24 hours with the new firmware without a reboot so far (UPnP enabled). I will try disabling UPnP to see if that causes a reboot. |
|
| said by JTS33:Let us know how it goes. I've been up 24 hours with the new firmware without a reboot so far (UPnP enabled). I will try disabling UPnP to see if that causes a reboot. It is getting worse with it enabled, more frequent boots.
Not only that, I now find some 'real' problems.
Although there are 3 computers on the network, only 2 are usually on. Mine and my wifes. I usually turn mine on first as I'm up earlier. Last night she turned hers on while mine was off andleft hers on and I couldn't get connected this morning. Why? Because since I use FTP and NETMEETING occasionally, I've set my network connection to always be 192.168.0.100. Hers was DHCP, whatever it gets. We hit a conflict as hers was on overnight. Not a problem, I was able to set hers to be 192.168.0.101 and I can get reconnected. However, the ROUTER doesn't see me at all? I noticed this prior to today with the new flash firmware, as it showed my name as UNKNOWN but I did see the MAC address clone and set it to me, but didn't give it much though. On the HOME, DHCP page only her system shows now?
================
Static DHCP Client List
Host Name IP Address MAC Address
LaraineP4 192.168.0.101 00-e0-18-55-52-87 editdelete
Dynamic DHCP Client List
Host Name IP Address MAC Address Expired Time
LaraineP4 192.168.0.100 00-e0-18-55-52-87 Jul/15/2006 06:57:53
================
Note the different IP addresses for LARAINEP4, the one 192.168.0.100 is IRVS, not LARAINEP4. This is the STATUS, LOG entries, complete...
===========
page 1 of 1
Time Message Source Destination Note
Jul/08/2006 06:58:06 DHCP lease IP 192.168.0.100 to LaraineP4 00-e0-18-55-52-87
Jul/08/2006 06:57:21 DHCP lease IP 192.168.0.100 to LaraineP4 00-e0-18-55-52-87
Jul/08/2006 06:57:08 DHCP Request success 70.121.179.80
Jul/08/2006 06:57:08 DHCP Request 70.121.179.80
Jul/08/2006 06:57:07 DHCP Discover
Jul/08/2006 06:57:07 System started
Jul/08/2006 06:57:00 AP 2.4GHz mode Ready. Channel : 6 TxRate : best SSID : dlink
Jul/08/2006 06:57:00 Access point: dlink started at channel 6.
===========
How could I not show (I'm on IRVS right now typing this)? LARAINEP4 is at 192.168.0.101 right now and I'm 192.168.0.100. I tired clearing the log and it clears, but NO NEW entries appear? It is like it isn't working?
Proof I'm connected however.
==========
c:\>net view
Server Name Remark
---------------------------------------------
\\IRVS Irv's Gen 5
\\LARAINEP4 P4 Sony - PCV-RX650
The command completed successfully.
c:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : IrvS
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection 4:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Cont
roller
Physical Address. . . . . . . . . : 00-12-3F-6B-9D-F2
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
=============
How can this be?
From the Connection Monitor
Up Time: 0:18:15 Boot: Saturday 7/8/2006 6:56:35 AM
WAN IP: 70.121.179.80 DNS: 65.32.5.74, 65.32.5.75 Network: {2}
Model: DI-624 Firmware: 2.75, Thu, 29 Jun 2006 Address: 192.168.0.1
Suggestions? I do feel this firmware IS FASTER, but it is annoying. With the older version I had the three machines set up to different IP addresses by MAC address. This version doesn't seem to see my computer's MAC address as IRVS but it was showing as UNKNOWN. Today, even that doesn't show, only LARAINEP4 is available? Even then, LARAINEP4 is listed as my IP address even though it has a different one?
I released and renewed the DHCP lease and that changed in the log. On the HOME, DHCP tag I did APPLY and it changed the data,
-----------------
Static DHCP Client List
Host Name IP Address MAC Address
LaraineP4 192.168.0.101 00-e0-18-55-52-87 editdelete
Dynamic DHCP Client List
Host Name IP Address MAC Address Expired Time
unknown 192.168.0.100 00-12-3f-6b-9d-f2 Jul/15/2006 07:24:17
---------------
However, I still do NOT show? I can PING and it works and resolves addresses, so does TRACERT? Why don't I show in the list to assign IP addresses?
Distressing to say the least? I've enabled all the LOG settings, maybe this will show something?
Anyone else see something similar?
--
Irv Spalten |
|
| This seems to be getting worse now. I decided after seeing many DROPPED PACKETS in the log after enabling all options to do a RESET to factory default settings via the TOOLS, SYSTEM MENU.
Ah hah! Both computer MAC Addresses now show with UNKNOWN as the name. Cloned LARAINEP4 and replaced UNKNOWN with it and pressed APPLY. That took, but IRVS (my machine) disappeared from the DHCP list...
Also, in the LOG see these...
==========
Time Message Source Destination Note
Jul/08/2006 09:49:09 Drop TCP packet from WAN 65.32.5.46:110 70.121.179.80:60007 Rule: Default deny
Jul/08/2006 09:48:08 Drop TCP packet from WAN 65.32.5.46:110 70.121.179.80:60007 Rule: Default deny
Jul/08/2006 09:47:46 Drop TCP packet from WAN 148.129.75.160:80 70.121.179.80:60093 Rule: Default deny
Jul/08/2006 09:47:06 Drop TCP packet from WAN 65.32.5.46:110 70.121.179.80:60007 Rule: Default deny
Jul/08/2006 09:46:40 Drop TCP packet from WAN 148.129.75.160:80 70.121.179.80:60093 Rule: Default deny
Jul/08/2006 09:46:05 Drop TCP packet from WAN 65.32.5.46:110 70.121.179.80:60007 Rule: Default deny
Jul/08/2006 09:45:35 Drop UDP packet from WAN 204.16.208.103:46622 70.121.179.80:1027 Rule: Default deny
Jul/08/2006 09:45:35 Drop UDP packet from WAN 204.16.208.103:46622 70.121.179.80:1026 Rule: Default deny
Jul/08/2006 09:45:34 Drop TCP packet from WAN 148.129.75.160:80 70.121.179.80:60093 Rule: Default deny
Jul/08/2006 09:45:20 Drop TCP packet from WAN 70.97.18.28:3907 70.121.179.80:1433 Rule: Default deny
and many more too...
-----------
I can't find any reason for this? Nothing on ADVANCED, FILTERS, FIREWALL, or VIRTUAL SERVER seems to be the cause of this blocked. My system firewall doesn't report anything wrong either? Where are these set?
--
Irv Spalten |
|
