From 400b45d590b883050e171a34daec3fe40b58b76e Mon Sep 17 00:00:00 2001 From: "Robin H. Johnson" Date: Sun, 12 Dec 2010 00:43:05 +0000 Subject: Final documentation cleanup for updated bridge code. Specifically document how to handle the case of explicitly starting a bridge and then dynamically adding interfaces to it. brctl_br0='' bridge_add_eth0='br0' --- doc/net.example.Linux.in | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) (limited to 'doc/net.example.Linux.in') diff --git a/doc/net.example.Linux.in b/doc/net.example.Linux.in index 7955fe3d..42e5477c 100644 --- a/doc/net.example.Linux.in +++ b/doc/net.example.Linux.in @@ -787,11 +787,18 @@ #bridge_add_eth0="br0" #bridge_add_eth1="br0" +# NOTE: If you want to manually start an empty bridge, and then dynamically add +# ports to it you must set at least one of the following variables based on the +# interface name, so that we can pick it up from your configuration. Even an +# empty value variable is fine, but at least one of them must be set: +# brctl_IFVAR + # You need to configure the ports to null values so dhcp does not get started #config_eth0="null" #config_eth1="null" -# Finally give the bridge an address - dhcp or a static IP +# Finally give the bridge an address - dhcp or a static IP, this is assigned to +# the bridge when the bridge is explicitly started. #config_br0="dhcp" # may not work when adding ports dynamically #config_br0="192.168.0.1/24" @@ -812,11 +819,6 @@ #forward_delay_br0="10" #hairpin_mode_eth0="1" -# If you want to start an empty bridge, and then dynmically add ports to it you -# MUST set the following variables (with the correct interface name). -# If you get the error "Misconfigured static bridge detected", this means you. -#bridge_br0='' - #----------------------------------------------------------------------------- # RFC 2684 Bridge Support # For RFC 2684 bridge support emerge net-misc/br2684ctl -- cgit v1.2.3