Configuring cluster for port forwarding

22 views
Skip to first unread message

Patrick Noble

unread,
Jan 12, 2017, 4:18:16 PM1/12/17
to codership
Hi, 

I am trying to set up a Master-Master replication system between 2 remote servers, both behind separate firewalls, and I'm having some trouble getting my 2nd node connected, logs just say connection timed out.
I am confused about what addresses to use where in my galera configuration variables.

Should all the node and cluster addresses be the IPs of the port forwarding devices, or does the wsrep_node_address variable need to be the actual IP of the server running the mysql service?

Sorry if my question is off the mark, I am new to network administration as well. Is there anything else I am missing that is beyond the generic cluster configuration?

Thank you,

Patrick

Philip Stoev

unread,
Jan 13, 2017, 3:48:55 AM1/13/17
to Patrick Noble, codersh...@googlegroups.com
Hello,

The settings should be as follows:

Use public IP for:
- wsrep_cluster_address
- wsrep_node_address

Use private IP for:
- ist.recv_bind

Also, please make sure the following ports are open bidirectional and every
machine can contact every other machine on them: 3306, 4567, 4568, 4444

Philip Stoev
--
You received this message because you are subscribed to the Google Groups
"codership" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to codership-tea...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Patrick Noble

unread,
Jan 13, 2017, 12:33:26 PM1/13/17
to Philip Stoev, codersh...@googlegroups.com
Thank you for the reply! That makes things a lot more clear. 

Still not connecting, so I did a packet capture on one of my gateways for traffic coming into my first node (bootstrap node) from my second node (connecting node).
All the packets I saw were coming from ports like 59788 and 57846 on the connecting node into port 4567 on the bootstrap node, and going back again.

What made me concerned is that packets are never getting sent back to port 4567 on the connecting node.
Maybe it has something to do with running the node behind a NAT?

Thanks!

Patrick

To unsubscribe from this group and stop receiving emails from it, send an email to codership-team+unsubscribe@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages