What's new

Syslog filled with errors 386.7_2

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

johndoe85

Senior Member
kernel: tuple errors

RT-AX86U

Code:
Jul 31 08:21:26 kernel:         STATUS[ IPS_SEEN_REPLY_BIT IPS_ASSURED_BIT IPS_CONFIRMED_BIT IPS_SRC_NAT_DONE_BIT IPS_DST_NAT_DONE_BIT IPS_BLOG_BIT ]
Jul 31 08:21:26 kernel:     NFCT: ct<0xffffffc02d01fb00>, master<0x          (null)>
Jul 31 08:21:26 kernel:         F_NAT<ffffffc02a36e478> keys[0x00000000 0x00000000] dir<DIR_ORIG>
Jul 31 08:21:26 kernel:         help<0x          (null)> helper<NONE> status=8000019e refcnt=2 zone=0
Jul 31 08:21:26 kernel: tuple ffffffc02d01fb98: 6 xxx.xxx.xxx.xxx:52971 -> xxx.xxx.xxx.xxx:443
Jul 31 08:21:26 kernel: tuple ffffffc02d01fbd0: 6 xxx.xxx.xxx.xxx:443 -> xxx.xxx.xxx.xxx:52971
Jul 31 08:21:26 kernel:         STATUS[ IPS_SEEN_REPLY_BIT IPS_ASSURED_BIT IPS_CONFIRMED_BIT IPS_SRC_NAT_BIT IPS_SRC_NAT_DONE_BIT IPS_DST_NAT_DONE_BIT IPS_BLOG_BIT ]
Jul 31 08:21:26 kernel: blog_link:overwriting ct_p=ffffffc02c30a650, new_ct=ffffffc02d01fb00 idx=0
Jul 31 08:21:26 kernel:     NFCT: ct<0xffffffc02c30a650>, master<0x          (null)>

What is this and what to do about it?
 

Attachments

  • syslog.txt
    482 KB · Views: 70
That looks like debug information from conntrack. Have you changed the router's logging level, or installed any scripts that mess with flow control (e.g. wireguard)?
 
Last edited:
That looks like debug information from conntrack. Have you changed the router's logging level, or installed any scripts that mess with flow control (e.g. wireguard)?
Wireguard is installed.
Conntrak idk about.


Edit. The debug was on, what should it be on?
 
1659298440872.png

is this the default log level thing?
 
Upgraded from 386.7 to 386.7_2 half an hour ago doing the following and everything seems to be okay.
- Unmounted and removed the usb rebooted.
- Upgraded the firmware and rebooted.
- After reboot waited a few minutes and unplugged the power
- Waited for half a minute, plugged in the USB and the power.

All reboots are manual reboots ( power off, wait, and power on)
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top