From owner-freebsd-net@FreeBSD.ORG  Mon Mar  9 18:30:30 2015
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 80D75A9
 for <freebsd-net@FreeBSD.org>; Mon,  9 Mar 2015 18:30:30 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 674493BC
 for <freebsd-net@FreeBSD.org>; Mon,  9 Mar 2015 18:30:30 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t29IUUDx062984
 for <freebsd-net@FreeBSD.org>; Mon, 9 Mar 2015 18:30:30 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 194855] VLAN interface MTU does not change on changing the base
 interface MTU
Date: Mon, 09 Mar 2015 18:30:30 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: john@jnielsen.net
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-194855-2472-RIh1UHUtYZ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-194855-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-194855-2472@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2015 18:30:30 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194855

John Nielsen <john@jnielsen.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |john@jnielsen.net

--- Comment #1 from John Nielsen <john@jnielsen.net> ---
I don't think that VLAN MTU should change automatically. In the example given
it does make sense to either give a warning or prevent the parent interface MTU
from being reduced smaller than any of the VLAN MTU (or conversely increasing
the VLAN MTU above that of the parent), but I don't think that increasing the
MTU on the parent should have any effect on the VLAN interfaces' MTU. I have
certainly had cases where I used different MTU settings for different VLANs on
the same parent interface (but of course not higher than the parent).

-- 
You are receiving this mail because:
You are the assignee for the bug.