Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[musicisbest]

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?

[FurryNutz]

Link>Welcome!

• What region are you located?
• Are you wired or wireless connected to the router?
• Was a Factory Reset performed before and after any firmware updates then set up from scratch?

FW Update Process

• Was the router working before any firmware updates?

Internet Service Provider and Modem Configurations

• What ISP Service do you have? Cable or DSL?
• What ISP Modem Mfr. and model # do you have?

[musicisbest]

Hi,

• I'm in Canada
• wireless
• No Factory Reset was performed after the upgrade
• Yes the router was working before
• Northerntel.  DSL.
• Sagemcom 4300
  
  
  Thanks

[FurryNutz]

So these log entries only started after loading v1.02?

Is your ISP modem bridged?

• If the ISP modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems: Link>Double NAT and How NAT Works. To tell if the modem is bridged or not, look at the routers web page, Status/Device Info/Wan Section, if there is a 192.168.0.# address in the WAN IP address field, then the modem is not bridged. If the modem can't be bridged then see if the modem has a DMZ option and input the IP address the router gets from the modem and put that into the modems DMZ. Also check the routers DHCP IP address maybe conflicting with the ISP modems IP address of 192.168.0.1. Check to see if this is the same on the ISP modem, and if modem can't be bridged, change the DIR router to 192.168.1.1 or .0.254.
  Example of a D-Link router configured for PPPoE with ISP Modem bridged: PPPoE Configuration on Router

[musicisbest]

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

[FurryNutz]

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...

[musicisbest]

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].

[FurryNutz]

Ok, last resort, using the same process, please upgrade using v1.04 from this site:
http://support.dlink.com/ProductInfo.aspx?m=DIR-820L

You are in the same region so you can use this version of FW.

[musicisbest]

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?

[FurryNutz]

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?

[musicisbest]

What are the current log options selected?

    All except "Dropped Packets"

Thank you very much for your prompt replies.

Cheers.

[FurryNutz]

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.

[musicisbest]

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.

 

[FurryNutz]

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...

[Mwillems]

I have exactly the same thing happening.