Add the ability for users to specify a custom
routing table where routes should be installed in.
As of now routes are always installed in the main
routing table of the operating system, however,
with the new --route-table option it is possibile
to specify the ID of the default routing table
to be
On Tue, Apr 18, 2023 at 10:14:46AM -0400, selva.n...@gmail.com wrote:
> From: Selva Nair
>
> - We assume that all text passed to the management interface
> and written to log file are in Unicode (UTF-8). This is broken by
> the use of the ANSI version of FormatMessage() for Windows error
>
From: Selva Nair
- We assume that all text passed to the management interface
and written to log file are in Unicode (UTF-8). This is broken by
the use of the ANSI version of FormatMessage() for Windows error
messages. Fix by using FormatMessageW() and converting the UTF-16
result to
On Tue, Apr 18, 2023 at 09:40:11AM -0400, selva.n...@gmail.com wrote:
> From: Selva Nair
>
> - We assume that all text passed to the management interface
> and written to log file are in Unicode (UTF-8). This is broken by
> the use of the ANSI version of FormatMessage() for Windows error
>
It is generated from t_client.sh.in by configure,
so no need to ship it. Due to the dependency on
the configuration it also might break reproducibility
of the dist tarball.
Signed-off-by: Frank Lichtenheld
---
tests/Makefile.am | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff
From: Selva Nair
- We assume that all text passed to the management interface
and written to log file are in Unicode (UTF-8). This is broken by
the use of the ANSI version of FormatMessage() for Windows error
messages. Fix by using FormatMessageW() and converting the UTF-16
result to
