plugins icon indicating copy to clipboard operation
plugins copied to clipboard

intrusion-detection-content-et-pro (v1.0.2_1): Gateway on WAN interface breaks when IDS is active on WAN interface.

Open phxyz12 opened this issue 2 years ago • 0 comments

Dear all

Important notices Before you add a new report, we ask you kindly to acknowledge the following:

  • [x] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
  • [x] I have searched the existing issues, open and closed, and I'm convinced that mine is new.
  • [x] The title contains the plugin to which this issue belongs

First things first: Merry Christmas to all of you who celebrate it, all others have a great time, too.

Describe the bug

Plugin version: 1.0.2_1

The gateway on the WAN interface gets disrupted when the intrusion detection service is running. The interface is reported as "UP" in "Interfaces" section of the lobby dashboard, but in the "Gateways" section, the gateway on the WAN interface is "OFFLINE".

The intrusion detection service is configured to operate on all interfaces, namely:

  • LAN: The local network
  • WAN: the network to the router
  • wg1: A Wireguard interface

This worked for many months, but it broke right after the last update od OPNsense. Rebooting restores the WAN gateway, but it fails again within a minute.

I did not a single change to the whole system before or after the update.

Important note: As far as I see, the plugin version did not get updated during the last update. The issue may be in some other component, but the only way I experience the error is when having IDS active on the WAN interface.

To Reproduce

  1. Configure intrusion detection for the WAN interface
  2. Restart the intrusion detection service
  3. Wait a short while

The WAN gateway will go OFFLINE.

Expected behavior

The WAN gateway should be working with active intrusion detection on the WAN interface and it's status should be ONLINE on the dashboard.

Screenshots

NA

Relevant log files

In the general system log, I see these entries:

2023-12-23T12:30:16	Error	opnsense	/usr/local/etc/rc.linkup: ROUTING: refusing to set inet gateway on addressless wan(em1)	
2023-12-23T12:30:15	Error	opnsense	/usr/local/etc/rc.linkup: The command '/sbin/ifconfig 'em1' inet '192.168.10.2'/'24'' returned exit code '1', the output was 'ifconfig: ioctl (SIOCAIFADDR): File exists'	
2023-12-23T12:27:32	Error	opnsense	/usr/local/etc/rc.linkup: ROUTING: refusing to set inet gateway on addressless wan(em1)	
2023-12-23T12:27:32	Error	opnsense	/usr/local/etc/rc.linkup: The command '/sbin/ifconfig 'em1' inet '192.168.10.2'/'24'' returned exit code '1', the output was 'ifconfig: ioctl (SIOCAIFADDR): File exists'

Additional context

NA

Environment

  • OPNsense 23.7.10_1-amd64
  • FreeBSD 13.2-RELEASE-p7
  • Running on VM (qemu/libvirt hypervisor on Rocky Linux 9)

phxyz12 avatar Dec 23 '23 14:12 phxyz12