• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

strange errorThere were error(s) loading the rules: pfctl: SIOCGIFGROUP: Device not configured

Scheduled Pinned Locked Moved General pfSense Questions
69 Posts 4 Posters 5.2k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S
    stephenw10 Netgate Administrator
    last edited by Apr 15, 2024, 1:41 PM

    Well you might try putting a switch in between if you can. It lost link for some reason. That could be a link negotiation issue. Though it's difficult to test if it didn't happen for 28days!

    Did it actually cause a problem beyond triggering the alert?

    P 1 Reply Last reply Apr 15, 2024, 1:44 PM Reply Quote 0
    • P
      pfsss @stephenw10
      last edited by Apr 15, 2024, 1:44 PM

      @stephenw10 there is no other issue affects me. the network re-acquires a new ip through PPPOE, and the network is ok. i will watch out such error the next a few days.

      1 Reply Last reply Reply Quote 0
      • S
        stephenw10 Netgate Administrator
        last edited by stephenw10 Apr 15, 2024, 2:05 PM Apr 15, 2024, 2:04 PM

        Just reviewing here I don't see if we ever checked what interface groups you actually have configured? And what you're using them for?

        Obviously that error should not be triggered simply because the PPPoE link reconnected.

        P 2 Replies Last reply Apr 15, 2024, 2:36 PM Reply Quote 0
        • P
          pfsss @stephenw10
          last edited by Apr 15, 2024, 2:36 PM

          @stephenw10 here is a few logs before the crush:

          Apr 15 03:55:00	sshguard	68173	Now monitoring attacks.
          Apr 15 04:56:00	sshguard	68173	Exiting on signal.
          Apr 15 04:56:00	sshguard	7842	Now monitoring attacks.
          Apr 15 05:25:20	check_reload_status	430	Linkup starting re0
          Apr 15 05:25:20	kernel		re0: link state changed to DOWN
          Apr 15 05:25:20	kernel		re0.1154: link state changed to DOWN
          Apr 15 05:25:20	check_reload_status	430	Linkup starting re0.1154
          Apr 15 05:25:21	check_reload_status	430	Reloading filter
          Apr 15 05:25:21	ppp	83198	caught fatal signal TERM
          

          I have configured three interface: LAN,WAN and wireguard. the LAN connects to the switch, and WAN connects to the modem.

          1 Reply Last reply Reply Quote 0
          • P
            pfsss @stephenw10
            last edited by May 15, 2024, 1:12 PM

            @stephenw10
            here I got the same error of pfctl
            the error log is as below:

            May 13 01:52:46	php-fpm	399	/rc.openvpn: Gateway, NONE AVAILABLE
            May 13 01:52:46	php-fpm	399	/rc.openvpn: Gateway, NONE AVAILABLE
            May 13 01:59:00	sshguard	36234	Exiting on signal.
            May 13 01:59:00	sshguard	50674	Now monitoring attacks.
            May 13 03:25:00	sshguard	50674	Exiting on signal.
            May 13 03:25:00	sshguard	52167	Now monitoring attacks.
            May 13 03:29:40	check_reload_status	430	Linkup starting re0
            May 13 03:29:40	kernel		re0: link state changed to DOWN
            May 13 03:29:40	kernel		re0.1154: link state changed to DOWN
            May 13 03:29:40	check_reload_status	430	Linkup starting re0.1154
            May 13 03:29:41	check_reload_status	430	Reloading filter
            May 13 03:29:41	ppp	61708	caught fatal signal TERM
            May 13 03:29:41	ppp	61708	[wan] IFACE: Close event
            May 13 03:29:41	ppp	61708	[wan] IPCP: Close event
            May 13 03:29:41	ppp	61708	[wan] IPCP: state change Opened --> Closing
            May 13 03:29:41	ppp	61708	[wan] IPCP: SendTerminateReq #4
            May 13 03:29:41	ppp	61708	[wan] error writing len 8 frame to b0: Network is down
            May 13 03:29:41	ppp	61708	[wan] IPCP: LayerDown
            May 13 03:29:42	php-cgi	75258	rc.kill_states: rc.kill_states: Removing states for IP XXX.XXX.XXX.XXX/32
            May 13 03:29:42	php-cgi	75258	rc.kill_states: rc.kill_states: Removing states for interface pppoe1
            May 13 03:29:42	check_reload_status	430	Rewriting resolv.conf
            May 13 03:29:42	ppp	61708	[wan] IFACE: Removing IPv4 address from pppoe1 failed(IGNORING for now. This should be only for PPPoE friendly!): Can't assign requested address
            May 13 03:29:42	ppp	61708	[wan] IPV6CP: Close event
            May 13 03:29:42	ppp	61708	[wan] IPV6CP: state change Opened --> Closing
            May 13 03:29:42	ppp	61708	[wan] IPV6CP: SendTerminateReq #3
            May 13 03:29:42	ppp	61708	[wan] error writing len 8 frame to b0: Network is down
            May 13 03:29:42	ppp	61708	[wan] IPV6CP: LayerDown
            May 13 03:29:42	php-cgi	79609	rc.kill_states: rc.kill_states: Removing states for IP fe80::XXXX%pppoe1/32
            May 13 03:29:42	php-cgi	79609	rc.kill_states: rc.kill_states: Removing states for interface pppoe1
            May 13 03:29:43	check_reload_status	430	Linkup starting re0
            May 13 03:29:43	kernel		re0: link state changed to UP
            May 13 03:29:43	kernel		re0.1154: link state changed to UP
            May 13 03:29:43	check_reload_status	430	Linkup starting re0.1154
            May 13 03:29:43	check_reload_status	430	Reloading filter
            May 13 03:29:44	check_reload_status	430	Rewriting resolv.conf
            May 13 03:29:44	ppp	61708	[wan] IFACE: Down event
            May 13 03:29:44	ppp	61708	[wan] IFACE: Rename interface pppoe1 to pppoe1
            May 13 03:29:44	ppp	61708	[wan] IFACE: Set description "WAN"
            May 13 03:29:44	ppp	61708	[wan] IPV6CP: SendTerminateReq #4
            May 13 03:29:44	ppp	61708	[wan] IPCP: SendTerminateReq #5
            May 13 03:29:44	ppp	19945	Multi-link PPP daemon for FreeBSD
            May 13 03:29:44	ppp	19945	process 19945 started, version 5.9
            May 13 03:29:44	ppp	19945	waiting for process 61708 to die...
            May 13 03:29:44	php-fpm	803	/rc.linkup: calling interface_dhcpv6_configure.
            May 13 03:29:44	php-fpm	803	/rc.linkup: Gateway, NONE AVAILABLE
            May 13 03:29:44	php-fpm	803	/rc.linkup: Default gateway setting as default.
            May 13 03:29:44	php-fpm	803	/rc.linkup: Gateway, none 'available' for inet6, use the first one configured. 'WAN_SLAAC'
            May 13 03:29:44	check_reload_status	430	Restarting IPsec tunnels
            May 13 03:29:44	check_reload_status	430	updating dyndns wan
            May 13 03:29:44	check_reload_status	430	Reloading filter
            May 13 03:29:45	ppp	19945	waiting for process 61708 to die...
            May 13 03:29:45	rc.gateway_alarm	71445	>>> Gateway alarm: LAN (Addr:192.XXX.XX.XX Alarm:1 RTT:5.442ms RTTsd:6.425ms Loss:25%)
            May 13 03:29:45	check_reload_status	430	updating dyndns LAN
            May 13 03:29:45	check_reload_status	430	Restarting IPsec tunnels
            May 13 03:29:45	check_reload_status	430	Restarting OpenVPN tunnels/interfaces
            May 13 03:29:46	php-fpm	56878	/rc.dyndns.update: Dynamic DNS (home.sinodmctech.cn) There was an error trying to determine the public IP for interface - wan (pppoe1 ).
            May 13 03:29:46	ppp	61708	[wan] IPCP: state change Closing --> Closed
            May 13 03:29:46	ppp	61708	[wan] IPCP: LayerFinish
            May 13 03:29:46	ppp	61708	[wan] IPV6CP: state change Closing --> Closed
            May 13 03:29:46	ppp	61708	[wan] IPV6CP: LayerFinish
            May 13 03:29:46	ppp	61708	[wan] Bundle: No NCPs left. Closing links...
            May 13 03:29:46	ppp	61708	[wan] Bundle: closing link "wan_link0"...
            May 13 03:29:46	ppp	61708	[wan] Bundle: Shutdown
            May 13 03:29:46	ppp	19945	waiting for process 61708 to die...
            May 13 03:29:46	ppp	61708	[wan_link0] Link: Shutdown
            May 13 03:29:46	ppp	61708	process 61708 terminated
            May 13 03:29:46	php-fpm	11767	/rc.openvpn: Gateway, NONE AVAILABLE
            May 13 03:29:46	php-fpm	11767	/rc.openvpn: Gateway, none 'available' for inet6, use the first one configured. 'WAN_SLAAC'```
            1 Reply Last reply Reply Quote 0
            • S
              stephenw10 Netgate Administrator
              last edited by May 15, 2024, 1:44 PM

              Not sure you ever clarified what interface groups you have configured?

              Ultimately if the re NIC keeps losing link it would be better to replace it with something Intel based.

              1 Reply Last reply Reply Quote 0
              • S
                sokeada
                last edited by Dec 28, 2024, 8:15 AM

                I just got the same error message today since I started using pfSense CE since v2.5, I've no any config change around 8 to 10 months ago but I face with the error today and my pfSense rebooting quite often and I don't know what is the exact problem is :(

                1 Reply Last reply Reply Quote 0
                • S
                  stephenw10 Netgate Administrator
                  last edited by Dec 28, 2024, 1:16 PM

                  Are you also using Realtek NICs?

                  Do you see any error logs or crash reports after it reboots?

                  S 1 Reply Last reply Dec 31, 2024, 3:52 AM Reply Quote 0
                  • S
                    sokeada @stephenw10
                    last edited by sokeada Dec 31, 2024, 3:56 AM Dec 31, 2024, 3:52 AM

                    @stephenw10 I'm using Intel NIC and the error message appear when the power source unstable and after power socket fixed, looks like everything back to normal.

                    I've rebooted pfSense box few times but I don't get any message error appear again.

                    1 Reply Last reply Reply Quote 0
                    • S
                      stephenw10 Netgate Administrator
                      last edited by Dec 31, 2024, 3:57 AM

                      So running fine since?

                      S 1 Reply Last reply Dec 31, 2024, 4:01 AM Reply Quote 0
                      • S
                        sokeada @stephenw10
                        last edited by Dec 31, 2024, 4:01 AM

                        @stephenw10 Yes after the action above, it has been running for two days+ without any issue or error appear. I'm not sure if power source fluctuation issue, I should not get error as topic.

                        1 Reply Last reply Reply Quote 0
                        • S
                          stephenw10 Netgate Administrator
                          last edited by Dec 31, 2024, 1:20 PM

                          Hmm, odd. I hate errors like that! 😉

                          S 1 Reply Last reply Jan 3, 2025, 4:47 AM Reply Quote 0
                          • S
                            sokeada @stephenw10
                            last edited by Jan 3, 2025, 4:47 AM

                            @stephenw10 so do I, not felling good when see it. 😖

                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post
                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                              This community forum collects and processes your personal information.
                              consent.not_received