Project

General

Profile

Actions
Copy link

Feature #8052

closed

Separate MTU interface values for IPv4 and IPv6

Added by Kristopher Kolpin over 6 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
-
Start date:
11/03/2017
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

Some ISPs do not offer IPv6 connetivity yet or offer it via a tunnelling mechanism.

As such, in some cases PMTU discovery can fail and it is sometimes necessary to explicitly define a lower MTU interface value.

Unfortunately, due to the 20 bytes overhead of a 6in4 tunnel an IPv6 MTU value of IPv4MTU - 20 bytes is necessary.

Shrinking the MTU to accommodate IPv6 results in poor IPv4 connectivity and vise versa.

Separate MTU interface values in the web GUI are proposed for IPv4 and IPv6 routes.

Actions
Copy link
 #1

Updated by Jim Pingle over 6 years ago

  • Target version changed from 2.4.2 to 2.4.3
Actions
Copy link
 #2

Updated by Jim Pingle about 6 years ago

  • Target version changed from 2.4.3 to 2.4.4
Actions
Copy link
 #3

Updated by Jim Pingle over 5 years ago

  • Status changed from New to Rejected
  • Target version deleted (2.4.4)

If you have a 6in4 tunnel with a lower MTU, then the lower MTU would go on the 6in4 tunnel, not the pfSense WAN. The routes should follow from there, bar some other issue such as #6868

Actions
Copy link

Also available in: Atom PDF