On Mon, 21 Jul 2025 02:57:44 +0200,
j...@bitminer.ca wrote:
> 
> OK, so here is my understanding of how relayd works with relays:
> 
> - every destination needs a table, even if to the same localhost
> 
> - multiple destinations need multiple tables, one for one, even
>   if going to localhost.
> 
> - tables define targets for relay, but they also carry health-
>   checking information (definitions and status).  Table
>   lookups use health-check results.
> 
> - protocols process TLS (including multiple TLS hosts) together
>   with parameters.  "Protocols ...define settings and rules
>   for relays" says the doc.
> 
> - the relay clause allows multiple forwardings but the document
>   says "subsequent entries will be used as the backup table if
>   all hosts in the previous table are down."  Which is unclear
>   to me: is the last in the list used, or are they searched
>   sequentially?  In Kirill's example, does <fallback>
>   get traffic only if <vaultwarden> and any other tables
>   are all simultaneously down?
> 
> - reading the doc closely does result in a state of simultaneous
>   awe and mystery.  There is no fix for that.
> 

Yep, it was as I had understand it and I confirm that reading docs was quite
difficult challenge and I spend some time to figure it out.

-- 
wbr, Kirill

Reply via email to