| bridge.4 (161261) | bridge.4 (162404) |
|---|---|
| 1.\" $NetBSD: bridge.4,v 1.5 2004/01/31 20:14:11 jdc Exp $ 2.\" 3.\" Copyright 2001 Wasabi Systems, Inc. 4.\" All rights reserved. 5.\" 6.\" Written by Jason R. Thorpe for Wasabi Systems, Inc. 7.\" 8.\" Redistribution and use in source and binary forms, with or without --- 19 unchanged lines hidden (view full) --- 28.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 29.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 30.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 31.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 32.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 33.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 34.\" POSSIBILITY OF SUCH DAMAGE. 35.\" | 1.\" $NetBSD: bridge.4,v 1.5 2004/01/31 20:14:11 jdc Exp $ 2.\" 3.\" Copyright 2001 Wasabi Systems, Inc. 4.\" All rights reserved. 5.\" 6.\" Written by Jason R. Thorpe for Wasabi Systems, Inc. 7.\" 8.\" Redistribution and use in source and binary forms, with or without --- 19 unchanged lines hidden (view full) --- 28.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 29.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 30.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 31.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 32.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 33.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 34.\" POSSIBILITY OF SUCH DAMAGE. 35.\" |
| 36.\" $FreeBSD: head/share/man/man4/if_bridge.4 161261 2006-08-13 18:44:18Z brueffer $ | 36.\" $FreeBSD: head/share/man/man4/if_bridge.4 162404 2006-09-18 15:24:20Z ru $ |
| 37.\" 38.Dd August 13, 2006 39.Dt IF_BRIDGE 4 40.Os 41.Sh NAME 42.Nm if_bridge 43.Nd network bridge device 44.Sh SYNOPSIS --- 51 unchanged lines hidden (view full) --- 96.Xr syslog 3 97by enabling the 98.Va net.link.bridge.log_stp 99variable using 100.Xr sysctl 8 . 101.Pp 102All the bridged member interfaces need to be up in order to pass network traffic. 103These can be enabled using | 37.\" 38.Dd August 13, 2006 39.Dt IF_BRIDGE 4 40.Os 41.Sh NAME 42.Nm if_bridge 43.Nd network bridge device 44.Sh SYNOPSIS --- 51 unchanged lines hidden (view full) --- 96.Xr syslog 3 97by enabling the 98.Va net.link.bridge.log_stp 99variable using 100.Xr sysctl 8 . 101.Pp 102All the bridged member interfaces need to be up in order to pass network traffic. 103These can be enabled using |
| 104.Xr ifconfig 8 | 104.Xr ifconfig 8 |
| 105or | 105or |
| 106.Va ifconfig_ Ns Ao Ar interface Ac Ns Va ="up" | 106.Va ifconfig_ Ns Ao Ar interface Ac Ns Li ="up" |
| 107in 108.Xr rc.conf 5 . 109.Pp 110The MTU of the first member interface to be added is used as the bridge MTU. 111All additional members are required to have exactly the same value. 112.Pp 113The TXCSUM capability is disabled for any interface added to the bridge, and it 114is restored when the interface is removed again. --- 4 unchanged lines hidden (view full) --- 119.Xr bpf 4 120processing, and are not processed or forwarded further. 121This can be used to multiplex the input of two or more interfaces into a single 122.Xr bpf 4 123stream. 124This is useful for reconstructing the traffic for network taps 125that transmit the RX/TX signals out through two separate interfaces. 126.Sh PACKET FILTERING | 107in 108.Xr rc.conf 5 . 109.Pp 110The MTU of the first member interface to be added is used as the bridge MTU. 111All additional members are required to have exactly the same value. 112.Pp 113The TXCSUM capability is disabled for any interface added to the bridge, and it 114is restored when the interface is removed again. --- 4 unchanged lines hidden (view full) --- 119.Xr bpf 4 120processing, and are not processed or forwarded further. 121This can be used to multiplex the input of two or more interfaces into a single 122.Xr bpf 4 123stream. 124This is useful for reconstructing the traffic for network taps 125that transmit the RX/TX signals out through two separate interfaces. 126.Sh PACKET FILTERING |
| 127.Pp | |
| 128Packet filtering can be used with any firewall package that hooks in via the 129.Xr pfil 9 130framework. 131When filtering is enabled, bridged packets will pass through the filter 132inbound on the originating interface, on the bridge interface and outbound on 133the appropriate interfaces. 134Either stage can be disabled. 135The filtering behaviour can be controlled using --- 152 unchanged lines hidden --- | 127Packet filtering can be used with any firewall package that hooks in via the 128.Xr pfil 9 129framework. 130When filtering is enabled, bridged packets will pass through the filter 131inbound on the originating interface, on the bridge interface and outbound on 132the appropriate interfaces. 133Either stage can be disabled. 134The filtering behaviour can be controlled using --- 152 unchanged lines hidden --- |