Lines 96-115
Link Here
|
96 |
.Xr sysctl 8 |
96 |
.Xr sysctl 8 |
97 |
node |
97 |
node |
98 |
.Va net.link.bridge.inherit_mac |
98 |
.Va net.link.bridge.inherit_mac |
99 |
has non-zero value, newly created bridge will inherit MAC address |
99 |
has a non-zero value, the newly created bridge will inherit the MAC |
100 |
from its first member instead of choosing random link-level address. |
100 |
address from its first member instead of choosing a random link-level |
101 |
This will provide more predictable bridge MAC without any |
101 |
address. |
102 |
additional configuration, but currently this feature is known |
102 |
This will provide more predictable bridge MAC addresses without any |
103 |
to break some L2 protocols, for example PPPoE that is provided |
103 |
additional configuration, but currently this feature is known to break |
104 |
by |
104 |
some L2 protocols, for example PPPoE that is provided by |
105 |
.Xr ng_pppoe 4 |
105 |
.Xr ng_pppoe 4 |
106 |
and |
106 |
and |
107 |
.Xr ppp 8 . |
107 |
.Xr ppp 8 . |
108 |
Now this feature is considered as experimental and is turned off |
108 |
Currently this feature is considered as experimental and is turned off |
109 |
by-default. |
109 |
by default. |
110 |
.Pp |
110 |
.Pp |
111 |
A bridge can be used to provide several services, such as a simple |
111 |
A bridge can be used to provide several services, such as a simple |
112 |
802.11-to-Ethernet bridge for wireless hosts, and traffic isolation. |
112 |
802.11-to-Ethernet bridge for wireless hosts, or traffic isolation. |
113 |
.Pp |
113 |
.Pp |
114 |
A bridge works like a switch, forwarding traffic from one interface |
114 |
A bridge works like a switch, forwarding traffic from one interface |
115 |
to another. |
115 |
to another. |
Lines 130-139
Link Here
|
130 |
All additional members are required to have exactly the same value. |
130 |
All additional members are required to have exactly the same value. |
131 |
.Pp |
131 |
.Pp |
132 |
The TOE, TSO, TXCSUM and TXCSUM6 capabilities on all interfaces added to the |
132 |
The TOE, TSO, TXCSUM and TXCSUM6 capabilities on all interfaces added to the |
133 |
bridge are disabled if any of the interfaces doesn't support/enable them. |
133 |
bridge are disabled if any of the interfaces do not support/enable them. |
134 |
The LRO capability is always disabled. |
134 |
The LRO capability is always disabled. |
135 |
All the capabilities are restored when the interface is removed from bridge. |
135 |
All the capabilities are restored when the interface is removed from the |
136 |
Changing capabilities in run time may cause NIC reinit and the link flap. |
136 |
bridge. |
|
|
137 |
Changing capabilities in run time may cause the NIC to reinitialize and |
138 |
the link to flap. |
137 |
.Pp |
139 |
.Pp |
138 |
The bridge supports |
140 |
The bridge supports |
139 |
.Dq monitor mode , |
141 |
.Dq monitor mode , |
Lines 198-204
Link Here
|
198 |
IPv6 addresses on the member interface will be automatically removed |
200 |
IPv6 addresses on the member interface will be automatically removed |
199 |
before the interface is added. |
201 |
before the interface is added. |
200 |
.Pp |
202 |
.Pp |
201 |
This behavior can be disabled by setting |
203 |
This behaviour can be disabled by setting the |
202 |
.Xr sysctl 8 |
204 |
.Xr sysctl 8 |
203 |
variable |
205 |
variable |
204 |
.Va net.link.bridge.allow_llz_overlap |
206 |
.Va net.link.bridge.allow_llz_overlap |