December 2005
Intermediate to advanced
1066 pages
33h 38m
English
Content preview from Understanding Linux Network InternalsBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Important Data Structures
The following list explains the main data structures defined and used by the bridging code. All of them have dedicated sections with field-by-field descriptions in Chapter 17.
-
mac_addr MAC address.
-
bridge_id Bridge ID (defined in Chapter 15).
-
net_bridge_fdb_entry Entry of the forwarding database. There is one for each MAC address learned by the bridge.
-
net_bridge_port Bridge port.
-
net_bridge Information applying to a single bridge. As shown in Figure 16-6, this structure is appended to a
net_devicedata structure. As with most virtual devices, it includes private information understood only by the virtual device code—bridging, in this case.-
br_config_bpdu The key fields of an ingress configuration BPDU are copied into this data structure, and it is passed instead of the original BPDU to the routine that processes configuration BPDUs.
All data structures are defined in net/bridge/br_private.h, with the exception of br_config_bpdu, which is defined in net/bridge/br_private_stp.h. Figure 16-6 shows the relationships between some of these data structures. The
figure does not reflect any of the examples of configurations seen in the previous
section.
The age_list list is not used anymore; I included
it in the figure only for reference. See the section "net_bridge Structure" in Chapter 17.
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.