From: [EMAIL PROTECTED] > 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?
No, because a trunk(4) is comprised of multiple phyiscal interfaces, not multiple vlan(4)s. You have 2 (or more) physical ports. They can be combined into a trunk(4) aggregated (or failover) port group. This trunk can be used as the 'vlandev' for a vlan(4) interface. And vlan(4) interfaces on multiple systems can be made highly-available via carp(4) by specifying them as your 'carpdev' (or referring to the routing table.) It's a matter of building blocks. DS
