NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ICMPv6 RA: ndisc_router_discovery() failed to add default route
I am seeing the following message in my logs every minute or so:
[FVS318Gv2]Sat Dec 31 13:00:39 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] ICMPv6 RA: ndisc_router_discovery() failed to add default route. [FVS318Gv2]Sat Dec 31 13:00:44 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] ICMPv6 RA: ndisc_router_discovery() failed to add default route. [FVS318Gv2]Sat Dec 31 13:00:49 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] ICMPv6 RA: ndisc_router_discovery() failed to add default route. [FVS318Gv2]Sat Dec 31 13:00:49 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] ICMPv6 RA: ndisc_router_discovery() failed to add default route. [FVS318Gv2]Sat Dec 31 13:00:54 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] ICMPv6 RA: ndisc_router_discovery() failed to add default route. [FVS318Gv2]Sat Dec 31 13:00:59 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] ICMPv6 RA: ndisc_router_discovery() failed to add default route. [FVS318Gv2]Sat Dec 31 13:00:59 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] ICMPv6 RA: ndisc_router_discovery() failed to add default route. [FVS318Gv2]Sat Dec 31 13:01:04 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] ICMPv6 RA: ndisc_router_discovery() failed to add default route. [FVS318Gv2]Sat Dec 31 13:01:09 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] ICMPv6 RA: ndisc_router_discovery() failed to add default route. [FVS318Gv2]Sat Dec 31 13:01:09 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] ICMPv6 RA: ndisc_router_discovery() failed to add default route.
This is using the latest firmware just downloaded too (4.3.4-2)
Any ideas what is going on here?
I ended up factory resetting the router per support.
So far things are good. I have not enabled ipv6 yet and will do so soon. So it appears that upgrading the firmware and then doing a factory reset is what was required.
10 Replies
Hi brianandrus,
Are there any recent changes in the settings of the FVS318Gv2 or recent changes within the network setup (such devices added or applications installed) that might trigger what you see in the logs?
Just to set your expectation, if you wanted the logs be interpreted, I suggest you to open an online case with NETGEAR Support. Kindly state your concern and attach the logs to the online case. After you have the requirements for escalation be ready, then it will be forwarded to the engineering team. The engineering team will be the one to analyze the logs.
Regards,
DaneA
NETGEAR Community Team
DaneA,
The one change I made was to lower the MTU from 1500 to 1492, but those log messages were showing up before and after the change.
The change was made because the device would just stop working for new sessions. If I had an open SSH session to a system, that stayed working, but any new connections would not go through. I saw that lowering the MTU could help that (which it seems to have remedied).
Everything seems to be working other than that message being spammed to the logs. I'll likely just turn off logging and let it be, unless issues start up again.
Brian
I'm glad to know that everything is working. :) About the MTU sizes, refer to the image below:
If ever the logs you've posted bothers you, you may open an online case with NETGEAR Support at anytime.
If you don't have any other concerns, I encourage you to mark the appropriate reply as the “Accepted Solution.” The NETGEAR Community looks forward to hearing from you and being a helpful resource in the future!
Regards,
DaneA
NETGEAR Community Team
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
