From owner-freebsd-net@FreeBSD.ORG Tue Aug 20 22:24:00 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A71FE6F1; Tue, 20 Aug 2013 22:24:00 +0000 (UTC) (envelope-from lists@rewt.org.uk) Received: from hosted.mx.as41113.net (abby.lhr1.as41113.net [91.208.177.20]) by mx1.freebsd.org (Postfix) with ESMTP id 6D9D62135; Tue, 20 Aug 2013 22:23:58 +0000 (UTC) Received: from jwhlaptop (unknown [91.208.177.70]) (using TLSv1.2 with cipher AES128-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: lists@rewt.org.uk) by hosted.mx.as41113.net (Postfix) with ESMTPSA id 3cKRP80DT3zdr; Tue, 20 Aug 2013 23:23:55 +0100 (BST) From: "Joe Holden" To: References: <201308190700.r7J701I9045665@freefall.freebsd.org> <5211D812.5070308@rewt.org.uk> <20130820011254.GZ94127@funkthat.com> <521327EB.6010407@rewt.org.uk> <162512031.20130820124633@serebryakov.spb.ru> <52137B62.3000405@rewt.org.uk> <648062544.20130821020631@serebryakov.spb.ru> In-Reply-To: <648062544.20130821020631@serebryakov.spb.ru> Subject: RE: kern/181388: [route] Routes not updated on mtu change Date: Tue, 20 Aug 2013 23:23:49 +0100 Message-ID: <17fb01ce9df3$f2cc6ba0$d86542e0$@rewt.org.uk> X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQJP8AXG1yGQWVh/gFlhKY93jfPlgAF8lD13AdiHrE0CosAU4QJ3WUG+AhW17pgCQOJ1wJg12Urw Content-Language: en-gb Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Aug 2013 22:24:00 -0000 You have a good point wrt VLANs on Windows but everyone uses Intel nics.... right? :P > -----Original Message----- > From: Lev Serebryakov [mailto:lev@FreeBSD.org] > Sent: 20 August 2013 23:07 > To: Joe Holden > Cc: freebsd-net@freebsd.org > Subject: Re: kern/181388: [route] Routes not updated on mtu change > > Hello, Joe. > You wrote 20 ??????? 2013 ?., 18:21:22: > > >> JH> vlan interfaces achieve the same thing without having to mess > >> JH> about with mtus on routes and also give you an interface to work > >> JH> with, a much nicer method comparatively. > >> But it could put huge load on routing between these two segments > >> and/or requires managed switches. > >> > JH> Neither really, don't need a managed switch to use dot1q and if > JH> you're routing between segments with a box, then you shouldn't be > JH> using multiple ranges in the same broadcast domain anyway. > JH> Networking 101 > > (1) As far as I know, Windows works very badly with VLANs, it depends on > drivers and Windows doesn't have unified VLAN management/support, > opposite to UNIX systems. My desktop adapter (Atheros AR8121), for > example, supports VLANs on hardware level and it works with FreeBSD, but > "desktop windows" (not Windows Server) drivers doesn't provide any way > to set VLAN. So, to put any Windows system, driver- and adapter- > independent, to VLAN, you need to assign VLAN at switch on per-port basis. > You need managed switch. Maybe, something was changed in Windows 8, I > don't know, but Windows 7 (even Ultimate edition) doesn't have any VLAN > management. > > (2) As far as I understand, "topicstarter" has Windows and FreeBSD > machines in one segment (with different MTUs) and you suggest to put > them in different segments (via VLANs), so there WAS NO routing at all, and > now it is two segments, which needs routing between them. But, maybe, I > understood John-Mark Gurney wrong, and they had two broadcast domains > on one network (and double-addressed interface in router). > > > -- > // Black Lion AKA Lev Serebryakov