]> git.proxmox.com Git - mirror_iproute2.git/blame - man/man8/bridge.8
bridge: Update bridge man pages to include vlan command
[mirror_iproute2.git] / man / man8 / bridge.8
CommitLineData
d04bc300
SH
1.TH BRIDGE 8 "1 August 2012" "iproute2" "Linux"
2.SH NAME
3bridge \- show / manipulate bridge addresses and devices
4.SH SYNOPSIS
5
6.ad l
7.in +8
8.ti -8
9.B bridge
10.RI "[ " OPTIONS " ] " OBJECT " { " COMMAND " | "
11.BR help " }"
12.sp
13
14.ti -8
15.IR OBJECT " := { "
ab938710 16.BR fdb " | " vlan " | " monitor " }"
d04bc300
SH
17.sp
18
19.ti -8
20.IR OPTIONS " := { "
21\fB\-V\fR[\fIersion\fR] |
22\fB\-s\fR[\fItatistics\fR]
23
24.ti -8
d611682a 25.BR "bridge fdb" " { " add " | " del " } "
d04bc300
SH
26.I LLADDR
27.B dev
28.IR DEV " { "
d611682a
JF
29.BR local " | " temp " } { "
30.BR self " } { " embedded " } "
d04bc300
SH
31
32.ti -8
33.BR "bridge fdb" " [ " show " ] [ "
34.B dev
35.IR DEV " ]"
36
ab938710
VY
37.ti -8
38.BR "bridge vlan" " { " add " | " del " } "
39.B dev
40.IR DEV
41.B vid
42.IR VID " [ "
43.BR pvid " ] [ " untagged " ] [ "
44.BR self " ] [ " master " ] "
45
46.ti -8
47.BR "bridge vlan" " [ " show " ] [ "
48.B dev
49.IR DEV " ]"
50
d04bc300
SH
51.ti -8
52.BR "bridge monitor" " [ " all " | " neigh " | " link " ]"
53
54.SH OPTIONS
55
56.TP
57.BR "\-V" , " -Version"
58print the version of the
59.B bridge
60utility and exit.
61
62.TP
63.BR "\-s" , " \-stats", " \-statistics"
49572501
KR
64output more information. If this option
65is given multiple times, the amount of information increases.
d04bc300
SH
66As a rule, the information is statistics or some time values.
67
68
69.SH BRIDGE - COMMAND SYNTAX
70
71.SS
72.I OBJECT
73
74.TP
75.B fdb
76- Forwarding Database entry.
77
ab938710
VY
78.TP
79.B vlan
80- VLAN filter list.
81
d04bc300
SH
82.SS
83.I COMMAND
84
85Specifies the action to perform on the object.
86The set of possible actions depends on the object type.
87As a rule, it is possible to
88.BR "add" , " delete"
89and
90.B show
91(or
92.B list
93) objects, but some objects do not allow all of these operations
94or have some additional commands. The
95.B help
96command is available for all objects. It prints
97out a list of available commands and argument syntax conventions.
98.sp
99If no command is given, some default command is assumed.
100Usually it is
101.B list
102or, if the objects of this class cannot be listed,
103.BR "help" .
104
105.SH bridge fdb - forwarding database management
106
107.B fdb
108objects contain known Ethernet addresses on a link.
109
110.P
111The corresponding commands display fdb entries, add new entries,
112and delete old ones.
113
d611682a 114.SS bridge fdb add - add a new fdb entry
d04bc300 115
d611682a 116This command creates a new fdb entry.
d04bc300
SH
117
118.TP
119.BI "ADDRESS"
120the Ethernet MAC address.
121
122.TP
123.BI dev " NAME"
124the interface to which this address is associated.
125
126.TP
127.in +8
128.B local
129- the address is associated with a local interface on the system
130and is never forwarded.
131.sp
132
133.B temp
134- the address is a dynamic entry, and will be removed if not used.
135.sp
136
d611682a
JF
137.B self
138- the address is associated with a software fdb (default)
139.sp
140
141.B embedded
142- the address is associated with an offloaded fdb
143.sp
144
d04bc300
SH
145.in -8
146
147.SS bridge fdb delete - delete a forwarding database entry
148This command removes an existing fdb entry.
149
150.PP
151The arguments are the same as with
152.BR "bridge fdb add" ,
153
154.SS bridge fdb show - list forwarding entries.
155
49572501 156This command displays the current forwarding table.
d04bc300
SH
157
158.PP
159With the
160.B -statistics
161option, the command becomes verbose. It prints out the last updated
162and last used time for each entry.
163
ab938710
VY
164.SH bridge vlan - VLAN filter list
165
166.B vlan
167objects contain known VLAN IDs for a link.
168
169.P
170The corresponding commands display vlan filter entries, add new entries,
171and delete old ones.
172
173.SS bridge vlan add - add a new vlan filter entry
174
175This command creates a new vlan filter entry.
176
177.TP
178.BI dev " NAME"
179the interface with which this vlan is associated.
180
181.TP
182.BI vid " VID"
183the VLAN ID that identifies the vlan.
184
185.TP
186.BI pvid
187the vlan specified is to be considered a PVID at ingress.
188Any untagged frames will be assigned to this VLAN.
189
190.TP
191.BI untagged
192the vlan specified is to be treated as untagged on egress.
193
194.TP
195.BI self
196the vlan is configured on the specified physical device. Required if the
197device is the bridge device.
198
199.TP
200.BI master
201the vlan is configured on the sofware bridge (default).
202
203.SS bridge vlan delete - delete a forwarding database entry
204This command removes an existing fdb entry.
205
206.PP
207The arguments are the same as with
208.BR "bridge vlan add".
209The
210.BR "pvid " and " untagged"
211flags are ignored.
212
213.SS bridge vlan show - list vlan configuration.
214
215This command displays the current VLAN filter table.
216
d04bc300
SH
217.SH bridge monitor - state monitoring
218
219The
220.B bridge
221utility can monitor the state of devices and addresses
222continuously. This option has a slightly different format.
223Namely, the
224.B monitor
225command is the first in the command line and then the object list follows:
226
227.BR "bridge monitor" " [ " all " |"
49572501 228.IR OBJECT-LIST " ]"
d04bc300
SH
229
230.I OBJECT-LIST
231is the list of object types that we want to monitor.
232It may contain
233.BR link ", and " fdb "."
234If no
235.B file
236argument is given,
237.B bridge
238opens RTNETLINK, listens on it and dumps state changes in the format
239described in previous sections.
240
241.P
242If a file name is given, it does not listen on RTNETLINK,
243but opens the file containing RTNETLINK messages saved in binary format
244and dumps them. Such a history file can be generated with the
245
246
247.SH NOTES
248This command uses facilities added in Linux 3.0.
249
250Although the forwarding table is maintained on a per-bridge device basis
251the bridge device is not part of the syntax. This is a limitation of the
252underlying netlink neighbour message protocol. When displaying the
253forwarding table, entries for all bridges are displayed.
254Add/delete/modify commands determine the underlying bridge device
255based on the bridge to which the coresponding ethernet device is attached.
256
257
258.SH SEE ALSO
259.BR ip (8)
49572501 260.SH BUGS
d04bc300
SH
261.RB "Please direct bugreports and patches to: " <netdev@vger.kernel.org>
262
263.SH AUTHOR
264Original Manpage by Stephen Hemminger