hcq/MaxScale
hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge branch '2.3' into 2.4

Browse Source
This commit is contained in:
Markus Mäkelä 2020-10-06 10:55:33 +03:00
commit e15b276273
No known key found for this signature in database
GPG Key ID: 5CE746D557ACC499
1 changed files with 13 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
Documentation/Filters/Database-Firewall-Filter.md
View File

@ -396,7 +396,19 @@ The second component is a list of user names and network addresses in the format
*`user`*`@`*`0.0.0.0`*. The first part is the user name and the second part is
the network address. You can use the `%` character as the wildcard to enable
user name matching from any address or network matching for all users. After the
list of users and networks the keyword match is expected.
list of users and networks the keyword match is expected. This means that the
following user definitions are supported:
* `user@host`
* `user@%`
* `%@host`
Partial wildcards, e.g. `user@192.%` are not supported.
As MaxScale listens to the IPv6 all address by default, IPv4 addresses will be
mapped into the IPv6 space. This means that the IPv4 address `192.168.0.1` will
show up in MaxScale as `::ffff:192.168.0.1`. Take this into account when
defining the `users` directives.
After this either the keyword `any`, `all` or `strict_all` is expected. This
defined how the rules are matched. If `any` is used when the first rule is