[MDEV-7676] Update site information on IPv6 support / status Created: 2015-03-06  Updated: 2016-02-17  Resolved: 2016-02-04

Status: Closed
Project: MariaDB Server
Component/s: Documentation
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Bastian Assignee: Ian Gilfillan
Resolution: Fixed Votes: 0
Labels: ipv6

Issue Links:
Relates
relates to MDEV-274 The data type for IPv6/IPv4 addresses... Closed
relates to MDEV-4051 INET6_ATON() and INET6_NTOA() Closed
relates to MDEV-4379 expand MariaDB dual-stack support Closed
relates to MDEV-8034 wsrep_node_address can't be ipv6 Closed

 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.

 Comments   
Comment by Bastian [ 2015-08-17 ]

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

Comment by Sergei Golubchik [ 2015-08-17 ]

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?

Comment by Bastian [ 2015-08-17 ]

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

Comment by Sergei Golubchik [ 2015-08-17 ]

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.

Comment by Ian Gilfillan [ 2015-08-18 ]

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

Comment by Wido den Hollander [ 2016-02-17 ]

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.

Comment by Bastian [ 2016-02-17 ]

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 ::

Generated at Thu Feb 08 07:21:25 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.