ddidderr
b3d1a9c046
Add socket-free relay forwarding logic for Ethernet datagrams. The future QUIC relay loop can now ask the room registry which peer IDs should receive a frame instead of embedding switching policy in network IO code. Forwarding validates that the ingress peer belongs to the room, drops malformed Ethernet frames, rejects client frames whose source MAC does not match the MAC announced during admission, never reflects frames back to ingress, routes known client unicasts directly, and floods broadcast/multicast or unknown unicast frames to the other room peers. The decision reports shared observability action and drop-reason values so the networking layer can log consistently. This still does not send bytes over QUIC; it only defines the room-local switch decision that the datagram loop will use. Test Plan: - cargo fmt --check - cargo test --workspace - cargo clippy --workspace --all-targets -- -D warnings Refs: PLAN.md Switching model
1.7 KiB
1.7 KiB
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:
- 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
Build
cargo check --workspace