Project

General

Profile

Bug #27885

Allow VM Network Interface to use an MTU over 1500

Added by Jim Shaw almost 3 years ago. Updated almost 3 years ago.

Status:
Done
Priority:
No priority
Assignee:
Marcelo Araujo
Category:
Middleware
Target version:
11.1-U2
Seen in:
11.1
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

When assigning a VM to a Network Interface that has a MTU of 9000. The MTU of the bridge interface is fixed at 1500.

Error is as follows;

bridge1: invalid MTU: 9000(vlan51) != 1500

Related issues

Related to FreeNAS - Bug #27886: Allow VLAN parent interfaces to be used in VMDone

Associated revisions

Revision d99beac2 (diff)
Added by Marcelo Araujo almost 3 years ago

- if_bridge(4) set its MTU based on the first interface attached to it. So the logic here must be, physical interface MTU set on tap(4) and tap attached to if_bridge. Without following the logic above, the bridge MTU will always be 1500 as well as tap. So interfaces with support to JUMBO FRAMES will never be attached to bridge. Ticket: #27885

Revision 9a4d4704 (diff)
Added by Marcelo Araujo almost 3 years ago

- if_bridge(4) set its MTU based on the first interface attached to it. So the logic here must be, physical interface MTU set on tap(4) and tap attached to if_bridge. Without following the logic above, the bridge MTU will always be 1500 as well as tap. So interfaces with support to JUMBO FRAMES will never be attached to bridge. Ticket: #27885

Revision 2e18148c (diff)
Added by Marcelo Araujo almost 3 years ago

- if_bridge(4) set its MTU based on the first interface attached to it. So the logic here must be, physical interface MTU set on tap(4) and tap attached to if_bridge. (#763) Without following the logic above, the bridge MTU will always be 1500 as well as tap. So interfaces with support to JUMBO FRAMES will never be attached to bridge. Ticket: #27885

Revision 64ea641c (diff)
Added by Marcelo Araujo almost 3 years ago

- if_bridge(4) set its MTU based on the first interface attached to it. So the logic here must be, physical interface MTU set on tap(4) and tap attached to if_bridge. (#764) Without following the logic above, the bridge MTU will always be 1500 as well as tap. So interfaces with support to JUMBO FRAMES will never be attached to bridge. Ticket: #27885

History

#1 Updated by Dru Lavigne almost 3 years ago

  • Related to Bug #27886: Allow VLAN parent interfaces to be used in VM added

#2 Updated by Dru Lavigne almost 3 years ago

  • Assignee changed from Release Council to Marcelo Araujo
  • Target version set to 11.1-U2

#3 Updated by Marcelo Araujo almost 3 years ago

  • Status changed from Unscreened to Not Started

#4 Avatar?id=13649&size=24x24 Updated by Ben Gadd almost 3 years ago

  • Due date set to 02/12/2018

Due date updated to reflect the code freeze for 11.1U2.

#5 Avatar?id=13649&size=24x24 Updated by Ben Gadd almost 3 years ago

  • Severity set to New

#6 Updated by Marcelo Araujo almost 3 years ago

  • Status changed from Not Started to In Progress

#7 Updated by Marcelo Araujo almost 3 years ago

  • Status changed from In Progress to Broken

#8 Updated by Marcelo Araujo almost 3 years ago

  • Status changed from Broken to Done

#9 Updated by Dru Lavigne almost 3 years ago

  • Subject changed from Unable to assign VM to Network Interface with MTU 9000 to Allow VM Network Interface to use an MTU over 1500
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

Also available in: Atom PDF