OPNsense Forum

Archive => 19.1 Legacy Series => Topic started by: ruzmat on February 06, 2019, 03:01:43 pm

Title: [SOLVED] Hotplug event detected
Post by: ruzmat on February 06, 2019, 03:01:43 pm: Hi,

I set up a firewall in bridge (transparent) mode, everything works, but when I add rules to the firewall, after a while, my ports are disabled and the bridge disappears.

log:
Code: [Select]
Feb 6 19:16:47 opnsense: /usr/local/etc/rc.newwanip: Failed to detect IP for 212_WAN[opt4] Feb 6 19:16:47 opnsense: /usr/local/etc/rc.newwanip: On (IP address: ) (interface: 212_WAN[opt4]) (real interface: igb5). Feb 6 19:16:47 opnsense: /usr/local/etc/rc.newwanip: IP renewal is starting on 'igb5' Feb 6 19:16:47 opnsense: /usr/local/etc/rc.linkup: Hotplug event detected for 212_WAN(opt4) but ignoring since interface is configured with static IP (0.0.0.0 ::) Feb 6 19:16:47 kernel: igb5: link state changed to UP Feb 6 19:16:46 opnsense: /usr/local/etc/rc.newwanip: Failed to detect IP for 178_WAN[opt2] Feb 6 19:16:46 opnsense: /usr/local/etc/rc.newwanip: On (IP address: ) (interface: 178_WAN[opt2]) (real interface: igb3). Feb 6 19:16:46 opnsense: /usr/local/etc/rc.newwanip: IP renewal is starting on 'igb3' Feb 6 19:16:46 opnsense: /usr/local/etc/rc.linkup: Hotplug event detected for 178_WAN(opt2) but ignoring since interface is configured with static IP (0.0.0.0 ::) Feb 6 19:16:46 kernel: igb3: link state changed to UP Feb 6 19:16:43 opnsense: /usr/local/etc/rc.linkup: Hotplug event detected for 212_WAN(opt4) but ignoring since interface is configured with static IP (0.0.0.0 ::) Feb 6 19:16:43 opnsense: /usr/local/etc/rc.linkup: Hotplug event detected for 178_WAN(opt2) but ignoring since interface is configured with static IP (0.0.0.0 ::) Feb 6 19:16:43 kernel: igb5: link state changed to DOWN Feb 6 19:16:43 kernel: igb3: link state changed to DOWN Feb 6 18:06:11 send_telemetry.py: telemetry data collected 61802 records in 11.09 seconds @2019-02-06 12:06:00.575861 Feb 6 17:53:00 send_telemetry.py: telemetry data collected 783 records in 0.16 seconds @2019-02-06 11:53:00.570842 Feb 6 17:51:00 send_telemetry.py: telemetry data collected 27 records in 0.02 seconds @2019-02-06 11:50:37.409144 Feb 6 17:49:00 send_telemetry.py: telemetry data collected 31 records in 0.03 seconds @2019-02-06 11:48:34.087590
firewall rules: http://joxi.ru/Q2KxDVQCLb181A (http://joxi.ru/Q2KxDVQCLb181A)
interface: http://joxi.ru/E2pkWVqi7OQEym (http://joxi.ru/E2pkWVqi7OQEym)

When these rules are disabled everything works!
After switching on after 20-30 minutes, the ports are disabled.
Title: Re: Hotplug event detected
Post by: ruzmat on February 06, 2019, 04:06:30 pm: I tried to disable suricata (Intrusion Detection).
Did not help.
Title: Re: Hotplug event detected
Post by: Northguy on February 10, 2019, 08:27:59 pm: Do you have Wan DHCP? What happens if you do a change on the WAN interface settings? Seems familiar behaviour as my issue #3200 on GitHub:

https://github.com/opnsense/core/issues/3200

My logs also show a hot plug event

Verstuurd vanaf mijn Moto G (5) Plus met Tapatalk
Title: Re: Hotplug event detected
Post by: ruzmat on March 05, 2019, 06:10:09 pm: Quote from: Northguy on February 10, 2019, 08:27:59 pm
Do you have Wan DHCP? What happens if you do a change on the WAN interface settings? Seems familiar behaviour as my issue #3200 on GitHub:

https://github.com/opnsense/core/issues/3200

My logs also show a hot plug event

Verstuurd vanaf mijn Moto G (5) Plus met Tapatalk

Thanks for the answer, the problem was solved in the last update on 19.1.2