2.3.4_1 greX: loop detected when hit save on filter rules or interfaces



  • upgraded from 2.2.6
    anytime we hit save in the GUI for interface or filter rules, even if no change was made, we start getting Jul 25 14:50:02 <histname>kernel: greX: loop detected spam in dmesg/system.log.  Our GRE tunnel goes down.

    Any cluster sync activity from the Primary to Secondary also causes this issue.

    We have to do a save on the GRE interface in the web GUI (this downs/ups the interface) and the tunnel starts working again.

    Please advise on what additional information I can provide or where else I can look to diagnose this issue.

    
    Jul 25 14:50:01 hostname kernel: gre0: loop detected
    Jul 25 14:50:02 hostname kernel: gre1: loop detected
    Jul 25 14:50:02 hostname kernel: gre0: loop detected
    Jul 25 14:50:02 hostname kernel: gre1: loop detected
    Jul 25 14:50:02 hostname kernel: gre0: loop detected
    Jul 25 14:50:03 hostname kernel: gre1: loop detected
    Jul 25 14:50:03 hostname kernel: gre0: loop detected
    Jul 25 14:50:03 hostname kernel: gre1: loop detected
    
    ```</histname>


  • ive logged a bug on this issue:  https://redmine.pfsense.org/issues/7730