|TRUNK(4)||Device Drivers Manual||TRUNK(4)|
trunkinterface allows aggregation of multiple network interfaces as one virtual
trunk interface can be created using the
create command. It can use different link
aggregation protocols specified using the
proto option. Child interfaces can be added using the
trunkport child-iface option
and removed using the
The driver currently supports the trunk protocols
default). The protocols determine which ports are used for outgoing traffic
and whether a specific port accepts incoming traffic. The interface link
state is used to validate if the port is active or not.
# ifconfig bge0 up # ifconfig bge1 up # ifconfig trunk0 trunkport bge0 trunkport bge1 \ 192.168.1.1 netmask 255.255.255.0
The following example uses an active failover trunk to set up roaming between wired and wireless networks using two network devices. Whenever the wired master interface is unplugged, the wireless failover device will be used:
# ifconfig em0 up # ifconfig ath0 nwid my_net up # ifconfig trunk0 trunkproto failover trunkport em0 trunkport ath0 \ 192.168.1.1 netmask 255.255.255.0
trunkdevice first appeared in OpenBSD 3.8.
trunkdriver was written by Reyk Floeter ⟨firstname.lastname@example.org⟩.
roundrobinrequire a switch which supports IEEE 802.3ad static link aggregation; otherwise protocols such as inet6(4) duplicate address detection (DAD) cannot properly deal with duplicate packets.
There is no way to configure LACP administrative variables, including system and port priorities. The current implementation always performs active-mode LACP and uses 0x8000 as system and port priorities.
|October 22, 2009||OpenBSD-5.1|