Nick([email protected]) on 2020.02.11 07:29:44 +0000:
> >Synopsis: relayd depends on the order of the 'forward' lines even when
> >they should be unambiguous
> >Category: system
> >Environment:
> System : OpenBSD 6.6
> Details : OpenBSD 6.6 (GENERIC.MP) #372: Sat Oct 12 10:56:27 MDT
> 2019
>
> [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>
> Architecture: OpenBSD.amd64
> Machine : amd64
>
> >Description:
>
> 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.
>
> (
> originally reported at
> *
> https://www.reddit.com/r/openbsd/comments/eh6ll8/relayd_as_a_reverse_proxy_help_due_to_uncertainty/
> *
> https://www.reddit.com/r/openbsd/comments/3qb2c4/some_observations_about_relayd/
> )
>
> >How-To-Repeat:
...
> 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
is mandatory.
I.e. its just the way the configuration laguage works to specify backup
destinations.
