Project

General

Profile

Actions
Copy link

Bug #7730

open

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

Added by Richie M over 7 years ago. Updated over 7 years ago.

Status:
New
Priority:
High
Assignee:
-
Category:
Interfaces
Target version:
-
Start date:
07/27/2017
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3.4
Affected Architecture:

Description

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.


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

Original Forum Thread: https://forum.pfsense.org/index.php?topic=134258.0

Actions
Copy link
 #1

Updated by Richie M over 7 years ago

to clarify previous cluster sync comment:
If we make the change as described above on secondary the tunnel stays up but obviously the cluster sync does not occur.

Actions
Copy link

Also available in: Atom PDF