Project

General

Profile

Actions
Copy link

Bug #3281

closed

In certain cases, GRE interfaces are missing the "RUNNING" flag at bootup and will not function

Added by Jim Pingle about 11 years ago. Updated almost 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Ermal Luçi
Category:
Interfaces
Target version:
2.2
Start date:
10/21/2013
Due date:
% Done:

100%

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

Description

Still trying to gather information but this has been directly observed on a customer system.

GRE tunnel configured and an interface assigned, with IP configured. The gre0 interface is marked "UP" at boot time but it does NOT have the "RUNNING" flag. In this state, the GRE tunnel will not accept nor initiate traffic over the tunnel. If you run "ifconfig gre0 up" it will then have the RUNNING flag and function as expected.

So far I have not been able to reproduce this in a VM, but it seems to only affect 2.1 and was not a problem on 2.0.

In the observed problem case, the GRE interface was configured, assigned with an IP set, gateway configured, and the GRE gateway was set as the default gateway. There was a static route set to reach the far-side GRE endpoint via a different local gateway. pf was disabled.

Workaround: Adding a shellcmd to "ifconfig gre0 up" at boot time allows it to function.

Actions
Copy link

Also available in: Atom PDF