Displaying 3 results from an estimated 3 matches for "br_state_listening".
2007 Apr 18
1
[Bridge] Bridge port states
Hi all,
Can anyone explain me why we need all this per port state information. A
bridge port seems to be either in BR_STATE_LISTENING, BR_STATE_LEARNING
or BR_STATE_FORWARDING. I don't get it, thought the bridge is learning
from MAC addresses of the received packets, therefore while listening.
Why a bridge port distinquishes these states?
Thanx,
Patrick
2007 Apr 18
0
[Bridge] [PATCH 2.6] Fix message age in bridge STP config packets
...vate_stp.h"
+/* since time values in bpdu are in jiffies and then scaled (1/256)
+ * before sending, make sure that is at least one.
+ */
+#define MESSAGE_AGE_INCR ((HZ < 256) ? 1 : (HZ/256))
+
static const char *br_port_state_names[] = {
[BR_STATE_DISABLED] = "disabled",
[BR_STATE_LISTENING] = "listening",
@@ -157,24 +162,25 @@
bpdu.root_path_cost = br->root_path_cost;
bpdu.bridge_id = br->bridge_id;
bpdu.port_id = p->port_id;
- bpdu.message_age = 0;
- if (!br_is_root_bridge(br)) {
+ if (br_is_root_bridge(br))
+ bpdu.message_age = 0;
+ else {
struct net_br...
2007 Apr 18
5
[Bridge] RFC: [PATCH] bridge vlan integration
...-44,6 +44,10 @@
#define BRCTL_SET_PORT_PRIORITY 16
#define BRCTL_SET_PATH_COST 17
#define BRCTL_GET_FDB_ENTRIES 18
+#define BRCTL_SET_PORT_UNTAGGED_VLAN 19
+#define BRCTL_ADD_PORT_VLAN 20
+#define BRCTL_DEL_PORT_VLAN 21
+#define BRCTL_GET_PORT_VLAN_INFO 22
#define BR_STATE_DISABLED 0
#define BR_STATE_LISTENING 1
@@ -91,6 +95,12 @@ struct __port_info
__u32 hold_timer_value;
};
+struct __vlan_info
+{
+ __u32 untagged;
+ __u8 filter[4096/8];
+};
+
struct __fdb_entry
{
__u8 mac_addr[6];
Index: wireless-dev/include/linux/skbuff.h
===================================================================
---...