Messages

Thanks for the suggestion @pfry. I updated the NVM and the problem still persists - I still get netmap_transmit ixl0 full from time to time.

As for missing interfaces, I'll update to 25.7.8 and see if it fixes it.

Hello,

I'm new to OPNsense and have been really enjoying working with this firewall. However, I'm encountering a strange issue with my setup and am not sure whether it's a bug or something I've configured incorrectly.

I'm running OPNsense v25.7.7_4 and have a dozen VLANs configured with IPv4 Static IPs (except for the IPs themselves, the VLANs are all setup the same way with the LAN port as the parent). DHCP is being handled by Dnsmasq DNS & DHCP.

Here's where the issue comes in: when I go to the Leases section under Dnsmasq DNS & DHCP, the drop-down menu for interfaces is missing a few VLANs. However, I can confirm that the VLANs are configured correctly, as clients are able to connect and receive the correct IPs.

Strangely, two of the missing VLANs are showing up under the WAN interface in the lease list, with the correct IP addresses. These clients are functioning normally, with internet access and proper firewall rule enforcement. But there are still three other VLANs that are missing from the lease drop-down altogether.

My question is: Does the lease drop-down only show interfaces that have been assigned IPs? Could it be that if an interface doesn't register an IP, it doesn't show up in the list? And if that's the case, how do you explain the two VLANs that are showing up under WAN?

Additionally, I've noticed some errors in the console from time to time (the first set of numbers 015.xxxxxxx is different but the message about ixl0 full is consistent). Not sure if this is related or a separate issue related to netmap. On the WAN port (ixl0), I'm only running Suricata in IPS mode, and the error message I'm seeing is as follows:
015.030954 [4335] netmap_transmit ixl0 full hwcur 205 hwtail 645 qlen 583

I've been troubleshooting this issue with ChatGPT, and after working through a few tests, it was suggested that this might be a cosmetic bug in OPNsense, with no significant impact.

Has anyone encountered something similar? Any advice or thoughts on this issue would be greatly appreciated!