Actions
Bug #8585
closed
Logical interface MTU matches configuration of its physical port channel, not its own configuration
Start date:
06/20/2018
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:
Description
If a port channel is configured with an MTU of 9000, but one of the VLAN interfaces on that port channel is configured with 1500, the port channel configuration is applied to the port, not the correct one from the logical configuration. Screenshots attached. This is causing issues internally for PMTUD.
Files
| Screenshot at Jun 20 09-12-07.png (51.5 KB) Screenshot at Jun 20 09-12-07.png | Port Channel 1 MTU Status | ||
| Screenshot at Jun 20 09-13-18.png (91.1 KB) Screenshot at Jun 20 09-13-18.png | WAN MTU Status | ||
| Screenshot at Jun 20 09-07-45.png (125 KB) Screenshot at Jun 20 09-07-45.png | Port Channel 1 MTU Configuration | ||
| Screenshot at Jun 20 09-07-18.png (126 KB) Screenshot at Jun 20 09-07-18.png | WAN MTU Configuration |
Updated by Jim Pingle over 5 years ago
- Category changed from Interfaces to LAGG Interfaces
Updated by Viktor Gurov almost 5 years ago
This PR adds additional checking for lagg vlan interface (lagg with dot) to set_interface_mtu():
https://github.com/pfsense/pfsense/pull/4247
Updated by Jim Pingle over 4 years ago
- Status changed from New to Pull Request Review
- Target version set to 2.5.0
Updated by Renato Botelho over 4 years ago
- Status changed from Pull Request Review to Feedback
- Assignee set to Renato Botelho
- % Done changed from 0 to 100
PR has been merged. Thanks!
Updated by Anonymous 
Actions