janjust wroteOpenVPN does not generate MAC Pause packets by itself, at least I have never seen it anywhere in the source code.
If we can rule out OpenVPN and the bridge (due to STP being disabled) for generating the packets, I'm quite confused as there don't seem to be any other components involved. (See below)
janjust wroteThe fact that you see these packets after OpenVPN starts is more likely related to the fact that OpenVPN forwards (and broadcasts) all traffic from the remote end - if there are STP packets generated there by a switch then OpenVPN will happily forward them. This happens regardless of whether STP is enabled on the bridge or not.
The daemon was running but idle. I.e. there was no active OpenVPN connection. So it can't have forwarded them from anywhere.
When I described the setup in the previous post, I probably should have explicitly stated that the WAN-side of the router is not connected to anything in the test setup.
The problem occured with the router being integrated in the network with DSL connected on one side and my network with some switches on the other side. When I ran into the problem, I unplugged one device after the other until I ended up with just the PC running wireshark and some script to generate packets and the router, still being able to reproduce the problem.
Next I replaced the router in the test network with an identical model and rebuilt the production network with OpenVPN disabled. The test network still showed the problem and the production network is running stable since then. (But without OpenVPN)
Could the problem be that there was no active OpenVPN connection? Might the packets get generated (by the daemon or the bridge or whoever) since the daemon sees packets on the internal network, realizes that it can't send them anywhere and requests a slowdown (maybe after some buffer fills up)?
Regards,
Mike
