----- Original Message ----- From: Ed Greshko Sent: 05/02/14 12:23 AM To: Community support for Fedora users Subject: Re: iptable
On 05/02/14 03:51, Patrick Dupre wrote:
Hello,
My firewall-config does not work properly (I am ready posted about). How can I manage the iptable manually? There is no /etc/sysconfig/iptables
Right now I need to turn on the port 5900 open for vnc
Are you running into the same problem a user had back in February? The subject line at that time, if I remember correctly, was along the lines of "vncviewer".
FWIW, vnc works fine here upon opening the necessary ports via firewall-config.
Oh I now, but on this machine the 5900-5903 port are filtering and I cannot open them. using firewall-config, I get:
ERROR:dbus.proxies:Introspect error on :1.80:/org/fedoraproject/Config/Services/ServiceHerders/XinetdServiceHerder: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
How can I fix it?
Thank.
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France ===========================================================================
On 05/02/14 06:52, Patrick Dupre wrote:
Oh I now, but on this machine the 5900-5903 port are filtering and I cannot open them. using firewall-config, I get:
ERROR:dbus.proxies:Introspect error on :1.80:/org/fedoraproject/Config/Services/ServiceHerders/XinetdServiceHerder: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
How can I fix it?
systemctl status dbus.service systemctl status dbus.socket