[MXS-1315] expand the source paramter possibilities beyond a single IP or subnetwork Created: 2017-07-10  Updated: 2018-09-04  Resolved: 2018-09-04

Status: Closed
Project: MariaDB MaxScale
Component/s: namedserverfilter
Affects Version/s: 2.1.4
Fix Version/s: 2.3.0

Type: New Feature Priority: Major
Reporter: Sylvain ARBAUDIE Assignee: Marko Rajala (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Sprint: MXS-SPRINT-64, MXS-SPRINT-65

 Description   

the source parameter in the NamedServerFilter only allows an IP like this :

source=192.168.10.1

or a wildcard pointer to a whole subnetwork like this :

source=192.168.10.%

as of 2.1.4

An interesting feature would be to provide a list of either IPs or subnetwork or even hostnames as value for this parameter like this :

source=192.168.10.%,192.168.21.3,mydckercontainer.mariadb.com

it would allow for example docker containers to be easily configured without previous knowledge of the network, or use of hosts file.



 Comments   
Comment by markus makela [ 2018-03-26 ]

Would make sense as a generic filter mechanism.

Comment by Reiner Keller [ 2018-07-11 ]

Yes, best like common host resolution used in MariaDB for core and all modules where needed.

I got e.g. with MariaDB MaxScale 2.2.11 this error while trying to connect with IPv4 address:

ERROR 1045 (28000): Access denied for user 'user'@'::ffff:172.16.30.49' (using password: YES)

Maxscale shows me this error:

  • while I use normally GRANT 'user'@'172.16.0.0/255.240.0.0';

    error  : [MySQLAuth] Unrecognized IP-bytes in host/mask-combination. Merge incomplete: 172.16.0.0/255.240.0.0
    

  • and for tests alreday simplified to 'user'@'172.16.%.%;

    warning: [MySQLAuth] Read-Only-Service-testing: login attempt for user 'user'@[::ffff:172.16.30.49]:51204, authentication failed. User not found.
    

I used for testing masking read connects these modules:

  • dbfwfilter
  • masking
  • (topfilter)
  • (mariadbmon)

EDIT: seems also related to MXS-1827

Comment by markus makela [ 2018-08-16 ]

Reiner030 I think your problem might be more about MXS-1827.

Generated at Thu Feb 08 04:05:49 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.