checks/integration · ranet3 · Tangled

forked from ranet3/ranet3

ranet3 checks integration

25 folders

Yifei Sun · checks/integration/k3s: run k3s with kube-proxy and flannel beside ranet3, its pods from an image in the store · 2w ago

checks/integration/docker: run docker beside an exit node

checks: ingest the checks the way packages are

internal/client: make the egress device at startup, originate each egress SID while every family the host forwards is ready, refuse a file whose iif rule sits where steered packets miss it, and report the device in status and metrics

checks/integration/k3s: run k3s with kube-proxy and flannel beside ranet3, its pods from an image in the store

checks: ingest the checks the way packages are

atelier,checks/integration: run the initiator and responder checks again with strongSwan and ranet3 naming each other by an FQDN through auth.aliases

checks/integration/k3s: run k3s with kube-proxy and flannel beside ranet3, its pods from an image in the store

checks: ingest the checks the way packages are

checks/integration,atelier: run x25519+mlkem768 against strongSwan dialing and answering, apart, falling back to x25519 and with ML-KEM-768 optional

mlkem-apart-responder

checks/integration,atelier: run x25519+mlkem768 against strongSwan dialing and answering, apart, falling back to x25519 and with ML-KEM-768 optional

checks/integration,atelier: run x25519+mlkem768 against strongSwan dialing and answering, apart, falling back to x25519 and with ML-KEM-768 optional

checks/integration,atelier: dial strongSwan with x25519+mlkem768 and then p384+mlkem1024 over links of MTU 1280 and 576, each end cutting its messages into RFC 7383 fragments

checks/integration,atelier: run x25519+mlkem768 against strongSwan dialing and answering, apart, falling back to x25519 and with ML-KEM-768 optional

mlkem-meet-responder

checks/integration,atelier: run x25519+mlkem768 against strongSwan dialing and answering, apart, falling back to x25519 and with ML-KEM-768 optional

checks/integration,atelier: run x25519+mlkem768 against strongSwan dialing and answering, apart, falling back to x25519 and with ML-KEM-768 optional

checks/integration,atelier: run x25519+mlkem768 against strongSwan dialing and answering, apart, falling back to x25519 and with ML-KEM-768 optional

treewide: write the node and the peers it dials in the config as identities

checks: ingest the checks the way packages are

atelier,checks/integration: run the initiator and responder checks again with strongSwan and ranet3 naming each other by an FQDN through auth.aliases

checks: ingest the checks the way packages are

atelier,checks/integration: meet strongSwan's proposals with ranet3's cap.crypto lists in one suite and in none, with either end dialing

suites-apart-responder

atelier,checks/integration: meet strongSwan's proposals with ranet3's cap.crypto lists in one suite and in none, with either end dialing

atelier,checks/integration: meet strongSwan's proposals with ranet3's cap.crypto lists in one suite and in none, with either end dialing

suites-meet-responder

atelier,checks/integration: meet strongSwan's proposals with ranet3's cap.crypto lists in one suite and in none, with either end dialing

checks/integration/tailscale: run tailscale with headscale beside ranet3, and an exit node