One workaround is to use firewalld and add the interface to a zone where you don't allow gluster communication.<div><br></div><div>Best Regards,</div><div>Strahil Nikolov <br> <br> <blockquote style="margin: 0 0 20px 0;"> <div style="font-family:Roboto, sans-serif; color:#6D00F6;"> <div>On Mon, Apr 3, 2023 at 12:59, Gregor Burck</div><div><gregor@aeppelbroe.de> wrote:</div> </div> <div style="padding: 10px 0 0 20px; margin: 10px 0 0 0; border-left: 1px solid #6D00F6;"> <div id="yiv2719489952"><span style="width:100%;display:inline;font-family:arial, helvetica, sans-serif;font-size:10pt;">Hi,<br>
<br>
after a bit of time I play around with glusterfs again.<br>
<br>
For now I want to bind the glusterd to an specified interface/ip adress.<br>
I want to have a management net, where the service doesn't reachable and an cluster net where the service is working on.<br>
<br>
I read something about to define it in the /etc/glusterfs/glusterfsd.vol file but found no valid desciption of it.<br>
Even on </span>https://docs.gluster.org or in an man page,...<br>
<br>
<span style="width:100%;display:inline;font-family:arial, helvetica, sans-serif;font-size:10pt;">Bye<br>
<br>
Gregor</span>
<div></div>
</div>________<br><br><br><br>Community Meeting Calendar:<br><br>Schedule -<br>Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC<br>Bridge: <a href="https://meet.google.com/cpu-eiue-hvk" target="_blank">https://meet.google.com/cpu-eiue-hvk</a><br>Gluster-users mailing list<br><a ymailto="mailto:Gluster-users@gluster.org" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br><a href="https://lists.gluster.org/mailman/listinfo/gluster-users" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br> </div> </blockquote></div>