Navigation

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

    LAN interface flaps

    General pfSense Questions
    2
    2
    397
    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
      smacdoug last edited by

      I gave a SG-1000 running 2.4.0-RC. I'm using VLANS on the LAN interface.

      I see daily logs showing that the lan interface and all the VLAN interfaces go down and back up as shown below. The LAN port is connected directly to a switch. Oddly, I do not see the port on the switch go up and down at the same time.

      I also get occasional errors like: There were error(s) loading the rules: pfctl: DIOCXCOMMIT: Device busy - The line in question reads [0]:, and PF was wedged/busy and has been reset, but these also do not appear at the same time as the interface resets.

      I get the sense this may be normal behaviour, but I don't see these types of logs coming from my other pfSenses.

      Here is the log:

      Oct 9 04:09:23 php-fpm /rc.newwanip: rc.newwanip: on (IP address: 192.168.101.1) (interface: STAFF[opt1]) (real interface: cpsw1_vlan101).
      Oct 9 04:09:23 php-fpm /rc.newwanip: rc.newwanip: Info: starting on cpsw1_vlan101.
      Oct 9 04:09:22 php-fpm /rc.newwanip: rc.newwanip: on (IP address: 192.168.100.1) (interface: MANAGEMENT[lan]) (real interface: cpsw1_vlan100).
      Oct 9 04:09:22 php-fpm /rc.newwanip: rc.newwanip: Info: starting on cpsw1_vlan100.
      Oct 9 04:09:22 php-fpm /rc.newwanip: rc.newwanip: on (IP address: 192.168.103.1) (interface: POS[opt3]) (real interface: cpsw1_vlan103).
      Oct 9 04:09:22 php-fpm /rc.newwanip: rc.newwanip: Info: starting on cpsw1_vlan103.
      Oct 9 04:09:22 php-fpm /rc.newwanip: rc.newwanip: on (IP address: 192.168.102.1) (interface: GUEST[opt2]) (real interface: cpsw1_vlan102).
      Oct 9 04:09:22 php-fpm /rc.newwanip: rc.newwanip: Info: starting on cpsw1_vlan102.
      Oct 9 04:09:22 check_reload_status Reloading filter
      Oct 9 04:09:21 check_reload_status rc.newwanip starting cpsw1_vlan101
      Oct 9 04:09:21 php-fpm /rc.linkup: Hotplug event detected for STAFF(opt1) static IP (192.168.101.1 )
      Oct 9 04:09:20 check_reload_status rc.newwanip starting cpsw1_vlan100
      Oct 9 04:09:20 check_reload_status rc.newwanip starting cpsw1_vlan103
      Oct 9 04:09:20 check_reload_status rc.newwanip starting cpsw1_vlan102
      Oct 9 04:09:20 php-fpm /rc.linkup: Hotplug event detected for MANAGEMENT(lan) static IP (192.168.100.1 )
      Oct 9 04:09:20 php-fpm /rc.linkup: Hotplug event detected for POS(opt3) static IP (192.168.103.1 )
      Oct 9 04:09:20 php-fpm /rc.linkup: Hotplug event detected for GUEST(opt2) static IP (192.168.102.1 )
      Oct 9 04:09:20 php-fpm /rc.linkup: Hotplug event detected for STAFF(opt1) static IP (192.168.101.1 )
      Oct 9 04:09:20 check_reload_status Reloading filter
      Oct 9 04:09:20 php-fpm /rc.linkup: Hotplug event detected for MANAGEMENT(lan) static IP (192.168.100.1 )
      Oct 9 04:09:20 php-fpm /rc.linkup: Hotplug event detected for POS(opt3) static IP (192.168.103.1 )
      Oct 9 04:09:20 php-fpm /rc.linkup: Hotplug event detected for GUEST(opt2) static IP (192.168.102.1 )
      Oct 9 04:09:20 check_reload_status Reloading filter
      Oct 9 04:09:19 check_reload_status Linkup starting cpsw1_vlan101
      Oct 9 04:09:19 check_reload_status Linkup starting cpsw1_vlan100
      Oct 9 04:09:19 check_reload_status Linkup starting cpsw1_vlan103
      Oct 9 04:09:19 check_reload_status Linkup starting cpsw1_vlan102
      Oct 9 04:09:19 check_reload_status Linkup starting cpsw1
      Oct 9 04:09:19 check_reload_status Linkup starting cpsw1_vlan101
      Oct 9 04:09:19 check_reload_status Linkup starting cpsw1_vlan100
      Oct 9 04:09:19 check_reload_status Linkup starting cpsw1_vlan103
      Oct 9 04:09:19 check_reload_status Linkup starting cpsw1_vlan102
      Oct 9 04:09:18 kernel cpsw1_vlan101: link state changed to UP
      Oct 9 04:09:18 kernel cpsw1_vlan100: link state changed to UP
      Oct 9 04:09:18 kernel cpsw1_vlan103: link state changed to UP
      Oct 9 04:09:18 kernel cpsw1_vlan102: link state changed to UP
      Oct 9 04:09:18 kernel cpsw1: link state changed to UP
      Oct 9 04:09:18 kernel cpsw1_vlan101: link state changed to DOWN
      Oct 9 04:09:18 kernel cpsw1_vlan100: link state changed to DOWN
      Oct 9 04:09:18 kernel cpsw1_vlan103: link state changed to DOWN
      Oct 9 04:09:18 kernel cpsw1_vlan102: link state changed to DOWN
      Oct 9 04:09:18 kernel cpsw1: link state changed to DOWN
      Oct 9 04:09:18 check_reload_status Linkup starting cpsw1

      1 Reply Last reply Reply Quote 0
      • dsiminiuk
        dsiminiuk last edited by

        I am seeing the exact same errors on every boot:

        pf_busy
        PF was wedged/busy and has been reset. @ 2017-10-13 10:58:59

        Filter Reload
        There were error(s) loading the rules: pfctl: DIOCXCOMMIT: Device busy - The line in question reads [0]: @ 2017-10-13 10:59:02

        These are new following the upgrade to 2.4:

        2.4.0-RELEASE (amd64)
        built on Tue Oct 10 06:43:01 CDT 2017
        FreeBSD 11.1-RELEASE-p1

        Running as a Virtual Machine on Xenserver 7.2. A pair of them actually, both getting the same error.

        Danny

        1 Reply Last reply Reply Quote 0
        • First post
          Last post