From: Nikolay Aleksandrov
Test that when a group in exclude mode expires it changes mode to
include and the blocked entries are deleted.
Signed-off-by: Nikolay Aleksandrov
---
.../selftests/net/forwarding/bridge_igmp.sh | 49 ++-
1 file changed, 48 insertions(+), 1 deletion(-
From: Nikolay Aleksandrov
When we have *,G ports in exclude mode and a new S,G,port is added
the kernel has to automatically create an S,G entry for each exclude
port to get proper forwarding.
Signed-off-by: Nikolay Aleksandrov
---
.../selftests/net/forwarding/bridge_igmp.sh | 31 +++
From: Nikolay Aleksandrov
The test checks for the following case:
state reportresult action
EXCLUDE (X,Y) BLOCK (A) EXCLUDE (X+(A-Y),Y) (A-X-Y)=Group Timer
Send Q(G,A-Y)
Signed-off-by: Nikolay
From: Nikolay Aleksandrov
The test checks for the following case:
state reportresult action
EXCLUDE (X,Y) TO_EX (A) EXCLUDE (A-Y,Y*A)(A-X-Y)=Group Timer
Delete (X-A)
From: Nikolay Aleksandrov
The test checks for the following case:
state reportresult action
EXCLUDE (X,Y) IS_EX (A) EXCLUDE (A-Y,Y*A)(A-X-Y)=GMI
Delete (X-A)
From: Nikolay Aleksandrov
The test checks for the following case:
state reportresult action
EXCLUDE (X,Y) ALLOW (A) EXCLUDE (X+A,Y-A) (A)=GMI
Signed-off-by: Nikolay Aleksandrov
---
.../selftests/net/forwarding/bridge_igmp.sh | 83
From: Nikolay Aleksandrov
The test checks for the following case:
state reportresult action
INCLUDE (A)IS_EX (B) EXCLUDE (A*B,B-A) (B-A)=0
Delete (A-B)
From: Nikolay Aleksandrov
The test checks for the following case:
state reportresult action
EXCLUDE (X,Y) IS_IN (A) EXCLUDE (X+A,Y-A) (A)=GMI
Signed-off-by: Nikolay Aleksandrov
---
.../selftests/net/forwarding/bridge_igmp.sh | 27 ++
From: Nikolay Aleksandrov
The test checks for the following case:
state reportresult action
INCLUDE (A)BLOCK (B) INCLUDE (A) Send Q(G,A*B)
Signed-off-by: Nikolay Aleksandrov
---
.../selftests/net/forwarding/bridge_igmp.sh | 33
From: Nikolay Aleksandrov
Add helpers which will be used in subsequent tests, they are:
- check_sg_entries: check for proper source list and S,G entry
existence
- check_sg_fwding: check for proper traffic forwarding/blocking
- check_sg_state: check for proper blocked/forwarding entry state
From: Nikolay Aleksandrov
The test checks for the following case:
state reportresult action
INCLUDE (A)IS_IN (B) INCLUDE (A+B)(B)=GMI
Signed-off-by: Nikolay Aleksandrov
---
.../selftests/net/forwarding/bridge_igmp.sh | 25 +
From: Nikolay Aleksandrov
The test checks for the following case:
state reportresult action
INCLUDE (A)TO_EX (B) EXCLUDE (A*B,B-A) (B-A)=0
Delete (A-B)
From: Nikolay Aleksandrov
To prepare the bridge_igmp.sh for IGMPv3 we need to rename the
current test to IGMPv2.
Signed-off-by: Nikolay Aleksandrov
---
tools/testing/selftests/net/forwarding/bridge_igmp.sh | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/tools/tes
From: Nikolay Aleksandrov
Hi,
This set adds tests for the bridge's new IGMPv3 support. The tests use
precooked packets which are sent via mausezahn and the resulting state
after each test is checked for proper X,Y sets, (*,G) source list, source
list entry timers, (S,G) existence and flags, packe
From: Nikolay Aleksandrov
Add support for one more argument which specifies the source address to
use. It will be later used for IGMPv3 S,G entry testing.
Signed-off-by: Nikolay Aleksandrov
---
.../testing/selftests/net/forwarding/bridge_igmp.sh | 13 +++--
1 file changed, 7 insertions
From: Nikolay Aleksandrov
First we test is_include/include mode then we build on that with allow
effectively achieving:
state reportresult action
INCLUDE (A)ALLOW (B)INCLUDE (A+B) (B)=GMI
Signed-off-by: Nikolay Aleksandrov
---
.../selftests
From: Nikolay Aleksandrov
We have to specifically check for udp protocol in addition to the mac
address because in IGMPv3 tests group-specific queries will use the same
mac address.
Signed-off-by: Nikolay Aleksandrov
---
tools/testing/selftests/net/forwarding/bridge_igmp.sh | 2 +-
1 file chan
On Tue, 2020-10-27 at 07:59 -0700, Stephen Hemminger wrote:
> On Tue, 27 Oct 2020 10:02:42 +
> Henrik Bjoernlund via Bridge wrote:
>
> > +/* Return 0 if the frame was not processed otherwise 1
> > + * note: already called with rcu_read_lock
> > + */
> > +static int br_process_frame_type(struc
On Tue, 27 Oct 2020 10:02:42 +
Henrik Bjoernlund via Bridge wrote:
> +/* Return 0 if the frame was not processed otherwise 1
> + * note: already called with rcu_read_lock
> + */
> +static int br_process_frame_type(struct net_bridge_port *p,
> + struct sk_buff *skb
This is the implementation of CFM netlink configuration
set information interface.
Add new nested netlink attributes. These attributes are used by the
user space to create/delete/configure CFM instances.
SETLINK:
IFLA_BRIDGE_CFM:
Indicate that the following attributes are CFM.
IF
This is the implementation of CFM netlink status
get information interface.
Add new nested netlink attributes. These attributes are used by the
user space to get status information.
GETLINK:
Request filter RTEXT_FILTER_CFM_STATUS:
Indicating that CFM status information must be delivered.
This is the implementation of Netlink notifications out of CFM.
Notifications are initiated whenever a state change happens in CFM.
IFLA_BRIDGE_CFM:
Points to the CFM information.
IFLA_BRIDGE_CFM_MEP_STATUS_INFO:
This indicate that the MEP instance status are following.
IFLA_BRIDGE_CFM_C
This patch extends the processing of frames in the bridge. Currently MRP
frames needs special processing and the current implementation doesn't
allow a nice way to process different frame types. Therefore try to
improve this by adding a list that contains frame types that need
special processing. T
This is the second commit of the implementation of the CFM protocol
according to 802.1Q section 12.14.
Functionality is extended with CCM frame transmission.
Interface is extended with these functions:
br_cfm_cc_rdi_set()
br_cfm_cc_ccm_tx()
br_cfm_cc_config_set()
A MEP Continuity Check feature c
This is the third commit of the implementation of the CFM protocol
according to 802.1Q section 12.14.
Functionality is extended with CCM frame reception.
The MEP instance now contains CCM based status information.
Most important is the CCM defect status indicating if correct
CCM frames are receive
This makes it possible to include or exclude the CFM
protocol according to 802.1Q section 12.14.
Signed-off-by: Henrik Bjoernlund
Reviewed-by: Horatiu Vultur
Acked-by: Nikolay Aleksandrov
---
net/bridge/Kconfig | 11 +++
net/bridge/br_device.c | 3 +++
net/bridge/br_private.h
This is the first commit of the implementation of the CFM protocol
according to 802.1Q section 12.14.
It contains MEP instance create, delete and configuration.
Connectivity Fault Management (CFM) comprises capabilities for
detecting, verifying, and isolating connectivity failures in
Virtual Brid
This EtherType is used by all CFM protocal frames transmitted
according to 802.1Q section 12.14.
Signed-off-by: Henrik Bjoernlund
Reviewed-by: Horatiu Vultur
Acked-by: Nikolay Aleksandrov
---
include/uapi/linux/if_ether.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/uapi/linux
This is the implementation of CFM netlink configuration
get information interface.
Add new nested netlink attributes. These attributes are used by the
user space to get configuration information.
GETLINK:
Request filter RTEXT_FILTER_CFM_CONFIG:
Indicating that CFM configuration informatio
Connectivity Fault Management (CFM) is defined in 802.1Q
section 12.14.
Connectivity Fault Management (CFM) comprises capabilities for
detecting, verifying, and isolating connectivity failures in Virtual
Bridged Networks. These capabilities can be used in networks
operated by multiple independent
30 matches
Mail list logo
