Print

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

[Soyale]

Hi

In the syslog entries from my DIR655, I see "mroute: pending queue full, dropping entries" about twice per second.  Does anyone know what that means?  Examples below :

<12>1 2013-11-05T08:36:38-08:00 dlinkrouter.hsd1.wa.comcast.net kernel - - - kernel: [ 1591.490000] mroute: pending queue full, dropping entries.
<12>1 2013-11-05T08:36:39-08:00 dlinkrouter.hsd1.wa.comcast.net kernel - - - kernel: [ 1592.350000] mroute: pending queue full, dropping entries.
<12>1 2013-11-05T08:36:39-08:00 dlinkrouter.hsd1.wa.comcast.net kernel - - - kernel: [ 1592.940000] mroute: pending queue full, dropping entries.
<12>1 2013-11-05T08:36:40-08:00 dlinkrouter.hsd1.wa.comcast.net kernel - - - kernel: [ 1593.290000] mroute: pending queue full, dropping entries.
<12>1 2013-11-05T08:36:40-08:00 dlinkrouter.hsd1.wa.comcast.net kernel - - - kernel: [ 1594.000000] mroute: pending queue full, dropping entries.
<12>1 2013-11-05T08:36:40-08:00 dlinkrouter.hsd1.wa.comcast.net kernel - - - kernel: [ 1594.050000] mroute: pending queue full, dropping entries.
<12>1 2013-11-05T08:36:41-08:00 dlinkrouter.hsd1.wa.comcast.net kernel - - - kernel: [ 1594.400000] mroute: pending queue full, dropping entries.


Background
I've been investigating poor network performance on my DIR-655 for several weeks, symptoms include temporary loss of connectivity, slow performance, problems resolving DNS.  After observing that the DIR 655 log (via the web interface) was showing a lot of dropped packets between machines inside the network (192.168.0.xxx addresses) I decided to reflash the 2.11NA firmware last night following the instructions here : http://forums.dlink.com/index.php?topic=42457.0

After reflashing, I manually reconfigured the router with only base configurations (wireless name, security type, DHCP reservations), enable Unicasting for IPv4 as well as v6 (necessary for a network TV tuner device I have).  I switched on one machine, LAN connected, let it run for a while and didn't see any dropped packets on the internal network (some dropped packets on the external network, but I believe this is normal behavior as Comcast's modem filters attempts to connect to my address).  After running for 30 minutes or so, I switched that machine to Wifi with the same result, no dropped packets on the internal network.  I then switched on my NAS and a Mac and left them running overnight.  As of this morning, no dropped packets according to the DIR-655 logs (that I could find, there are frequent dropped packets on the external IP address).  The DIR-655 log interface is quite slow, so I thought it would be easier to measure the frequency and SRC / DST for the dropped packets by enabling logging to my Syslog server from the DIR-655.  The Syslog server is on a QNAP NAS.  Syslog didn't work until I enabled logging via UDP and then the "mroute" errors showed up.  There is nothing else in the syslog, which is interesting because the built-in DIR-655 log interface is showing dropped packets on the external IP address every 5 seconds or so with the same IP address for maybe a minute then switching to a different IP address.

Where are the mroute errors coming from?  That's a lot of errors and it'd be nice to get to the route of that before moving along with the rest of the debugging process.

Once I figure out the source of those errors, most of the traffic to this point is on the LAN interface, not the Wifi.  It'll be interesting to see if I start to see dropped packets again once I get on the Wifi.  Also, I use extended range antennas on the DIR-655 rather than the standard ones.  I may also try putting the default antenna back.


Answers to standard questions
What Hardware version is your router? Look at sticker under router. -> B1
Link>What Firmware version is currently loaded? Found on the routers web page under status. -> 2.11NA
What region are you located? -> USA
Are you wired or wireless connected to the router? -> Currently all clients are wired
Has a Factory Reset been performed? -> Yes
Was a Factory Reset performed before and after any firmware updates then set up from scratch? -> Yes
Was the router working before any firmware updates? -> No

Internet Service Provider and Modem Configurations
What ISP Service do you have? Cable or DSL? -> Comcast, Cable
What ISP Modem Mfr. and model # do you have? -> Need to check
What ISP Modem service link speeds UP and Down do you have? -> 60Mbps Down, 10 Up
Check ISP MTU requirements, Cable is usually 1500, DSL is around 1492 down to 1472. Call the ISP and ask. Link>Checking MTU Values -> Currently set to 1500
For DSL/PPPoE connections on the router, ensure that "Always ON" option is enabled. -> NA

Router and Wired Configurations -> Haven't run through these yet.
Ensure devices are set to auto obtain an IP address. -> I have done this one though
If IPv6 is an option on the router, select Local Connection Only or Disable IPv6 options under Setup/IPv6.
Set Firewall settings to Endpoint Independent for TCP and UDP under Advanced/Firewall. Enable or Disable SPI to test.
Enable uPnP and Multi-cast Streaming under Advanced/Networking. -> Did this as well
Set current Time Zone, Date and Time. Use an NTP Server feature. Tools/Time. -> Did this
Check cable between Modem and Router, swap out to be sure. Link> Cat6 is recommended. -> Changed this for new cable

Wireless Configurations
Links>Wireless Installation Considerations and Managing Signal Congestion
Ensure the default (dlink) SSID name is changed. Can be anything and not something thats already in use by any neighboring WiFi routers. Under Setup/Wireless/Manual. -> Done
What wireless modes are you using? -> G and N
2.4Ghz Routers only: Try single mode G or N or mixed G and N? -> Am using mixed G and N
Channel Width set for Auto 20/40Mhz or try 20Mhz only.
Try setting a manual Channel to a open or unused channel. 1, 6 or 11. 11 for single mode N if the channel is clear. -> Running on channel 11.  Nothing in my neighborhood is clear unfortunately.
What security mode are you using? Preferred security is WPA-Personal. WPA2/AES Only. Some WiFi adapters don't support AES, so you might want to try TPIK only or Auto TPIK and AES. -> WPA2 / AES only
What wireless devices do you have connected? -> At the moment none. 
Any cordless house phones? -> Yes but never used.
Any other WiFi routers in the area? Link> Use InSSIDer to find out. How many? -> about 12
If you have any of these options, Try turning OFF or ON Short GI, WLAN Partition, HT 20/40 Co-exhistance and Extra Wireless Protection if you have it. Recommended settings are default. Under Advanced/Advanced Wireless. -> Haven't changed these yet
Enable WMM Enable Under Advanced/Advanced Wireless. -> Haven't changed these yet
Try setting Medium or Low power output settings and test again Under Advanced/Advanced Wireless. -> Haven't tried this yet

3rd Party Security Software Configurations
Turn off all anti virus and firewall programs on PC while testing. 3rd party firewalls are not generally needed when using routers as they are effective on blocking malicious inbound traffic.
Turn off all devices accept for one wired LAN PC while testing. -> Yep, did this.  No dropped packets on internal network but then nothing for that machine to talk to either!
Disable any downloading client software managers, i.e. Torrents or similar. -> Done

[FurryNutz]

Only thing I could come up with is this is something to do with the FW interacting with what I believe is the ISP modem. If you reboot the router with out the ISP modem being connected, you don't get these message. Or at least I didn't. I first encountered this in v2.07 and reported it. Beta v2.08 and Release v2.10 continued to have this problem however I found that after 10-15 minutes of leaving the router alone after it booted, this seemed to go away as I notice that ALL of the LAN LEDs were continually active until after 10-15 minutes elapsed. Then normal network activity was seen and normal operation:
http://forums.dlink.com/index.php?topic=48026.15

After v2.11 came out, I didn't notice this again and it seemed to have been fixed, at least for my 655 router connecting to a Motorola SB 6120 modem. I haven't tested my SB 6180 yet.

The odd behavior I saw was after the final factory reset. The router behaved normally. Only after I started making changes to the router manually and setting it up, would I see the MROUTE and constant LED activity for the period of time. Then it would stop.  

I tried to isolate the router from the ISP modem and used a switch to check other LAN devices. I could connect ALL wired devices up with out the ISP modem connected and normal behavior was seen. Soon as I connected the ISP modem...there went the MROUTE and LED constantly going for that period of time then would stop.

Let us know what Model ISP Modem you have.
You could do a factory reset and send the v2.03 .bin file and factory reset once again and re-test this...
I would be interested if this is seen again on v2.11NA...Does it happend with just 1 wired PC connected while the router is connected to the ISP modem?

[Soyale]

I checked the syslog tonight and as you predicted, the problem stopped after about 30 minutes.  It was interesting to see that I would get occasional "signal" in the log (DROPPED PACKET notifications) in amongst the mroute errors.  Then toward the end of the mroute errors I started to see more signal.  As you speculate, it's like there's a lot of traffic between the router and the modem that's causing an overflow in something and eventually it catches up or settles down.

I'll do the rest of the experimentation when I've got an hour or two to spend on it, probably in a couple of days.

[FurryNutz]

So takes your longer to settle down. Interesting.

Your not effected by any of this are you? http://forums.dlink.com/index.php?topic=50791.0

Let us know what Model ISP Modem you have.

[Soyale]

I'm not aware that I'm affected by the DNS problem on Comcast, but I had considered following the DNS guide to find a better DNS resolution server.  I'll do that once I've exhausted investigation on the mroute "issue"

My modem is an Arris WBM760A.

There's some interesting stuff in my syslog today.  I had another mroute storm.  It was preceded by what looked like a kernel crash, note in the log how the time / date suddenly shifts to earlier in 2013 for a while, presumably until it's got the NTP connection, and then reverts back to today's date / time.  Once it's finished dumping out the kernel debug information [log below], the mroute's start up again and take 50 minutes to resolve (9:15am to 10:05am).  Then at 11:45am you get a couple of minutes of these entries :

<28>1 2013-11-06T11:45:57-08:00 dlinkrouter.hsd1.wa.comcast.net miniupnpd 1943 - - miniupnpd[1943]: [truncated] m

Any useful clues in the possible kernel crash / recurrence of mroute errors?  Or in the make / model of the modem?

[kernel crash?]

Code: [Select]

<134>1 2013-11-06T09:10:24-08:00 dlinkrouter.hsd1.wa.comcast.net udhcpd 150 - - udhcpd[150]: UDHCPD Inform: add_lease 192.168.0.113
<134>1 2013-11-06T09:11:29-08:00 dlinkrouter.hsd1.wa.comcast.net udhcpd 150 - - udhcpd[150]: UDHCPD Inform: add_lease 192.168.0.113
<134>1 2013-11-06T09:12:31-08:00 dlinkrouter.hsd1.wa.comcast.net udhcpd 150 - - udhcpd[150]: UDHCPD Inform: add_lease 192.168.0.113
<13>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: klogd started: BusyBox v1.14.1 (2013-07-18 15:11:38 CST)
<13>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] Linux version 2.6.28.10 (vicchang@vicchang-desktop) (gcc version 4.4.1 20100320 (stable) (GCC) ) #4 Thu Jul 18 15:37:43 CST 2013
<11>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] processor dram 40100000-44000000, expecting 40100000-42000000
<14>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] processor ocm 3ffc1f00-3fff4d00, expecting 3ffc1f00-3fff4d00
<14>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] updating range registers for expanded dram
<14>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] IP7K Processor, Ubicom, Inc. <www.ubicom.com>
<14>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] Device Tree:
<14>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] #0113fffbed0: sendirq=255, recvirq=255,  name=board
<14>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] #0113fffbc8c: sendirq=255, recvirq=255,  name=bootargs
<14>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] #0113fffbb6c: sendirq=011, recvirq=023,  name=eth_lan
<14>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] #0113fffbb18: sendirq=010, recvirq=022,  name=pci
<14>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] #0113fffbaac: sendirq=255, recvirq=255,  name=processor
<14>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] #0113fffbc44: sendirq=255, recvirq=001,  name=traps
<14>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] #0113fffbbcc: sendirq=021, recvirq=013,  name=usbtio
<15>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] On node 0 totalpages: 16508
<15>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] free_area_init_node: node 0, pgdat 403b4aa4, node_mem_map 40934800
<15>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000]   DMA zone: 1 pages used for memmap
<15>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000]   DMA zone: 0 pages reserved
<15>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000]   DMA zone: 59 pages, LIFO batch:0
<15>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000]   Normal zone: 129 pages used for memmap
<15>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000]   Normal zone: 16319 pages, LIFO batch:3
<15>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000]   Movable zone: 0 pages used for memmap
<12>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 16378
<13>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] Kernel command line: console=ttyUM0 console=ttyUS0 serdes=0x02004000,61,250000000 mtdparts=ubicom32_boot_flash:128k(bootloader),7360k(upgrade),384k(jffs2),64k(fw_env),192k(language_pack),64k(artblock)
<12>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] PID hash table entries: 256 (order: 8, 1024 bytes)
<13>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] timer[34]: timer-primary - created
<13>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] timer[34]: shutdown
<13>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] timer[34]: periodic: 5000000 cycles
<14>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] console [ttyUM0] enabled
<8>1 2013-07-18T15:30:00-08:00 192.168.0.1 kernel - - - kernel: [    0.000000] diff: 64746898, timer has lost 13 ticks [rounded up]

... removed 100s of lines of log because of 20,000 char limit


<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: dhcp6_get_options: get DHCP option DNS, len 32
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: client6_recvadvert: server ID: 00:01:00:01:17:f4:8a:7d:14:fe:b5:d5:aa:fc, pref=255
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: client6_send: a new XID (18ecfb) is generated
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: copy_option: set client ID (len 10)
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: copy_option: set server ID (len 14)
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: copyout_option: set IA address
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: copyout_option: set identity association
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: copy_option: set elapsed time (len 2)
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: copyout_option: set IA_PD prefix
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: copyout_option: set IA_PD
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: copy_option: set opt_20 (len 0)
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: client6_send: send request to ff02::1:2
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: dhcp6_reset_timer: reset a timer on eth0.1, state=REQUEST, timeo=0, retrans=951
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: dhcp6_reset_timer: reset a timer on eth0.1, state=REQUEST, timeo=0, retrans=92
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: client6_recv: receive advertise from fe80::21d:45ff:fe70:56e2 on eth0.1
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: dhcp6_get_options: get DHCP option client ID, len 10
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog:   DUID: 00:03:00:01:14:d6:4d:25:a4:6b
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: dhcp6_get_options: get DHCP option server ID, len 14
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog:   DUID: 00:01:00:01:17:f4:8a:79:14:fe:b5:d5:b6:d5
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: dhcp6_get_options: get DHCP option identity association, len 40
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog:   IA_NA: ID=220570731, T1=172800, T2=276480
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: copyin_option: get DHCP option IA address, len 24
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: copyin_option:   IA_NA address: 2001:558:600a:5c:f83e:8d95:f896:4718 pltime=345600 vltime=345600
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: dhcp6_get_options: get DHCP option IA_PD, len 41
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog:   IA_PD: ID=220570731, T1=172800, T2=276480
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: dhcp6_get_options: get DHCP option opt_20, len 0
<14>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: dhcp6_get_options: unknown or unexpected DHCP6 option opt_20, len 0
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: dhcp6_get_options: get DHCP option preference, len 1
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog:   preference: 0
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: dhcp6_get_options: get DHCP option DNS, len 32
<14>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: client6_recvadvert: XID mismatch
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: client6_recv: receive reply from fe80::21d:45ff:fe70:56e2 on eth0.1
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: dhcp6_get_options: get DHCP option client ID, len 10
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog:   DUID: 00:03:00:01:14:d6:4d:25:a4:6b
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: dhcp6_get_options: get DHCP option server ID, len 14
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog:   DUID: 00:01:00:01:17:f4:8a:7d:14:fe:b5:d5:aa:fc
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: dhcp6_get_options: get DHCP option identity association, len 40
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog:   IA_NA: ID=220570731, T1=127704, T2=204327
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: copyin_option: get DHCP option IA address, len 24
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: copyin_option:   IA_NA address: 2001:558:600a:5c:3428:508b:cf33:9348 pltime=255409 vltime=255409
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: dhcp6_get_options: get DHCP option IA_PD, len 41
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog:   IA_PD: ID=220570731, T1=127704, T2=204327
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: copyin_option: get DHCP option IA_PD prefix, len 25
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: copyin_option:   IA_PD prefix: 2601:8:ae00:620::/60 pltime=255409 vltime=255409
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: dhcp6_get_options: get DHCP option opt_20, len 0
<14>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: dhcp6_get_options: unknown or unexpected DHCP6 option opt_20, len 0
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: dhcp6_get_options: get DHCP option authentication, len 28
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: info_printf: nameserver[0] 2001:558:feed::1
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: info_printf: nameserver[1] 2001:558:feed::2
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: get_ia: make an IA: PD-220570731
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: update_prefix: create a prefix 2601:8:ae00:620::/60 pltime=255409, vltime=255409
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: ifaddrconf: add an address 2601:8:ae00:621:16d6:4dff:fe25:a46a/64 on br0
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: get_ia: make an IA: NA-220570731
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: update_address: create an address 2001:558:600a:5c:3428:508b:cf33:9348 pltime=255409, vltime=255409
<15>1 2013-11-06T09:14:42-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: ifaddrconf: add an address 2001:558:600a:5c:3428:508b:cf33:9348/128 on eth0.1
<15>1 2013-11-06T09:14:45-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: client6_recvreply: executes /etc/dhcp6c-script
<30>1 2013-11-06T09:14:48-08:00 dlinkrouter.hsd1.wa.comcast.net radvd 3270 - - radvd[3270]: version 1.8.3 started
<15>1 2013-11-06T09:14:50-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: gpio create pidfile /var/run/gpio_wan_green.pid
<14>1 2013-11-06T09:15:03-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: Current local time and date: Wed Nov  6 09:15:03 2013
<30>1 2013-11-06T09:15:08-08:00 dlinkrouter.hsd1.wa.comcast.net radvd 4354 - - radvd[4354]: version 1.8.3 started
<28>1 2013-11-06T09:15:08-08:00 dlinkrouter.hsd1.wa.comcast.net radvd 4354 - - radvd[4354]: Ignoring deprecated RDNSS preference.
<28>1 2013-11-06T09:15:08-08:00 dlinkrouter.hsd1.wa.comcast.net radvd 4354 - - radvd[4354]: Ignoring deprecated RDNSS open flag.
<27>1 2013-11-06T09:15:09-08:00 dlinkrouter.hsd1.wa.comcast.net dhcp6s 4403 - - dhcp6s[4403]: cfparse: cfparse: fopen(/var/etc/dhcpd6.conf): No such file or directory
<27>1 2013-11-06T09:15:09-08:00 dlinkrouter.hsd1.wa.comcast.net dhcp6s 4403 - - dhcp6s[4403]: dhcp6_ctl_authinit: failed to open /etc/dhcp6sctlkey: No such file or directory
<27>1 2013-11-06T09:15:18-08:00 dlinkrouter.hsd1.wa.comcast.net dhcp6s 4846 - - dhcp6s[4846]: dhcp6_ctl_authinit: failed to open /etc/dhcp6sctlkey: No such file or directory
<12>1 2013-11-06T09:15:19-08:00 dlinkrouter.hsd1.wa.comcast.net kernel - - - kernel: [  112.310000] mroute: pending queue full, dropping entries.
<12>1 2013-11-06T09:15:19-08:00 dlinkrouter.hsd1.wa.comcast.net kernel - - - kernel: [  112.600000] mroute: pending queue full, dropping entries.
<15>1 2013-11-06T09:15:19-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: client6_script: script "/etc/dhcp6c-script" terminated
<15>1 2013-11-06T09:15:19-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: dhcp6_remove_event: removing an event on eth0.1, state=REQUEST
<15>1 2013-11-06T09:15:19-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: dhcp6_remove_event: removing server (ID: 00:01:00:01:17:f4:8a:7d:14:fe:b5:d5:aa:fc)
<15>1 2013-11-06T09:15:19-08:00 dlinkrouter.hsd1.wa.comcast.net syslog - - - syslog: client6_recvreply: got an expected reply, sleeping.



[FurryNutz]

Seen many odd things and behaviors with Arris modems:
Arris Cable Modems and External Routers

I recommend that you have your ISP check the cabling going to the ISP modem, check signal levels going to the ISP modem. Check for t.v. line splitters and remove them as they can introduce noise on the line and lower the signal going to the ISP modem. Connecting to the ISP modem could result in a false positive as the signal to the modem could be just enough to that point then adding on a router, could see problems. The router operation is dependent upon getting good data flow from the ISP modem and the modem is dependent upon getting good signal from the ISP Service.

Any chance you can test a different ISP modem? Motorola SB 6120, 6121, 6141 or 6180? Or do you have friend or family where you can take the 655 and test it out on there ISP modem? Would be interesting to see if the problem follows...

I personally don't recommend Arris modems. Even though they bought Motorola's modem division. 

[Soyale]

Your theory is that the apparent crash in the DLINK is caused by something happening in the cable modem?

[FurryNutz]

Possible. One way to experiment. Boot up with out ISP modem connect while everything else is connected and view results...

[Soyale]

I just flashed 2.03NA to see if the 2.11NA firmware was the culprit.  Almost immediately on bootup the syslog is filled with mroute pending errors (6 minutes worth and counting at several per second).

The cable connection coming into the house splits in my network panel and there is a 3-way splitter.  The modem is attached to the -3.5dB leg and an HD Homerun to the -7.5dB leg.  The 3rd leg is connected to a wall cable connection that' not being used/  I can replace the 3-way with a 2-way split without losing anything.

On my list of experiments I'm going to try :

* Contacting Comcast to have them check signal strength
* Replace 3-way splitter with 2-way
* Disconnecting the router from the cable modem and rebooting to see if mroute errors still show up

[FurryNutz]

Keep us posted...

[Soyale]

I tried :

* Disconnecting the router from the cable modem and rebooting to see if mroute errors still show up

So basically I had the router rebooted and connected to the cable modem.  mroute errors were flooding in.  I then disconnected the LAN cable between the cable modem and the router and mroute errors stopped immediately.  I rebooted the modem, left it for ten minutes and reconnected the LAN cable between the cable modem and router and ... you guessed it ... the mroute errors started up again.

I think this points to an issue with the cable modem.  I'll take a look at signal strength and splitters first.

The odd thing since I reflashed to 2.03NA is that the mroute errors don't seem to stop, I've got hours and hours of 4 or 5 of these every second.

[FurryNutz]

Any chance you can test a difference modem? Or test the 655 at a friends or families place with a different modem?
http://forums.dlink.com/index.php?topic=48026.0