5fc175b7b4
The name trunk is misused as the networking term trunk means carrying multiple VLANs over a single connection. The IEEE standard for link aggregation (802.3 section 3) does not talk about 'trunk' at all while it is used throughout IEEE 802.1Q in describing vlans. The lagg(4) driver provides link aggregation, failover and fault tolerance. Discussed on: current@
47 lines
1.2 KiB
Makefile
47 lines
1.2 KiB
Makefile
# From: @(#)Makefile 8.1 (Berkeley) 6/5/93
|
|
# $FreeBSD$
|
|
|
|
.include <bsd.own.mk>
|
|
|
|
PROG= ifconfig
|
|
|
|
SRCS= ifconfig.c # base support
|
|
|
|
#
|
|
# NB: The order here defines the order in which the constructors
|
|
# are called. This in turn defines the default order in which
|
|
# status is displayed. Probably should add a priority mechanism
|
|
# to the registration process so we don't depend on this aspect
|
|
# of the toolchain.
|
|
#
|
|
SRCS+= af_link.c # LLC support
|
|
SRCS+= af_inet.c # IPv4 support
|
|
SRCS+= af_inet6.c # IPv6 support
|
|
SRCS+= af_atalk.c # AppleTalk support
|
|
|
|
SRCS+= ifclone.c # clone device support
|
|
SRCS+= ifmac.c # MAC support
|
|
SRCS+= ifmedia.c # SIOC[GS]IFMEDIA support
|
|
SRCS+= ifvlan.c # SIOC[GS]ETVLAN support
|
|
SRCS+= ifieee80211.c # SIOC[GS]IEEE80211 support
|
|
|
|
SRCS+= ifcarp.c # SIOC[GS]VH support
|
|
SRCS+= ifgroup.c # ...
|
|
SRCS+= ifpfsync.c # pfsync(4) support
|
|
|
|
SRCS+= ifbridge.c # bridge support
|
|
SRCS+= iflagg.c # lagg support
|
|
|
|
.if ${MK_IPX_SUPPORT} != "no" && !defined(RELEASE_CRUNCH)
|
|
SRCS+= af_ipx.c # IPX support
|
|
DPADD= ${LIBIPX}
|
|
LDADD= -lipx
|
|
.endif
|
|
|
|
MAN= ifconfig.8
|
|
|
|
CFLAGS+= -Wall -Wmissing-prototypes -Wcast-qual -Wwrite-strings -Wnested-externs
|
|
WARNS?= 0
|
|
|
|
.include <bsd.prog.mk>
|