tree 220c5dc4fe4a828aa0764d6b7cb623e945f3bb34
parent 0580a14c23b7f7005abd2c18587f108ed6f1e93e
author ericorth <ericorth@google.com> 1784751861 -0700
committer Copybara-Service <copybara-worker@google.com> 1784751898 -0700

Bonnet Tun Exchanger Refactor: Divorce exchanger from QbonePacketWriter

The Tun exchanger code and the server-side packet-to-network logic shared an interface in an old attempt to share the same to-network logic in both client and server.  But there was so much different logic, that it didn't really do much other than very slightly simplify the one call to pass error packets backwards on being too big for the tunnel.

Needlessley restrains my ability to modify the exchanger and interface as needed for async Tun refactors, so cleaner to remove the interface. Server session keeps using its writer implementation. Client session now deals directly with the Tun exchanger.

This also fixes the subtle issue that overriding the "quic_QbonePacketWriter" test value previously could not differentiate which direction was being overridden and could insert the same mock on both ends in an integration test. Now, that test value only affects server-side network writes.

PiperOrigin-RevId: 952297179