Project

General

Profile

Actions
Copy link

Bug #2674

closed

MTU setting hardcoded 1280 for gif interfaces and in RADVD config

Added by Keenan Tims about 12 years ago. Updated over 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
2.1
Start date:
11/06/2012
Due date:
% Done:

100%

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

Description

The MTU setting in the GUI for gif interfaces is ignored, and set to hardcoded or default value of 1280. Likewise, RADVD advertises a hardcoded link MTU, which should be read from interface config / appropriate defaults for link type.

Actions
Copy link
 #1

Updated by Seth Mos about 12 years ago

Indeed I did. Do we want to always advertise the local interface MTU or the WAN MTU?

Actions
Copy link
 #2

Updated by Chris Buechler about 12 years ago

  • Category set to Interfaces
  • Target version set to 2.1
  • Affected Version set to 2.1-IPv6

Normally I'd say the local interface MTU, but since there's no MSS clamping on v6 for the time being, probably the WAN MTU is best to avoid issues.

Actions
Copy link
 #3

Updated by Ermal Luçi almost 12 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by Adam Thompson over 11 years ago

As of {2.1-RC1 (amd64) built on Tue Aug 13 14:23:15 EDT 2013 FreeBSD 8.3-RELEASE-p9}, GIF tunnels still default to 1280. I can override up to 1480 and that appears to work correctly, but I am seeing strange fragmentation problems no matter what MTU I use.

Actions
Copy link
 #5

Updated by Chris Buechler over 11 years ago

  • Status changed from Feedback to Resolved

The "strange fragmentation problems" are a separate issue entirely (current PF has issues w/v6 frags).

Actions
Copy link

Also available in: Atom PDF