Sg-1000 issue



  • i keep getting the below almost everyday, checked all the rules and aliases but cant seem to figure out whats causing this

    
    pf_busy
    
        PF was wedged/busy and has been reset. @ 2017-06-20 06:22:43
        PF was wedged/busy and has been reset. @ 2017-06-21 12:20:21
    
    Filter Reload
    
        There were error(s) loading the rules: pfctl: DIOCXCOMMIT: Device busy - The line in question reads [0]: @ 2017-06-20 06:22:44
        There were error(s) loading the rules: pfctl: DIOCXCOMMIT: Device busy - The line in question reads [0]: @ 2017-06-21 12:20:22
    
    

  • Rebel Alliance Developer Netgate

    I'm not seeing that here on either of mine. What packages, if any, do you have installed on there? And what services are enabled?



  • no packages other than cron, openvpn server and client but i used to get those even without them, i tried creating aliases and rules from scratch but its still same



  • i use one limiter, no traffic shaping as it doesnt work on 2.4 anyways, 2 schedules, NAT, port forwards and thats about it



  • This seems to be my standard response at the moment, but are you using pppoe?
    I see the same lines, seems to coincide with dns mess as well as IP change at the ISP end.
    Although recently it's been fine



  • yes i use pppoe, i updated to latest snap today so lets see if i still get those or no.
    Btw i have 2 wans configured, one is pppoe and other is on direct Ethernet connection and for both i have static ips but using VLANS, the pppoe connection always gives the same ip so my ips never change, the pppoe connection might go up and down though



  • i still get the error using 23rd snapshot



  • i noticed when the openvpn tunnel is restarted or some settings changed in it that time this error occurs



  • @jimp:

    I'm not seeing that here on either of mine. What packages, if any, do you have installed on there? And what services are enabled?

    i tested this on another system and this error comes if the pppoe connection is reset from isp end or they force a disconnection causing pfsense to reconnect pppoe and when that happens this error comes