Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-7676

Update site information on IPv6 support / status

Details

    Description

      I would to see an update on IPv6 support / status. The page you land on when searching for it is from 2010 https://mariadb.com/kb/en/mariadb/does-mariadb-support-ipv6/

      With mariadb galera 10 I can get the mysql port 3306 to listen on an IPv6 socket but not wsrep 4567. This is to bad as I was trying to get an IP6 only cluster running as the entire environment is IPv6 only.

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. MDEV-274 The data type for IPv6/IPv4 addresses in MariaDB

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-4051 INET6_ATON() and INET6_NTOA()

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-4379 expand MariaDB dual-stack support

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Task - A task that needs to be done. MDEV-8034 wsrep_node_address can't be ipv6

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            Bastian Bastian added a comment -

            I saw a message on twitter that this would/could be resolved in version 10.1

            Can someone confirm and maybe close this request?

            https://twitter.com/yogurtboy/status/632243434787487744

            Bastian Bastian added a comment - I saw a message on twitter that this would/could be resolved in version 10.1 Can someone confirm and maybe close this request? https://twitter.com/yogurtboy/status/632243434787487744
            serg Sergei Golubchik added a comment -

            What exactly do you mean under "ipv6 support" ?

            There is MDEV-4051 (inet6_aton, inet6_ntoa)— it was implemented in 10.0.12
            There is MDEV-4379 (listening on ipv4 and ipv6 addresses) — it was implemented in 10.0.13
            There is MDEV-274 (IPv6 column type) — it is not implemented yet, work in progress.
            And may be you meant something else entirely?

            serg Sergei Golubchik added a comment - What exactly do you mean under "ipv6 support" ? There is MDEV-4051 (inet6_aton, inet6_ntoa)— it was implemented in 10.0.12 There is MDEV-4379 (listening on ipv4 and ipv6 addresses) — it was implemented in 10.0.13 There is MDEV-274 (IPv6 column type) — it is not implemented yet, work in progress. And may be you meant something else entirely?
            Bastian Bastian added a comment -

            WSREP in galera cluster does not listen on IPv6 socket. Thus I have an IPv6 only environment with some mariadb servers that have an IPv4 address for replication.

            tcp 0 0 0.0.0.0:4567 0.0.0.0:* LISTEN 4555/mysqld
            tcp6 0 0 :::3306 :::* LISTEN 4555/mysqld

            Bastian Bastian added a comment - WSREP in galera cluster does not listen on IPv6 socket. Thus I have an IPv6 only environment with some mariadb servers that have an IPv4 address for replication. tcp 0 0 0.0.0.0:4567 0.0.0.0:* LISTEN 4555/mysqld tcp6 0 0 :::3306 :::* LISTEN 4555/mysqld
            serg Sergei Golubchik added a comment -

            Thanks! (I knew I've missed something)
            And thanks for pointing out that it's MDEV-8034. I've now updated it to make sure that this bug will be fixed in 10.1.

            serg Sergei Golubchik added a comment - Thanks! (I knew I've missed something) And thanks for pointing out that it's MDEV-8034 . I've now updated it to make sure that this bug will be fixed in 10.1.
            greenman Ian Gilfillan added a comment -

            I have updated the answer on the 2010 question to reflect the current status. There's also MDEV-6536 as a related issue.

            greenman Ian Gilfillan added a comment - I have updated the answer on the 2010 question to reflect the current status. There's also MDEV-6536 as a related issue.
            widodh Wido den Hollander added a comment -

            This has been resolved and closed, but in MariaDB 10.1 it doesn't work for me.

            root@ns011:~# netstat -nap|grep LISTEN|grep mysqld
            tcp 0 0 0.0.0.0:4567 0.0.0.0:* LISTEN 17871/mysqld
            tcp6 0 0 :::3306 :::* LISTEN 17871/mysqld
            unix 2 [ ACC ] STREAM LISTENING 1146141 17871/mysqld /var/run/mysqld/mysqld.sock
            root@ns011:~#

            In my case 'bind-address' has been set to '::' and this makes MariaDB listen on IPv4 and IPv6 for SQL connections, but WSREP still listens on IPv4-only.

            The documentation doesn't show or tell how this should be done properly.

            In my case I want to run MariaDB Galera on a IPv6-only network.

            widodh Wido den Hollander added a comment - This has been resolved and closed, but in MariaDB 10.1 it doesn't work for me. root@ns011:~# netstat -nap|grep LISTEN|grep mysqld tcp 0 0 0.0.0.0:4567 0.0.0.0:* LISTEN 17871/mysqld tcp6 0 0 :::3306 :::* LISTEN 17871/mysqld unix 2 [ ACC ] STREAM LISTENING 1146141 17871/mysqld /var/run/mysqld/mysqld.sock root@ns011:~# In my case 'bind-address' has been set to '::' and this makes MariaDB listen on IPv4 and IPv6 for SQL connections, but WSREP still listens on IPv4-only. The documentation doesn't show or tell how this should be done properly. In my case I want to run MariaDB Galera on a IPv6-only network.
            Bastian Bastian added a comment - - edited

            I don't use bind-address, it's commented out. But 3306 is listening on IPv4 and IPv6 sockets. However for the WSREP address I have not have a chance to test it yet.

            Current config:
            wsrep_cluster_address="gcomm://10.0.0.21,10.0.0.31"
            wsrep_cluster_name='galera_cluster'
            wsrep_node_address='10.0.0.11'
            wsrep_node_name='db11'

            Maybe that the WSREP should also be not specified or specified with the ::

            Bastian Bastian added a comment - - edited I don't use bind-address, it's commented out. But 3306 is listening on IPv4 and IPv6 sockets. However for the WSREP address I have not have a chance to test it yet. Current config: wsrep_cluster_address="gcomm://10.0.0.21,10.0.0.31" wsrep_cluster_name='galera_cluster' wsrep_node_address='10.0.0.11' wsrep_node_name='db11' Maybe that the WSREP should also be not specified or specified with the ::

            People

              greenman Ian Gilfillan
              Bastian Bastian
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.