From: Jason Dixon (jasondixongroup.net)
Date: Tue Aug 01 2006 - 17:26:06 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Aug 1, 2006, at 5:23 PM, Tim Pushor wrote:

> Stuart Henderson wrote:
>> The vlan idea makes a fair bit of sense - carp(4) over vlan(4)
>> over trunk(4) over $some_nic(4) or some other mix - but if this
>> is used for security be aware that your switch then becomes a
>> security device. Google will find more information, including
>> http://www.cisco.com/en/US/products/hw/switches/ps708/
>> products_white_paper09186a008013159f.shtml
>>
> Thinking about it more, isn't it carp over trunk over vlan over
> nic? I'm gonna give it a shot here in the next day or so.

No. The OpenBSD trunk device is for link aggregation and failover,
both properties of the physical layer. The OpenBSD vlan device
provides access to VLAN segments (802.1Q), properties of the data-
link and network layers.

Again, make sure you're not confusing vendor terminologies here. An
OpenBSD trunk is what many vendors refer to as teaming or bonding
(some do refer to it as trunking). However, many(?) vendors refer to
a trunk as a port carrying multiple tagged VLANs.

--
Jason Dixon
DixonGroup Consulting
http://www.dixongroup.net

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]