D-Link Forums

The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: lotacus on February 28, 2009, 06:21:04 PM

Title: some bugs
Post by: lotacus on February 28, 2009, 06:21:04 PM: 1.
Editing a policy already created, will not allow you to edit the details in step 2. ie: Details: Always. I want to put my own detials in there. IE: Allow Web browsing.

2.
Problem: When A Wireless client has a statically assigned ip address, the wireless status page shows the IP address as 0.0.0.0. As well, when a Wired client has a statically set IP address, it will NOT show up under LAN computers or anywhere else for that matter. A simple RARP to resolve the MAC address to the IP address and then resolving the IP address to a host name, would be beneficial. At the very least, resolving the MAC address to an IP address. This would heavily rely on the ARP table so it's ARP cache would have to be cleared I would guess.
(http://hpzdfa.bay.livefilestore.com/y1pntMDeCAGQjITGp-qUjbfOKGD5PZRA6TnJXq4fBA2QiEM81aMesutx9iVovr4FlcIzXnWAmfW6DA/wlan%20clients.PNG)

3.
After flashing the router, and despite doing several hard resets and power cycles, a RULE for Virutal Servers list STILL remains. Even when I drown the router in the bath tub!

(http://hpzdfa.bay.livefilestore.com/y1ptLqzadYMgKbx0Vkrb4_3Be1Gxsaqux6vZy8k7eEBP7Vt3BQyb2c5NJo9l9MOBbz8AwJRI9jBdFs/v_server.PNG)
4.
THE DANG LOGS

Seriously. After applying a web only rule to the router, it's logging ALL the incoming traffic that is now being blocked even though logging for that rule is disabled, because the router cannot make a connection to the computer to where those destinations are supposed to be reached because THEY ARE BLOCKED. Now, because of that the router's performance is TERRIBLE, and the logs stop at 2000 log entries, which I would assume it starts over writing.

Can you PLEASE include the option to disable logging all together (both logs and internet sessions). As well to limit the log entries as well as only log CERTAIN entries NOT just applying a filter to them. I do NOT want to go into the router every 3 minutes to "clear" the log.
Title: Re: some bugs
Post by: EddieZ on March 01, 2009, 03:26:49 AM: Quote
Seriously. After applying a web only rule to the router, it's logging ALL the incoming traffic that is now being blocked even though logging for that rule is disabled, because the router cannot make a connection to the computer to where those destinations are supposed to be reached because THEY ARE BLOCKED. Now, because of that the router's performance is TERRIBLE, and the logs stop at 2000 log entries, which I would assume it starts over writing.
Just curious how you connect this feature to the terrible performance of the router? My logs are full eventually but hasn't reduced the performance in any way. The log is not overwritten but completely cleared when full (fresh start).

Quote
Can you PLEASE include the option to disable logging all together (both logs and internet sessions). As well to limit the log entries as well as only log CERTAIN entries NOT just applying a filter to them. I do NOT want to go into the router every 3 minutes to "clear" the log.
I guess you missed the checkmark option in the log screen which turns logging for those specific items on/off. You seem to want to filter out some very specific logging which is not possible with these option. There are also some things I want to lose from the logs without losing other reports, but they're in the same group. Bad luck, I realize that Dlink can't individualize the router to that extend without customized firmware (there is always somebody not happy ;D )
Title: Re: some bugs
Post by: lotacus on March 01, 2009, 04:42:55 AM: A checkmark to enable logging? That certainly is not an option available. They only one that I think you are speaking of is the logging to a syslog server or emailing the log.

The router is set up very basic. wired devices in the ports, WAN port connecting out to PPoE. It only happens when allowing only web browsing in a rule and the clients are trying to torrent. In this particular case, when the rule was created, someone was already torrenting.

I suppose that would have been due to the fact that hundreds of other torrent clients where already aware of the connetion and then retrying. Dunno. But it pee'd me off a little.
Title: Re: some bugs
Post by: EddieZ on March 01, 2009, 04:48:42 AM: Howe about actually looking on the page? http://192.168.0.1/Status/Logs.shtml

There's a header saying "LOG OPTIONS"

Just uncheck the items. If you evidence that turning these 'view' options off actually does not stop logging I'd like to see it.
Title: Re: some bugs
Post by: lotacus on March 01, 2009, 06:37:48 AM: yes, that's filtering out what's already been generated.
Title: Re: some bugs
Post by: EddieZ on March 01, 2009, 07:40:53 AM: How can you tell the logging for those items isn't halted?
Title: Re: some bugs
Post by: lotacus on March 01, 2009, 08:37:48 AM: Your right. No one could tell if it's halted because we removed the check mark to untrap the messages, so we wouldn't see the log.

If a tree fell in the forest and no one was around to hear it, does it make a noise? :P

The only way would be to telnet into the device (which isn't possible).
Title: Re: some bugs
Post by: EddieZ on March 01, 2009, 08:52:50 AM: Quote from: lotacus on March 01, 2009, 08:37:48 AM
Your right. No one could tell if it's halted because we removed the check mark to untrap the messages, so we wouldn't see the log.

If a tree fell in the forest and no one was around to hear it, does it make a noise? :P

The only way would be to telnet into the device (which isn't possible).

Let's see what the Dlink guys have tosay about this one. If they are still around... ???
Title: Re: some bugs
Post by: bluenote on March 01, 2009, 11:15:41 AM: I believe this does (although its shoddy labeling, mind you) halt the logging (or at least, some options do).
The way I verified this in the past was to turn it off, wait, refresh, see no entries, turn it on, refresh.

The end result would be that even with changing the 'view' settings, those entries in the log would be lost permanently, not just temporarily invisible.

I have no evidence but I also have a suspicion that sending spam to the logs will slow down the router.
It logs too much crap anyways IMHO.
Title: Re: some bugs
Post by: EddieZ on March 01, 2009, 01:18:36 PM: LMAO
Usually the complaints are the other way around
Title: Re: some bugs
Post by: lotacus on March 01, 2009, 05:11:01 PM: Well, I think they should remove logging all together. If someone wants it they can purchase a 800 switch. haha. inside funny.
Title: Re: some bugs
Post by: bluenote on March 01, 2009, 06:20:25 PM: Heh

Dont get me wrong Eddie, more logging is good. In this case "spam" logging isnt helpful and with fw this touchy .... you want to be as easy as possible on it.

Running 1.22b05 now, crossed fingers whether this resolves my last one-two reboots per day.
Title: Re: some bugs
Post by: EddieZ on March 02, 2009, 01:54:44 AM: Quote from: bluenote on March 01, 2009, 06:20:25 PM
Heh

Dont get me wrong Eddie, more logging is good. In this case "spam" logging isnt helpful and with fw this touchy .... you want to be as easy as possible on it.

Running 1.22b05 now, crossed fingers whether this resolves my last one-two reboots per day.

I'm still curious as to how you ascertained that logging causes issues in your router...
Title: Re: some bugs
Post by: lotacus on March 02, 2009, 12:14:46 PM: well, who really knows. No one knew how the DNS issue would cause problems, until someone can take a deeper look into it. Perhaps, someone can tell us how to through the dlink in debug mode, or add a cpu chart in the status page.

Could be a rogue thread causng high cpu usage when it's logging too many requests than it can really handle, which is what I had assumed with my problem. My logs have never reached 2000 entries from the times I went in there viewing them, Especially in 2 minutes!

By the way, I think both are correct in terms of those tick boxes. I did in fact untick them all, then waited, did some stuff, went back in, put a tick in all of the boxes, hit refresh, and there was very few entries. So, the dev's wording is not very accurate because I decifered it as filtering out unwanted entries not DISABLING logging for those particular entries. Since then, the performance had improved when I applied that certain web only policy, when people were running p2p applications.

It's something that really cannot be avoided since the prior connections, and we know how many connections p2p makes, will keep on DDoS'n the router in an attempt at trying to re-establish a connection to the p2p host. The only work-around for this, would be to apply such policies during a period where there is very little network usage.
Title: Re: some bugs
Post by: Lycan on March 03, 2009, 09:38:24 AM: NO LOGGING STILL HAPPENS. it' not retained via memory. this is TRUE for ALL ROUTERS. A log is simply a retention of commands given to NAT.
For instance, if you disable LOG and enable SYSLOG you're still gunna see output, WHY? Cause the NAT is still doing things.

Also this is a router, not a tree and your network is a network, not a forest. If you want the unit to stop producing log entires, uncheck the boxes. IF you want the unit to stop responding to NAT commands (and there by never creating a log entry even if it's not retained by the log system) unplug the device and put it in the closet and read a book. :)
Title: Re: some bugs
Post by: EddieZ on March 03, 2009, 01:04:58 PM: Quote from: Lycan on March 03, 2009, 09:38:24 AM
NO LOGGING STILL HAPPENS. it' not retained via memory. this is TRUE for ALL ROUTERS. A log is simply a retention of commands given to NAT.
For instance, if you disable LOG and enable SYSLOG you're still gunna see output, WHY? Cause the NAT is still doing things.

Also this is a router, not a tree and your network is a network, not a forest. If you want the unit to stop producing log entires, uncheck the boxes. IF you want the unit to stop responding to NAT commands (and there by never creating a log entry even if it's not retained by the log system) unplug the device and put it in the closet and read a book. :)

I guess the detail is in "retain through memory" ;D