Project

General

Profile

Actions
Copy link

Bug #3080

closed

2.1-RC0 (i386) - GRE Interface not getting correct/configured MTU at boot time

Added by Dirk M over 12 years ago. Updated about 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
-
Start date:
07/07/2013
Due date:
% Done:

0%

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

Description

I'm having a working GREoverIPSec + OSPF environment (Cisco C876 <-> pfSense). Today I just saw that a GRE interface was not getting the configured MTU (1400) after rebooting. Well you might know that OSPFs is not properly working (stuck in exstart) sometimes due to an MTU mismatch between OSPF neighbors.

ifconfig output after reboot:

gre0: flags=9051<UP,POINTOPOINT,RUNNING,LINK0,MULTICAST> metric 0 mtu 1476
tunnel inet xxx.xxx.xxx.xxx --> xxx.xxx.xxx.xxx
inet 172.16.0.2 --> 172.16.0.1 netmask 0xffffff00
inet6 fe80::xxxx:xxxx:xxxx:xxxx%gre0 prefixlen 64 scopeid 0x9
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>

ifconfig output after reapplying GRE settings on the web-interface:

gre0: flags=9051<UP,POINTOPOINT,RUNNING,LINK0,MULTICAST> metric 0 mtu 1400
tunnel inet xxx.xxx.xxx.xxx --> xxx.xxx.xxx.xxx
inet 172.16.0.2 --> 172.16.0.1 netmask 0xffffff00
inet6 fe80::xxxx:xxxx:xxxx:xxxx%gre0 prefixlen 64 scopeid 0x9
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>

Cheers,
Dirk

Actions
Copy link
 #1

Updated by Chris Buechler about 11 years ago

  • Status changed from New to Resolved

works in 2.2 (and probably newer 2.1x versions than this referenced, but didn't test those)

Actions
Copy link

Also available in: Atom PDF