James Carlson wrote: > ... > dladm show-bridge [-p] [-s [-i <interval>]] [<bridge-name>] > > This subcommand shows the running status of bridges. When given > a bridge name, it shows the status of that one bridge. If no > bridge name is given, then it shows summary status of all > bridges on the system. > > Note the lack of a "-R" option here. It is not possible to list > bridge configuration information in an alternate root, in > keeping with the rest of the dladm user interface. The reason > for this restriction is to allow the data to be represented in > SMF, where "writing" to an alternate root is supported by way of > copying appropriate commands to $ROOT/var/svc/profile/upgrade, > but "reading" is not feasible because the repository on the > alternate root may be incompatible with the running system.
If there is no separate command, how do we observe the state of the bridging tables in use internally, as we might routing information with "netstat -r"? > ... > 2. Packet Observability > ... > The observability node is intended for use with snoop and > wireshark. It behaves as a standard Ethernet interface, but does > not permit the transmission of packets. All transmitted packets > are silently dropped. Was there any consideration given to there being a kstat counter to record this drop events? Some other questions.... What is the rights profile for bridging? Can I bridge interfaces with different MTUs? If so, what happens to the larger packets? Is the assignment of a NIC to a bridge mutually exclusive with other use, say with plumbing an IP interface on it? Are there any interaction issues with bridging and the default setting of the eeprom setting "local-mac-address?"? (OOB setting is "false", potentially giving all NICs the same MAC address.) Darren
