ECN interop failures

[larseggert]

See the red Es in the quinn row and column on https://interop.seemann.io/

[Ralith]

I'm pretty sure this is an issue with our interop tool/image rather than Quinn proper, but I've never been able to get the runner to work in my environment to begin with; some weird interaction between docker and iptables that I'm not dockery enough to understand. Help here would be very welcome.

[mxinden]

For what it is worth, here are the logs of a failed ECN testcase run:

2024-05-02 12:07:43,263 Using the client's key log file.
2024-05-02 12:07:43,263 Using the client's key log file.
2024-05-02 12:07:43,496 Check of downloaded files succeeded.
2024-05-02 12:07:43,496 Using the client's key log file.
2024-05-02 12:07:44,221 ECN.NONE 17
2024-05-02 12:07:44,221 ECN.ECT1 0
2024-05-02 12:07:44,221 ECN.ECT0 0
2024-05-02 12:07:44,221 ECN.CE 0
2024-05-02 12:07:44,468 ECN.NONE 15
2024-05-02 12:07:44,469 ECN.ECT1 0
2024-05-02 12:07:44,469 ECN.ECT0 0
2024-05-02 12:07:44,469 ECN.CE 0
2024-05-02 12:07:44,470 Client did not mark any packets ECT(0) or ECT(1)
2024-05-02 12:07:44,470 Server did not mark any packets ECT(0) or ECT(1)

https://interop.seemann.io/logs/2024-05-02T08:27/quinn_quinn/ecn/output.txt

[larseggert]

@Ralith can't help you with QNS on Linux; on the Mac it's as simple as

1. checking out the repo
2. creating a pyenv
3. installing the deps
4. and running the scripts

[Ralith]

This doesn't seem to be happening anymore; probably it was fixed when I finally got the runner working locally last year and did a bunch of clean-up.