D-Link Forums

The Graveyard - Products No Longer Supported => Routers => DIR-820L => Topic started by: musicisbest on August 18, 2014, 10:49:17 PM

Title: bizarre log entries after firmware update
Post by: musicisbest on August 18, 2014, 10:49:17 PM
After updating to 1.02 from 1.00, I'm seeing log entries I have never seen before like:

Code: [Select]
Aug 16 11:22:58 derp user.warn kernel: add 0.0.0.0/0.0.0.0 to access 0.0.0.0/0.0.0.17:10 directly[0/0].
Aug 16 17:47:52 derp user.warn kernel: add 0.0.0.0/0.0.0.0 to access 0.0.229.142/0.0.0.17:10 directly[0/0]
Aug 17 02:23:44 derp user.warn kernel: add 0.0.0.0/0.0.0.0 to access 0.0.76.27/0.0.0.17:10 directly[0/0]
Aug 17 02:55:39 derp user.warn kernel: add 0.0.0.0/0.0.0.0 to access 0.0.227.63/0.0.0.17:10 directly[0/0]
Aug 17 04:10:43 derp user.warn kernel: add 0.0.0.0/0.0.0.0 to access 0.0.124.181/0.0.0.17:10 directly[0/0]
Aug 17 05:53:12 derp user.warn kernel: add 0.0.0.0/0.0.0.0 to access 0.0.203.79/0.0.0.17:10 directly[0/0]
Aug 17 06:18:10 derp user.warn kernel: add 0.0.0.0/0.0.0.0 to access 0.0.27.223/0.0.0.17:10 directly[0/0]

...and many many more similar entries.  Anybody know what this is about?
Title: Re: bizarre log entries after firmware update
Post by: FurryNutz on August 19, 2014, 06:49:29 AM
Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)

FW Update Process (http://forums.dlink.com/index.php?topic=42457.0)

Internet Service Provider and Modem Configurations
Title: Re: bizarre log entries after firmware update
Post by: musicisbest on August 19, 2014, 08:06:31 AM
Hi,

Title: Re: bizarre log entries after firmware update
Post by: FurryNutz on August 19, 2014, 08:12:03 AM
So these log entries only started after loading v1.02?

Is your ISP modem bridged?
Title: Re: bizarre log entries after firmware update
Post by: musicisbest on August 19, 2014, 08:36:37 AM
Quote
So these log entries only started after loading v1.02?

yes

The modem does not have router functionality. There is no other router set up.

The way the modem is setup by the ISP is to just plug in a network cable and go. The modem supplies a public IP.

The internet connection on the router is set to Dynamic IP (DHCP)

Not sure if this answers your question.

Thanks
Title: Re: bizarre log entries after firmware update
Post by: FurryNutz on August 19, 2014, 08:41:49 AM
I'd like you to do the following and reload the FW file:
Factory reset.
Reload v1.02 using IE or FF without any browser add-ons.
Factory reset and set up from scratch...

Let us know if the logs entries are still present...
Title: Re: bizarre log entries after firmware update
Post by: musicisbest on August 19, 2014, 12:27:40 PM
Just reset, reflashed, and reconfigured and...

Code: [Select]
Aug 19 13:44:47 user.warn: kernel: add 0.0.0.0/0.0.0.0 to access 0.0.6.230/0.0.0.17:10 directly[0/0].
Title: Re: bizarre log entries after firmware update
Post by: FurryNutz on August 19, 2014, 12:31:45 PM
Ok, last resort, using the same process, please upgrade using v1.04 from this site:
http://support.dlink.com/ProductInfo.aspx?m=DIR-820L (http://support.dlink.com/ProductInfo.aspx?m=DIR-820L)

You are in the same region so you can use this version of FW.
Title: Re: bizarre log entries after firmware update
Post by: musicisbest on August 19, 2014, 01:38:57 PM
upgraded to 1.04...

Code: [Select]
Aug 19 16:26:55 user.warn: kernel: add 0.0.0.0/0.0.0.0 to access 0.0.0.0/0.0.0.0:56200 directly[10/10].
Aug 19 16:26:53 user.warn: kernel: add 0.0.0.0/0.0.0.0 to access 0.0.0.0/0.0.0.0:0 directly[10/10].
Aug 19 16:25:47 user.warn: kernel: add 0.0.0.0/0.0.0.0 to access 0.0.0.0/0.0.0.0:14510 directly[10/10].
Aug 19 16:25:45 user.warn: kernel: add 0.0.0.0/0.0.0.0 to access 0.0.0.0/0.0.0.0:0 directly[10/10].
Dec 31 19:03:23 user.warn: kernel: add 0.0.0.0/0.0.0.0 to access 0.0.0.0/0.0.0.0:57630 directly[10/10].
Dec 31 19:03:21 user.warn: kernel: add 0.0.0.0/0.0.0.0 to access 0.0.0.0/0.0.0.0:0 directly[10/10].
Dec 31 19:02:15 user.warn: kernel: add 0.0.0.0/0.0.0.0 to access 0.0.0.0/0.0.0.0:54287 directly[10/10].

Any idea what this means? Who's accessing what?
Title: Re: bizarre log entries after firmware update
Post by: FurryNutz on August 19, 2014, 01:41:15 PM
It's something internal to the FW. IT's nothing coming from the outside...Seems odd though. I'll forward this to my contact at D-Link as see if I get any thing back. It maybe some diagnostic result reporting is all.

What are the current log options selected?
Title: Re: bizarre log entries after firmware update
Post by: musicisbest on August 19, 2014, 01:46:00 PM
Quote
What are the current log options selected?

    All except "Dropped Packets"

Thank you very much for your prompt replies.

Cheers.
Title: Re: bizarre log entries after firmware update
Post by: FurryNutz on August 19, 2014, 01:48:07 PM
Ok, I can't promise any thing however I'll post back if I hear some information.

If the router is working other than this, maybe something not to worry about.

Please be patient.
Title: Re: bizarre log entries after firmware update
Post by: musicisbest on August 20, 2014, 11:37:40 AM
Hi,

It's much worse now since upgrading.

I get my full logs emailed to me. They're coming in every 60 to 90 minutes full of
 "user.warn kernel: add 0.0.0.0/0.0.0.0 to access 0.0.0.0/0.0.0.0:0 directly[10/10]"
entries. And this is after I decreased the logging level by unchecking the "Debug" and "Notice" options.

It's unfortunate because it's made the email notifications and logging annoying and more trouble than they're worth.

 
Title: Re: bizarre log entries after firmware update
Post by: FurryNutz on August 20, 2014, 11:39:22 AM
Ok I recommend going back to v1.00 FW, do a factory reset, load the FW file, then factory reset again then setup from scratch...

Title: Re: bizarre log entries after firmware update
Post by: Mwillems on January 22, 2015, 05:02:29 AM
I have exactly the same thing happening.
Title: Re: bizarre log entries after firmware update
Post by: FurryNutz on January 22, 2015, 07:55:10 AM
Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)


Internet Service Provider and Modem Configurations

I have exactly the same thing happening.
Title: Re: bizarre log entries after firmware update
Post by: epoch555 on April 01, 2015, 07:00:13 PM
Any progress on this? I just noticed the same thing is happening to my router.

DIR-820L A1, firmware 1.06, Canada
Cable Internet, 50Mbps DL/3.5 up, Motorola SB6120, Dynamic IP

I'm also getting "daemon.err: miniupnpd[23028]: Can't find in which sub network the client is" very often. Disabling UPNP makes it go away, but then I loose functionality.

Apr 1 19:57:40   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is
Apr 1 19:57:38   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is
Apr 1 19:57:36   user.warn: kernel: add   0.0.0.0/0.0.0.0 to access 0.0.0.0/0.0.0.0:33170 directly[10/10].
Apr 1 19:57:36   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is
Apr 1 19:57:34   user.warn: kernel: add   0.0.0.0/0.0.0.0 to access 0.0.0.0/0.0.0.0:0 directly[10/10].
Apr 1 19:57:33   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is
Apr 1 19:56:32   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is
Apr 1 19:56:30   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is
Apr 1 19:56:28   user.warn: kernel: add   0.0.0.0/0.0.0.0 to access 0.0.0.0/0.0.0.0:62780 directly[10/10].
Apr 1 19:56:28   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is
Title: Re: bizarre log entries after firmware update
Post by: FurryNutz on April 02, 2015, 07:10:13 AM
Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)

>FW Update Process (http://forums.dlink.com/index.php?topic=42457.0)

Did you change the logging level by un-checking the "Debug" and "Notice" options?

Any progress on this? I just noticed the same thing is happening to my router.

DIR-820L A1, firmware 1.06, Canada
Cable Internet, 50Mbps DL/3.5 up, Motorola SB6120, Dynamic IP

I'm also getting "daemon.err: miniupnpd[23028]: Can't find in which sub network the client is" very often. Disabling UPNP makes it go away, but then I loose functionality.

Apr 1 19:57:40   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is
Apr 1 19:57:38   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is
Apr 1 19:57:36   user.warn: kernel: add   0.0.0.0/0.0.0.0 to access 0.0.0.0/0.0.0.0:33170 directly[10/10].
Apr 1 19:57:36   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is
Apr 1 19:57:34   user.warn: kernel: add   0.0.0.0/0.0.0.0 to access 0.0.0.0/0.0.0.0:0 directly[10/10].
Apr 1 19:57:33   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is
Apr 1 19:56:32   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is
Apr 1 19:56:30   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is
Apr 1 19:56:28   user.warn: kernel: add   0.0.0.0/0.0.0.0 to access 0.0.0.0/0.0.0.0:62780 directly[10/10].
Apr 1 19:56:28   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is
Title: Re: bizarre log entries after firmware update
Post by: FurryNutz on April 03, 2015, 07:15:30 AM
Any status on this?  ???

Any progress on this? I just noticed the same thing is happening to my router.

DIR-820L A1, firmware 1.06, Canada
Cable Internet, 50Mbps DL/3.5 up, Motorola SB6120, Dynamic IP

I'm also getting "daemon.err: miniupnpd[23028]: Can't find in which sub network the client is" very often. Disabling UPNP makes it go away, but then I loose functionality.

Apr 1 19:57:40   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is
Apr 1 19:57:38   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is
Apr 1 19:57:36   user.warn: kernel: add   0.0.0.0/0.0.0.0 to access 0.0.0.0/0.0.0.0:33170 directly[10/10].
Apr 1 19:57:36   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is
Apr 1 19:57:34   user.warn: kernel: add   0.0.0.0/0.0.0.0 to access 0.0.0.0/0.0.0.0:0 directly[10/10].
Apr 1 19:57:33   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is
Apr 1 19:56:32   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is
Apr 1 19:56:30   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is
Apr 1 19:56:28   user.warn: kernel: add   0.0.0.0/0.0.0.0 to access 0.0.0.0/0.0.0.0:62780 directly[10/10].
Apr 1 19:56:28   daemon.err: miniupnpd[23028]: Can't find in which sub network the client is