NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
brianandrus
Jan 01, 2017Aspirant
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 r...
- Jan 19, 2017
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.
brianandrus
Jan 01, 2017Aspirant
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
DaneA
Jan 10, 2017NETGEAR Employee Retired
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
- brianandrusJan 10, 2017Aspirant
It seems I spoke too soon. Now the router has been behaving as before: It suddenly just plain old stops routing. I am unable to connect to it or even ping it. I have to power-cycle it to get it up. That is occuring about 2x a day... grrrr
- brianandrusJan 10, 2017Aspirant
Here is something new in the logs:
Sat Oct 8 11:49:42 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] ---[ end trace 22e0bc744e623748 ]---
Sat Oct 8 11:49:42 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] [<a01b45f8>] (sys_send+0x18/0x20) from [<a0025d80>] (ret_fast_syscall+0x0/0x2c)
Sat Oct 8 11:49:42 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] [<a01b45bc>] (sys_sendto+0xb0/0xd4) from [<a01b45f8>] (sys_send+0x18/0x20)
Sat Oct 8 11:49:41 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] [<a01b42e4>] (sock_sendmsg+0xa0/0xc4) from [<a01b45bc>] (sys_sendto+0xb0/0xd4)
Sat Oct 8 11:49:41 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] [<9f64f4a4>] (key_output+0x1a0/0x210 [vipsec]) from [<a01b42e4>] (sock_sendmsg+0xa0/0xc4)
Sat Oct 8 11:49:41 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] [<9f6282b8>] (key_parse+0x6a8/0x798 [vipsec]) from [<9f64f4a4>] (key_output+0x1a0/0x210 [vipsec])
Sat Oct 8 11:49:41 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] [<9f64efc0>] (key_sendup0+0x164/0x1a8 [vipsec]) from [<9f6282b8>] (key_parse+0x6a8/0x798 [vipsec])
Sat Oct 8 11:49:41 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] [<9f64bbfc>] (copy_mbuf_to_skbuff+0xac/0x104 [vipsec]) from [<9f64efc0>] (key_sendup0+0x164/0x1a8 [vipsec])
Sat Oct 8 11:49:41 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] [<a01b82e4>] (sock_queue_rcv_skb+0x2c/0x100) from [<9f64bbfc>] (copy_mbuf_to_skbuff+0xac/0x104 [vipsec])
Sat Oct 8 11:49:41 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] [<a01cedbc>] (sk_filter+0x80/0x8c) from [<a01b82e4>] (sock_queue_rcv_skb+0x2c/0x100)
Sat Oct 8 11:49:41 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] [<a0042f20>] (local_bh_enable+0x40/0xa4) from [<a01cedbc>] (sk_filter+0x80/0x8c)
Sat Oct 8 11:49:41 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] [<a003e318>] (warn_slowpath_common+0x4c/0x80) from [<a0042f20>] (local_bh_enable+0x40/0xa4)
Sat Oct 8 11:49:41 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] [<a002ba44>] (unwind_backtrace+0x0/0xdc) from [<a003e318>] (warn_slowpath_common+0x4c/0x80)
Sat Oct 8 11:49:41 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] Modules linked in: vipsec(P) klite(P) nf_nat_h323 nf_conntrack_h323 nf_nat_tftp nf_conntrack_tftp nf_nat_pptp nf_conntrack_pptp nf_nat_proto_gre nf_conntrack_proto_gre umi(P) ipt_set ipt_SET ip_set_iphash ip_set sppe
Sat Oct 8 11:49:41 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] WARNING: at kernel/softirq.c:143 local_bh_enable+0x40/0xa4()
Sat Oct 8 11:49:41 2016(GMT-0800) [FVS318Gv2][Kernel][KERNEL] ------------[ cut here ]------------- DaneAJan 11, 2017NETGEAR Employee Retired
Kindly try the steps below:
1. On the web-GUI of the FVS318Gv2, go to Security > Firewall > Attack Checks.
2. Uncheck the boxes that says "Block TCP flood" and "Block UDP flood."
3. Click Apply.
Refer on the image below:

Let us know the result.
Regards,
DaneA
NETGEAR Community Team
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!