• February 22, 2025, 09:18:34 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: kernel - conntrack messages  (Read 4531 times)

lanny_

  • Level 1 Member
  • *
  • Posts: 5
kernel - conntrack messages
« on: July 11, 2018, 03:28:32 AM »
Hello,
I am receiving several kernel conntrack messages.  how can I block or stop these?  I am on the latest firmware.

[DSR-250N] <4> 1 2018-07-10T21:27:26-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:26-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [114.98.184.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:26-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:26-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:26-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:26-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [166.122.164.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:26-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
0:00:00:00:00] [TCP] [36576] [25]
[DSR-250N] <30> 1 2018-07-10T21:27:26-04:00 DSR-250N nimfStatus 1154 - - Connection type information has been updated.
[DSR-250N] <30> 1 2018-07-10T21:27:26-04:00 DSR-250N nimfStatus 1155 - - Connection type information has been updated.
[DSR-250N] <30> 1 2018-07-10T21:27:26-04:00 DSR-250N nimfStatus 1156 - - Connection type information has been updated.
[DSR-250N] <30> 1 2018-07-10T21:27:26-04:00 DSR-250N linkStatusDetect 1264 - - WAN1 link is UP.
[DSR-250N] <30> 1 2018-07-10T21:27:26-04:00 DSR-250N nimfStatus 1160 - - Connection type information has been updated.
[DSR-250N] <30> 1 2018-07-10T21:27:30-04:00 DSR-250N linkStatusDetect 1264 - - WAN1 link is UP.
[DSR-250N] <30> 1 2018-07-10T21:27:35-04:00 DSR-250N linkStatusDetect 1264 - - WAN1 link is UP.
[DSR-250N] <30> 1 2018-07-10T21:27:37-04:00 DSR-250N nimfStatus 1257 - - Connection type information has been updated.
[DSR-250N] <30> 1 2018-07-10T21:27:37-04:00 DSR-250N nimfStatus 1258 - - Connection type information has been updated.
[DSR-250N] <30> 1 2018-07-10T21:27:37-04:00 DSR-250N nimfStatus 1259 - - Connection type information has been updated.
[DSR-250N] <30> 1 2018-07-10T21:27:38-04:00 DSR-250N nimfStatus 1263 - - Connection type information has been updated.
[DSR-250N] <30> 1 2018-07-10T21:27:40-04:00 DSR-250N linkStatusDetect 1264 - - WAN1 link is UP.
[DSR-250N] <30> 1 2018-07-10T21:27:45-04:00 DSR-250N linkStatusDetect 1264 - - WAN1 link is UP.
[DSR-250N] <30> 1 2018-07-10T21:27:51-04:00 DSR-250N linkStatusDetect 1264 - - WAN1 link is UP.
[DSR-250N] <30> 1 2018-07-10T21:27:51-04:00 DSR-250N nimfStatus 1444 - - Connection type information has been updated.
[DSR-250N] <30> 1 2018-07-10T21:27:52-04:00 DSR-250N nimfStatus 1455 - - Connection type information has been updated.
[DSR-250N] <30> 1 2018-07-10T21:27:52-04:00 DSR-250N nimfStatus 1456 - - Connection type information has been updated.
[DSR-250N] <30> 1 2018-07-10T21:27:53-04:00 DSR-250N nimfStatus 1457 - - Connection type information has been updated.
[DSR-250N] <4> 1 2018-07-10T21:27:56-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:56-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:56-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:56-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:56-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:56-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:56-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:56-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:56-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:56-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:56-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:56-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:56-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:56-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:56-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:56-04:00 DSR-250N KERNEL - - - <sppe_cmd_arp> Fail to read IPv4 ARP entry, IP 0x0a0a0a53
[DSR-250N] <4> 1 2018-07-10T21:27:56-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:56-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:56-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
[DSR-250N] <4> 1 2018-07-10T21:27:56-04:00 DSR-250N KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [2.135.49.255] [128]
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: kernel - conntrack messages
« Reply #1 on: July 11, 2018, 06:52:49 AM »
I recommend that you phone contact your regional D-Link support office and ask for help and information regarding this.
Link> Tech Support Contact Information
We find that phone contact has better immediate results over using email.
Let us know how it goes please.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

Cyberg

  • Level 1 Member
  • *
  • Posts: 13
Re: kernel - conntrack messages
« Reply #2 on: September 17, 2018, 08:26:28 PM »
lanny_,

Did you ever discover the cause of you No_Conntrack_Entry log messages.  I'm getting tons of them. As well as many of the ones below (just listing a couple of repeating ones) but mostly No_Conntrack_Entry.  I'm having to reboot my router at lease once a week to re-establish internet connection.   I too have the latest Firmware installed 3.12.  I'd like to know what the log messages mean.

1 2018-09-17T21:34:04-05:00 DSR-250 KERNEL - - [INVALID][NO_CONNTRACK_ENTRY][DROP] [0.0.0.0] [130.22...
1 2018-09-17T21:32:54-05:00 DSR-250 KERNEL - - [SYSTEM][DROP] [IN=WAN] [23.195.248.101 80:e0:1d:02:c...
1 2018-09-17T21:33:57-05:00 DSR-250 KERNEL - - - CPU: 0 Tainted: P W (2.6.31.1-cavm1 #7)
1 2018-09-17T21:33:57-05:00 DSR-250 KERNEL - - - TEST_DEBUG mykmod loaded 41645/5000 jiffies before
1 2018-09-17T21:33:57-05:00 DSR-250 KERNEL - - - TEST_DEBUG timer 41645 jiffies calling keep alive
1 2018-09-17T21:34:03-05:00 DSR-250 KERNEL - - - Pid: 8807, comm: linkStatusDetec
Logged