>Synopsis: relayd depends on the order of the 'forward' lines even when they should be unambiguous
System : OpenBSD 6.6
Details : OpenBSD 6.6 (GENERIC.MP) #372: Sat Oct 12 10:56:27 MDT 2019
Machine : amd64
Most options in relayd.conf are order insensitive (except for filter rules). But
when using `forward to <table>`, the order matters, even when there's only a single
possible forward for each table.
> I can't understand why though. It seems like the rules are unambiguous.
Its a feature:
forward to <table> [port number] options ...
Specify the tables of target hosts to be used; see the TABLES
section above for information about table options. If the port
option is not specified, the first port from the listen on
directive will be used. *This directive can be specified twice
the second entry will be used as the backup table if all hosts in
the main table are down.* At least one entry for the main table
I.e. its just the way the configuration laguage works to specify backup
Thanks for taking a look. relayd is a complicated but still elegant solution to some messy parts of the web and I appreciate that its author took the time to look in on this.
On February 11, 2020 6:15:54 PM EST, Sebastian Benoit <[hidden email]> wrote:
>Nick([hidden email]) on 2020.02.11 07:29:44 +0000:
>> I can't understand why though. It seems like the rules are
>Its a feature:
>I.e. its just the way the configuration laguage works to specify backup
In this case they aren't backup tables though, they are separate destinations with different meanings. Things to /app should always go to one server, everything else to another.