• February 23, 2025, 10:14:53 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Logging options  (Read 4076 times)

d01100100

  • Level 2 Member
  • **
  • Posts: 34
Logging options
« on: July 03, 2009, 08:08:46 PM »
My FIOS settop boxes like to spam the network and the DGL likes to log that information.  As you can see here each settop box will broadcast every 10 seconds, 2 boxes will generate 6 log entries per minutes.  Segregation of the settop boxes from the normal IP network isn't an option, doing so would mean loss of some of their functionality.  I can't set a route for this network within the DGL-4500, it won't accept it as being valid.  Does enabling syslog prevent this information from being stored on the router itself?  I've caught my router twice now running out of memory, and I believe the culprit is the logging.

[INFO]   Wed Jun 10 06:59:20 2009   Dropped packet from 169.254.1.107 to 169.254.1.255 (IP protocol 17) as unable to create new session
[INFO]   Wed Jun 10 06:59:17 2009   Dropped packet from 169.254.1.122 to 169.254.1.255 (IP protocol 17) as unable to create new session
[INFO]   Wed Jun 10 06:59:10 2009   Dropped packet from 169.254.1.107 to 169.254.1.255 (IP protocol 17) as unable to create new session
[INFO]   Wed Jun 10 06:59:07 2009   Dropped packet from 169.254.1.122 to 169.254.1.255 (IP protocol 17) as unable to create new session
[INFO]   Wed Jun 10 06:59:00 2009   Dropped packet from 169.254.1.107 to 169.254.1.255 (IP protocol 17) as unable to create new session
[INFO]   Wed Jun 10 06:58:57 2009   Dropped packet from 169.254.1.122 to 169.254.1.255 (IP protocol 17) as unable to create new session
[INFO]   Wed Jun 10 06:58:50 2009   Dropped packet from 169.254.1.107 to 169.254.1.255 (IP protocol 17) as unable to create new session
[INFO]   Wed Jun 10 06:58:47 2009   Dropped packet from 169.254.1.122 to 169.254.1.255 (IP protocol 17) as unable to create new session
[INFO]   Wed Jun 10 06:58:40 2009   Dropped packet from 169.254.1.107 to 169.254.1.255 (IP protocol 17) as unable to create new session
[INFO]   Wed Jun 10 06:58:37 2009   Dropped packet from 169.254.1.122 to 169.254.1.255 (IP protocol 17) as unable to create new session
[INFO]   Wed Jun 10 06:58:30 2009   Dropped packet from 169.254.1.107 to 169.254.1.255 (IP protocol 17) as unable to create new session
[INFO]   Wed Jun 10 06:58:27 2009   Dropped packet from 169.254.1.122 to 169.254.1.255 (IP protocol 17) as unable to create new session
[INFO]   Wed Jun 10 06:58:20 2009   Dropped packet from 169.254.1.107 to 169.254.1.255 (IP protocol 17) as unable to create new session
[INFO]   Wed Jun 10 06:58:17 2009   Dropped packet from 169.254.1.122 to 169.254.1.255 (IP protocol 17) as unable to create new session
[INFO]   Wed Jun 10 06:58:10 2009   Dropped packet from 169.254.1.107 to 169.254.1.255 (IP protocol 17) as unable to create new session
Logged

anon

  • Level 3 Member
  • ***
  • Posts: 263
Re: Logging options
« Reply #1 on: July 03, 2009, 08:57:34 PM »
what f/w are you using?
Logged

d01100100

  • Level 2 Member
  • **
  • Posts: 34
Re: Logging options
« Reply #2 on: July 04, 2009, 06:02:47 AM »
I've been using 1.20.

I did some testing with the traffic coming into syslog-ng I've setup on 1 system.  If appears to store the information on the router as well as UDP broadcast.  If I uncheck INFO, then reenable it, the log entry count drops, while storing that information into the memory setting.  I've left the INFO turned off for now due to the UDP spam that is generated by my settop boxes.  The logging of the broadcast for unrecoganized networks has existed for every firmware since 1.15.
Logged