You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a TP-Link Archer C7 v5 (ath79/generic) running OpenWrt 19.07.2 r10947-65030d81f3 and periodically one of my hosts sends out a long-running flood (10/sec) of MPCP Pause frames. The AR8337 switch is configured to honor these frames on port 0 (CPU), and other ports, so stops switching frames essentially forever.
There is no way exposed to user to disable flow control.
Flow control should be turned off unless explicitly requested by the user (e.g., they are in a Datacenter/Enterprise environment and/or doing Fibre Channel over Ethernet). This is exactly the opposite of how it currently is with the added benefit that the user cannot change the behavior.
You can use this to bring down your network indefinitely. Additionally, since the AR8337 switch consumes these frames you will not be able to see them from the OpenWRT host.
The text was updated successfully, but these errors were encountered:
rkeene:
I have a TP-Link Archer C7 v5 (ath79/generic) running OpenWrt 19.07.2 r10947-65030d81f3 and periodically one of my hosts sends out a long-running flood (10/sec) of MPCP Pause frames. The AR8337 switch is configured to honor these frames on port 0 (CPU), and other ports, so stops switching frames essentially forever.
There is no way exposed to user to disable flow control.
Flow control should be turned off unless explicitly requested by the user (e.g., they are in a Datacenter/Enterprise environment and/or doing Fibre Channel over Ethernet). This is exactly the opposite of how it currently is with the added benefit that the user cannot change the behavior.
Here's a tool that will helpfully generate MPCP Pause frames:
https://github.com/nwholloway/mpcp
You can use this to bring down your network indefinitely. Additionally, since the AR8337 switch consumes these frames you will not be able to see them from the OpenWRT host.
The text was updated successfully, but these errors were encountered: