kern/181388: [route] Routes not updated on mtu change
Lev Serebryakov
lev at FreeBSD.org
Tue Aug 20 22:06:40 UTC 2013
Hello, Joe.
You wrote 20 августа 2013 г., 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 nicer
>> 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
JH> routing between segments with a box, then you shouldn't be using
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).
--
// Black Lion AKA Lev Serebryakov <lev at FreeBSD.org>
More information about the freebsd-net
mailing list