Date: Wed, 21 Aug 2013 02:06:31 +0400 From: Lev Serebryakov <lev@FreeBSD.org> To: Joe Holden <lists@rewt.org.uk> Cc: freebsd-net@freebsd.org Subject: Re: kern/181388: [route] Routes not updated on mtu change Message-ID: <648062544.20130821020631@serebryakov.spb.ru> In-Reply-To: <52137B62.3000405@rewt.org.uk> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Joe. You wrote 20 =D0=B0=D0=B2=D0=B3=D1=83=D1=81=D1=82=D0=B0 2013 =D0=B3., 18:21= :22: >> JH> vlan interfaces achieve the same thing without having to mess about = with >> JH> mtus on routes and also give you an interface to work with, a much n= icer >> JH> 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 you're= =20 JH> routing between segments with a box, then you shouldn't be using=20 JH> multiple ranges in the same broadcast domain anyway. 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). --=20 // Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?648062544.20130821020631>