Benjamin Wiegand bf7ad0a43a use TCP RTT timeout-style calculation for max_rtt ...

this was one of the annoying limitations of the old system, that the
max_rtt had to be set manually and I couldn't figure out how to
effectively auto-detect it. This appears to work alright.

2025-12-07 20:38:34 -08:00

..

starter-scripts

manually apply ip forwarding rules

2025-12-07 13:26:00 -08:00

.gitignore

add .gitignore

2025-12-07 16:16:30 -08:00

circusd.service

revert to original unit description

2025-12-06 23:55:56 -08:00

config_default.py

use TCP RTT timeout-style calculation for max_rtt

2025-12-07 20:38:34 -08:00

config.example.py

add """configuration file""" support

2025-12-07 15:52:22 -08:00

gw_spec.py

add """configuration file""" support

2025-12-07 15:52:22 -08:00

helpers.py

initial daemon code

2025-12-06 23:30:47 -08:00

log.py

initial daemon code

2025-12-06 23:30:47 -08:00

main.py

use TCP RTT timeout-style calculation for max_rtt

2025-12-07 20:38:34 -08:00

node_config.local.py

add """configuration file""" support

2025-12-07 15:52:22 -08:00

node_config.remote.py

add """configuration file""" support

2025-12-07 15:52:22 -08:00

ping.py

initial daemon code

2025-12-06 23:30:47 -08:00

requirements.txt

initial daemon code

2025-12-06 23:30:47 -08:00

stats.py

use TCP RTT timeout-style calculation for max_rtt

2025-12-07 20:38:34 -08:00