ispalten
join:2005-04-16
Clermont, FL
| reply to ispalten
Re: DI-624 c - NEW FIRMWARE 2.75b2
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 |
|
tqhoang
join:2006-01-25
| 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 |
|
ispalten
join:2005-04-16
Clermont, FL
| 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 |
|
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 |
|
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; |
|
ycb
@cndata.com |  ?????
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; |
|
