nf_conntrack: table full

General discussions for anything not model specific
Post Reply
palace
Posts: 7
Joined: Wed Nov 07, 2012 9:54 am

nf_conntrack: table full

Post by palace » Sat Dec 31, 2016 10:00 pm

Hi All

I'm seeing a bunch of these in the system log-
kern warn kernel: nf_conntrack: table full, dropping packet.

From what I've been able to find it could be torrents from an internal machine or a DDOS from outside? Is there some way maybe via the shell to get more info in what is actually causing these log entries? We've updated our router to a 8700NEXLR2 as the previous 7800VDOX was having intermittent WiFi issues, but did see similar entries on the 7800 as well.

Cheers
Peter

billion_fan
Posts: 5268
Joined: Tue Jul 19, 2011 4:30 pm

Re: nf_conntrack: table full

Post by billion_fan » Wed Jan 04, 2017 11:52 am

palace wrote:Hi All

I'm seeing a bunch of these in the system log-
kern warn kernel: nf_conntrack: table full, dropping packet.

From what I've been able to find it could be torrents from an internal machine or a DDOS from outside? Is there some way maybe via the shell to get more info in what is actually causing these log entries? We've updated our router to a 8700NEXLR2 as the previous 7800VDOX was having intermittent WiFi issues, but did see similar entries on the 7800 as well.

Cheers
Peter
It will be hard to comment as we have never sold the 8700NEXLR2 within the UK

palace
Posts: 7
Joined: Wed Nov 07, 2012 9:54 am

Re: nf_conntrack: table full

Post by palace » Wed Jan 04, 2017 10:03 pm

Hi There

It's not much different to a 7800 or 7800VDOX. No VOIP and menus pretty much the same. Can telnet and get into busybox etc but wondering if there is a way to dig deeper to see what is causing the issue?

Cheers
Peter

billion_fan
Posts: 5268
Joined: Tue Jul 19, 2011 4:30 pm

Re: nf_conntrack: table full

Post by billion_fan » Fri Jan 06, 2017 9:48 am

palace wrote:Hi There

It's not much different to a 7800 or 7800VDOX. No VOIP and menus pretty much the same. Can telnet and get into busybox etc but wondering if there is a way to dig deeper to see what is causing the issue?

Cheers
Peter
The only way to find out which device is causing the issue, is to disconnect devices one by one, until the logs the disappear.

Once you have pin pointed the device, you can then reboot the router, and leave the device disconnected, to see if the logs appear again.

Post Reply