Project

General

Profile

Actions
Copy link

Bug #8115

closed

After update 2.3.4_1-> 2.4.0 ospf over gre looks broken

Added by Konstantin Pobudzey about 7 years ago. Updated over 5 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
FRR
Target version:
-
Start date:
11/21/2017
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:

Description

#
#site1 ( 2.3.4_1 )
logs
Nov 4 09:47:58 ospfd 45632 Packet[DD]: Neighbor 10.10.10.18 MTU 1400 is larger than [gre1:10.10.10.25]'s MTU 1376
Nov 4 09:47:53 ospfd 45632 Packet[DD]: Neighbor 10.10.10.18 MTU 1400 is larger than [gre1:10.10.10.25]'s MTU 1376
Nov 4 09:47:48 ospfd 45632 Packet[DD]: Neighbor 10.10.10.18 MTU 1400 is larger than [gre1:10.10.10.25]'s MTU 1376
Nov 4 09:47:43 ospfd 45632 Packet[DD]: Neighbor 10.10.10.18 MTU 1400 is larger than [gre1:10.10.10.25]'s MTU 1376

#site2 ( updated to 2.4.0 ) <- ospf broken
#route
10.10.10.25 link#12 UH 2322 1376 gre2

#logs site2
Nov 4 16:50:04 ospfd 52879 *** sendmsg in ospf_write failed to 224.0.0.5, id 0, off 0, len 64, interface gre2, mtu 1400: Permission denied

It looks like site2 after upgrade it not sending correct MTU info to it peer on site1
GRE header ignored may be .

#After rollback from 2.4.0 to 2.3.4 all working as expected.

site1 site2
-----------IPSEC transport mode---------------------- |--------GRE------------------------
ospf stuck in exstart |----------GRE----------------------
-----------IPSEC transport mode----------------------

MTU is 1400 on GRE Interface

Again with version 2.3.4_1 on both sites all working as expected

Let me know , if more details needed

Actions
Copy link

Also available in: Atom PDF