freebsd-dev/share/man/man4/bridge.4

112 lines
2.4 KiB
Groff
Raw Normal View History

1998-12-21 22:37:53 +00:00
.\"
1999-08-28 00:22:10 +00:00
.\" $FreeBSD$
1998-12-21 22:37:53 +00:00
.\"
.Dd September 28, 1998
1998-12-21 22:37:53 +00:00
.Dt BRIDGE 4
.Os
.Sh NAME
.Nm bridge
2001-04-18 15:54:10 +00:00
.Nd bridging support
1998-12-21 22:37:53 +00:00
.Sh DESCRIPTION
2000-11-14 11:20:58 +00:00
Starting from version 2.2.8,
.Fx
supports bridging on Ethernet-type
interfaces.
This is enabled by including the following line in the kernel configuration
file:
2000-11-14 11:20:58 +00:00
.Pp
.Dl "options BRIDGE"
2000-11-14 11:20:58 +00:00
.Pp
Runtime operation of the bridge is controlled by several
.Xr sysctl 8
variables.
The
.Va net.link.ether.bridge
variable can be set to
.Li 1
to enable bridging, or set to
.Li 0
to disable it.
2000-11-14 11:20:58 +00:00
.Pp
The
.Va net.link.ether.bridge_ipfw
.Xr sysctl 8
variable can be set to
.Li 1
to enable
.Xr ipfw 8
filtering on bridged packets.
Note that
.Xr ipfw 8
1998-12-21 22:37:53 +00:00
rules only apply
to IP packets.
Non-IP packets are subject to the default
.Xr ipfw 8
rule
.Pq number 65535
which must be an
1998-12-21 22:37:53 +00:00
.Ar allow
rule if ARP and other non-IP packets need to flow through the
1998-12-21 22:37:53 +00:00
bridge.
.Pp
The bridge configuration is controlled by the
.Va net.link.ether.bridge_cfg
.Xr sysctl 8
variable.
It consists of a comma-separated list of
.Ar interface : Ns Ar cluster
pairs, where all interfaces with the same
.Ar cluster
number will
be bridged together.
.Pp
Another
.Xr sysctl 8
variable reinitializes the bridge; this is required if bridged
configurations include loadable interfaces.
After loading new interface drivers, setting the
.Va net.link.ether.bridge_refresh
variable to
.Li 1
will cause the bridge to reinitialize itself.
.Sh EXAMPLES
The following command will cause the
.Li ep0
and
.Li fxp0
interfaces to be bridged together, and the
.Li fxp1
and
.Li de0
interfaces to be bridged together:
.Pp
.Dl "sysctl -w net.link.ether.bridge_cfg ep0:0,fxp0:0,fxp1:1,de0:1"
1998-12-21 22:37:53 +00:00
.Sh BUGS
Care must be taken not to construct loops in the bridge topology.
The kernel supports only a primitive form of loop detection, by disabling
some interfaces when a loop is detected.
No support for a daemon running the
1998-12-21 22:37:53 +00:00
spanning tree algorithm is currently provided.
.Pp
With bridging active, interfaces are in promiscuous mode,
thus causing some load on the system to receive and filter
out undesired traffic.
.Pp
Extended functionality to enable bridging selectively on clusters
of interfaces is still in the works.
.Pp
Interfaces that cannot be put into promiscuous mode or that don't
support sending packets with arbitrary Ethernet source addresses
are not compatible with bridging.
1998-12-21 22:37:53 +00:00
.Sh SEE ALSO
.Xr ip 4 ,
.Xr ng_bridge 4 ,
1998-12-21 22:37:53 +00:00
.Xr ipfw 8 ,
.Xr sysctl 8
1998-12-21 22:37:53 +00:00
.Sh HISTORY
.Nm
2000-11-14 11:20:58 +00:00
bridging was introduced in
.Fx 2.2.8
by
.An Luigi Rizzo Aq luigi@iet.unipi.it .