qiurui
/
freebsd-doc
mirror of https://git.FreeBSD.org/doc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove whitespaces at end of lines 

No content changes.
This commit is contained in:
Benedict Reuschling 2025-08-29 09:50:53 +00:00
parent 02857856ac
commit f19e4a3dba
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
documentation/content/en/books/handbook/advanced-networking/_index.adoc
View File

@ -1325,7 +1325,7 @@ cu -l $PTS
By default, when FreeBSD is accepting a new connection, it tries to perform a role switch and become master.
Some older Bluetooth devices which do not support role switching will not be able to connect.
Since role switching is performed when a new connection is being established, it is not possible to ask the remote device if it supports role switching.
Since role switching is performed when a new connection is being established, it is not possible to ask the remote device if it supports role switching.
However, there is a HCI option to disable role switching on the local side:
[source,shell]
@ -1454,7 +1454,7 @@ The STP protocol detects loops and puts redundant links into a blocked state.
Should one of the active links fail, STP calculates a different tree and enables one of the blocked paths to restore connectivity to all points in the network.
The Rapid Spanning Tree Protocol (RSTP or 802.1w) provides backwards compatibility with legacy STP.
RSTP provides faster convergence and exchanges information with neighboring switches to quickly transition to forwarding mode without creating loops.
RSTP provides faster convergence and exchanges information with neighboring switches to quickly transition to forwarding mode without creating loops.
FreeBSD supports RSTP and STP as operating modes, with RSTP being the default mode.
STP can be enabled on member interfaces using man:ifconfig[8].
@ -1527,7 +1527,7 @@ Sticky entries are never aged out of the cache or replaced, even if the address
This gives the benefit of static address entries without the need to pre-populate the forwarding table.
Clients learned on a particular segment of the bridge cannot roam to another segment.
+
An example of using sticky addresses is to combine the bridge with VLANs in order to isolate customer networks without wasting IP address space.
An example of using sticky addresses is to combine the bridge with VLANs in order to isolate customer networks without wasting IP address space.
Consider that `CustomerA` is on `vlan100`, `CustomerB` is on `vlan101`, and the bridge has the address `192.168.0.1`:
+
[source,shell]
@ -1558,7 +1558,7 @@ The following example sets the maximum number of Ethernet devices for `CustomerA
# ifconfig bridge0 ifmaxaddr vlan100 10
....
Bridge interfaces also support monitor mode, where the packets are discarded after man:bpf[4] processing and are not processed or forwarded further.
Bridge interfaces also support monitor mode, where the packets are discarded after man:bpf[4] processing and are not processed or forwarded further.
This can be used to multiplex the input of two or more interfaces into a single man:bpf[4] stream.
This is useful for reconstructing the traffic for network taps that transmit the RX/TX signals out through two separate interfaces.
For example, to read the input from four network interfaces as one stream:
@ -1688,7 +1688,7 @@ Each LAG is composed of ports of the same speed, set to full-duplex operation, a
Typically, there is only one LAG which contains all the ports.
In the event of changes in physical connectivity, LACP will quickly converge to a new configuration.
+
LACP balances outgoing traffic across the active ports based on hashed protocol header information and accepts incoming traffic from any active port.
LACP balances outgoing traffic across the active ports based on hashed protocol header information and accepts incoming traffic from any active port.
The hash includes the Ethernet source and destination address and, if available, the VLAN tag, and the IPv4 or IPv6 source and destination address.
roundrobin::
@ -1844,7 +1844,7 @@ ifconfig_lagg0="laggproto failover laggport fxp0 laggport fxp1 10.0.0.15/24"
[example]
====
For laptop users, it is usually desirable to configure the wireless device as a secondary which is only used when the Ethernet connection is not available.
For laptop users, it is usually desirable to configure the wireless device as a secondary which is only used when the Ethernet connection is not available.
With man:lagg[4], it is possible to configure a failover which prefers the Ethernet connection for both performance and security reasons, while maintaining the ability to transfer data over the wireless connection.
This is achieved by overriding the Ethernet interface's MAC address with that of the wireless interface.