Hi -net folk...
Awhile back, I was trying to figure out how bridge(4) worked, but
discovered that the manpage didn't list all the sysctls necessary to
configure the bridge. I filed a PR (22060) asking someone to look into
this. I subsequently lost interest in bridge(4), but gained a commit
bit, the result being that I own a PR for something I know close to
zero about.
I've made the following diff against the bridge.4 manpage in -CURRENT.
Can someone tell me if this is anywhere close to the state of reality?
Thanks for any assistance!
Bruce.
Index: bridge.4
===================================================================
RCS file: /home/ncvs/src/share/man/man4/bridge.4,v
retrieving revision 1.12
diff -u -r1.12 bridge.4
--- bridge.4 2001/04/18 15:51:26 1.12
+++ bridge.4 2001/06/13 21:08:09
@@ -44,6 +44,40 @@
.Ar allow
rule if we want ARP and other non-IP packets to flow through the
bridge.
+.Pp
+The bridge configuration is controlled by the
+.Bd -literal
+ net.link.ether.bridge_cfg
+.Ed
+.Pp
+.Nm sysctl
+variable.
+It consists of a comma-separated list of
+.Ar interface:cluster
+pairs, where all interfaces with the same
+.Ar cluster
+number will
+be bridged together.
+.Pp
+Another
+.Nm sysctl
+variable reinitializes the bridge; this is required if bridged
+configurations include loadable interfaces.
+After loading new
+interface drivers, setting the:
+.Bd -literal
+ net.link.ether.bridge_refresh
+.Ed
+.Pp
+variable to 1 will cause the bridge to reinitialize itself.
+.Sh EXAMPLES
+.Pp
+The following command will cause the ep0 and fxp0 interfaces to be
+bridged together, and the fxp1 and de0 interfaces to be bridged
+together:
+.Bd -literal
+ sysctl -w net.link.ether.bridge_cfg ep0:0,fxp0:0,fxp1:1,de0:1
+.Ed
.Sh BUGS
.Pp
Care must be taken not to construct loops in the bridge topology.
PGP signature
