JTS33
join:2003-05-03
USA | reply to Ali Baba
Re: DI-624 c - NEW FIRMWARE 2.75b2
Can you disable UPnP with the new firmware 2.76b05 without the router randomly rebooting? |
|
Ali Baba
@pppool.de
| reply to JTS33
Salam,
Dl 624Cx yes the new Firmware 2.75b2 is still Bullshit!
But now theres a newer one, no crashes, no wireless problems,
real good on peer to peer tools aso.
Try it and you will be happy too.
So take the Firmware 2.76b05 right here:
»www.dlink.de/?go=jN7uAYLx/oIJaWV···YxVI5HU=
Direkt Download: »www.dlink.de/?go=gNTyP9CnptFMIC4···unfZfQ==
its only for Dl 624Cx and Dl 624Hx
Greetings Lucky Ali |
|
gsperkins
join:2006-08-01 | reply to JTS33
Yes, I cannot disable SSID broadcast... I have tried just about every combination in the menu... can't get it to take. |
|
ycb
@cndata.com |  reply to ycb
?????
function set_channel(){
var channel_list = "6";
var current_channel = 6;
var ch = channel_list.split(",");
var obj = get_by_id("channel");
var count = 0; |
|
ycb
@cndata.com |  reply to ispalten
function set_channel(){
var channel_list = "6";
var current_channel = ;
var ch = channel_list.split(",");
var obj = get_by_id("channel");
var count = 0; |
|
ispalten
join:2005-04-16
Clermont, FL
1 edit | reply to krick
said by krick  :said by ispalten :Basically, the computer requests a new IP address via DHCP, and the router always doles out the same (reserved) IP address. I always make sure that the fixed address I choose is outside the range that is normally allocated via DHCP but I'm not sure that's really necessary. For example, my DHCP pool is 192.168.0.100 through 192.168.0.255. I have 3 machines on my network that are assigned fixed IP addresses by the router: 192.168.0.8, 192.168.0.16, and 192.168.0.32. Every machine is still set up with a dynamically assigned IP address in its network settings. [/BQUOTE ] Yes, that is what I had been doing, using the MAC address to assign IP address always to the same one. However, with the latest firmware that is problematic. Worked fine under 2.71b11 but not the lastest. Matter of fact, when I set one up (all show as unknown in 2.75B) the other disappeared for a period of time. Later when I rebooted my setting was gone as well. Under 2.71 is stays and works. Irv --
Irv Spalten |
|
krick
join:2002-04-09
Merchantville, NJ
| reply to ispalten
said by ispalten :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? If you want your computer to always be 192.168.0.100, leave the PCs DHCP *ON* and tell the router to always assign 192.168.0.100 to your computer's mac address.
Basically, the computer requests a new IP address via DHCP, and the router always doles out the same (reserved) IP address.
I always make sure that the fixed address I choose is outside the range that is normally allocated via DHCP but I'm not sure that's really necessary.
For example, my DHCP pool is 192.168.0.100 through 192.168.0.255. I have 3 machines on my network that are assigned fixed IP addresses by the router: 192.168.0.8, 192.168.0.16, and 192.168.0.32. Every machine is still set up with a dynamically assigned IP address in its network settings. |
|
ispalten
join:2005-04-16
Clermont, FL
| reply to tqhoang
said by tqhoang :1. Have you had these constant reboots with other firmwares before this one? For what it is worth, like I said, I went back to the older Beta, and here is the Connection Monitor data since I went back.
=========
Up Time: 22:16:39 Boot: Saturday 7/8/2006 11:03:43 AM
WAN IP: 70.121.179.80 DNS: 65.32.5.74, 65.32.5.75 Network: {1}
Model: DI-624 Firmware: 2.71, Mon, 3 Oct 2005 Address: 192.168.0.1
========
Almost 1 day running without a reboot. With the newest Beta I never got more than a few hours, and usually less than 1 before it rebooted.
--
Irv Spalten |
|
ispalten
join:2005-04-16
Clermont, FL
| reply to tqhoang
said by tqhoang :I don't believe you show up in the list since it seems to be generated via DHCP requests. Unless the DI-624 is doing some kind of Reverse ARP (RARP), it won't be able to figure out a name for your statically assigned box. Also you said it's able to ping, nslookups, and traceroute's, so you're fine. It seems that given enough time it comes up and is recognized. I've given up on this version and went back to the B11 versions. It seems it too has 'unknown' as the name of the machine.
--
Irv Spalten |
|
ispalten
join:2005-04-16
Clermont, FL
| reply to tqhoang
said by tqhoang :1. Have you had these constant reboots with other firmwares before this one? Not the last one, the B11 version. It was usually solid for days on end.
said by tqhoang :2. With your wireless clients, do you see any other access points using channel 6 in the area? Not using wireless, only hardwired at this time. It didn't seem to matter if wireless was on or off.
--
Irv Spalten |
|
tqhoang
join:2006-01-25
| reply to ispalten
This is someone on the outside trying to access the TCP and UDP ports on your router. This is very common with bots & script kiddies out on the Internet. Your router is doing the right thing and blocking them.
You should just turn off most of the logging since it will just fill up with this stuff.
1. Have you had these constant reboots with other firmwares before this one?
2. With your wireless clients, do you see any other access points using channel 6 in the area?
--
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 |
|
tqhoang
join:2006-01-25
| reply to ispalten
I don't believe you show up in the list since it seems to be generated via DHCP requests. Unless the DI-624 is doing some kind of Reverse ARP (RARP), it won't be able to figure out a name for your statically assigned box.
Also you said it's able to ping, nslookups, and traceroute's, so you're fine. |
|
ispalten
join:2005-04-16
Clermont, FL
| reply to ispalten
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 |
|
ispalten
join:2005-04-16
Clermont, FL
| reply to JTS33
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 |
|
JTS33
join:2003-05-03
USA
| 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. |
|
JTS33
join:2003-05-03
USA
| 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. |
|
ispalten
join:2005-04-16
Clermont, FL
| 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 |
|
ispalten
join:2005-04-16
Clermont, FL
| 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 |
|
JTS33
join:2003-05-03
USA
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. |
|
JTS33
join:2003-05-03
USA
2 edits | reply to 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?
My current wireless settings: SuperG without Turbo, Channel Auto Select off, Extended Range Mode disabled, WMM disabled, 802.11g only Mode enabled, WPA2-AES |
|
