IPv6 errors and net-cgi not found in R2 logs

[Wantox81]

Hello NetDuma team,

I would like to ask for some clarification about two recurring types of messages in my R2 logs: IPv6-related errors and “net-cgi not found”

My current setup is:

ONT → FRITZ!Box 7490 (fw7.62) → NetDuma R2 (fw3.3.280) → GL.iNet AR750 (Only Access Point fw4.3.25)

The FRITZ!Box handles the Internet connection, the R2 handles routing, and the AR750 is used only as a Wi-Fi Access Point. Wi-Fi is disabled on the R2.

After several tests, we found that the R2 works better when its workload is reduced by having the FRITZ!Box handle the Internet connection and the AR750 handle Wi-Fi separately, allowing the R2 to focus mainly on routing and its gaming-related functions.

However, even with IPv6 disabled on both WAN and LAN, the R2 continues to generate IPv6-related errors.

I am also seeing recurring “net-cgi not found” entries in the logs.

Could you please explain:

● Why does the R2 generate IPv6-related errors when IPv6 is disabled on both WAN and LAN?

● What exactly does “net-cgi notfound” mean, and what causes this message to appear in the logs?

I can provide the relevant log entries and timestamps if required.

Thank you.

[Netduma Fraser]

The logs can generally be ignored unless you're experiencing a specific issue as it shows background processes that can appear to be issues but aren't. These ones are very common and don't pose any problems at all, they're log spam essentially and just need to be cleaned up, as you've seen the IPv6 log shouldn't appear because its not even enabled.

[Wantox81]

Thank you for the clarification regarding the IPv6 and net-cgi: NOTFOUND messages.

I understand that these can be ignored and that the IPv6 messages should not appear when IPv6 is disabled.

While reviewing the complete R2 log, however, I noticed another event that looks different:

At 22:44:53, the kernel started reporting:

nf_queue: full at 1024 entries, dropping packets(s)

This was not a single occurrence. The message was repeatedly logged from approximately 22:44:53 to 22:45:14, with multiple net_ratelimit messages such as:

230 callbacks suppressed
388 callbacks suppressed
351 callbacks suppressed

Could you clarify what can cause the R2 nf_queue to become full at 1024 entries and start dropping packets?

Is this something I should investigate further, or can this also be considered normal log noise?

I have the complete R2 log available if it would be useful.