ddidderr
b8ae95a911
The relay now keeps a shared room registry behind the QUIC endpoint and runs an accept loop instead of only binding the socket. Each accepted connection must open its first bidirectional control stream with a hello frame; the relay joins the room registry and replies with welcome or reject. Admission clamps the hello datagram budget to Quinn's negotiated peer datagram size before choosing the effective room MTU, so room state is based on what the connection can actually carry. Accepted peers remain present until the QUIC connection closes, then the relay removes them through the existing leave cleanup path. The development self-signed certificate helper now exposes the certificate to tests so a loopback Quinn client can trust the relay and exercise the real stream codec path. Test Plan: - cargo fmt --check - cargo test --workspace - cargo clippy --workspace --all-targets -- -D warnings Refs: PLAN.md relay QUIC control-stream startup flow
softlan-vpn
Monorepo for a Layer 2 over QUIC LAN party bridge.
Workspace crates
lanparty-proto: shared frame format, MAC validation, MTU helpers.lanparty-ctrl: control-plane messages (join/hello/role/version).lanparty-obs: shared diagnostics/logging event models.lanparty-client-core: platform-agnostic client session state.lanparty-client-win: Windows TAP + route/metric handling binary.lanparty-gateway: Linux AF_PACKET gateway binary.lanparty-relay: public QUIC relay binary.
lanparty-proto
Transport-agnostic tunnel contract shared by all binaries:
- overlay datagram header encoding and decoding
- Ethernet frame header parsing
- MAC address parsing and identity validation
- QUIC datagram to TAP MTU budget helpers
lanparty-ctrl
Reliable control-plane schema shared by the QUIC stream handlers:
- endpoint hello messages with role, room, MAC, and datagram budget
- server welcome, reject, peer lifecycle, stats, and disconnect messages
- room-code, role/MAC, peer-id, and effective-MTU validation
- length-prefixed JSON control frames for reliable QUIC streams
lanparty-obs
Shared diagnostics and structured logging vocabulary:
- gateway/relay frame logs with MACs, ethertype, length, peer, and action
- tunnel counters shared by control messages and runtime diagnostics
- client connectivity/TAP diagnostics and user-facing status messages
lanparty-relay
Public relay binary and relay-owned room state:
- QUIC endpoint binding and first-stream hello/welcome admission
- room admission for clients and gateways
- one gateway per room, duplicate client MAC rejection, and room limits
- stable effective room MTU chosen before Ethernet datagrams flow
- Ethernet datagram forwarding decisions with no ingress reflection
- peer leave cleanup for room membership and MAC indexes
Build
cargo check --workspace
Relay
cargo run -p lanparty-relay -- --listen 443/udp
--listen accepts either a socket address or a UDP port shorthand such as
443/udp. The relay binds a QUIC endpoint, accepts a control-stream hello,
and replies with welcome or reject. Ethernet datagram forwarding is still
implemented as relay-owned decisions but not yet wired to live QUIC datagrams.
It currently uses a generated self-signed development certificate; production
certificate and client trust handling remain future work.