Firewalld 0.3.13 routing problem.

[_will_]

Dear All,

I have a number of problems with different services which ultimately seem to be related to firewalld. For example, ypserv, gmetad, x2go, glusterd, and slurmd, all work when the firewalld service isn't active, but fail when it is, in spite of the requisite ports being opened. Having, investigated the issue further, it seems to be related to the fact that if firewalld is running, services which bind to localhost seem to bind to the public IP address as opposed to 127.0.0.1.

Taking x2go for example, with firewalld running, the logs contain

Info: Agent running with pid '204654'.
Session: Starting session at 'Wed Aug 5 14:57:49 2015'.
Info: Proxy running in server mode with pid '204654'.
Info: Waiting for connection from 'localhost' on port '30011'.
Warning: Refusing connection from '131.***.***.100'.
100' on port '30011',

and I'm unable to connect, but after stopping the firewalld service, they contain

Info: Agent running with pid '214487'.
Session: Starting session at 'Wed Aug 5 15:19:53 2015'.
Info: Proxy running in server mode with pid '214487'.
Info: Waiting for connection from 'localhost' on port '30011'.
Info: Accepted connection from '127.0.0.1'.
Info: Connection with remote proxy completed.

and x2go works, without issue.

The routing table looks the same in both cases. My /etc/hosts file contains the localhost line first and the public hostname/IP address line second. Apologies if this is a totally trivial problem, but any advice on how to resolve or diagnose the problem would be very highly appreciated.

Many thanks,


Will.

[aks]

Please post output from:
firewall-cmd --get-zone-of-interface=lo
firewall-cmd --get-active-zones