Fedora 19: can't disable the firewall

Question

I've installed a server (WSO2 ESB) in my laptop.

When I run it, going to the browser and typing the console address https://10.13.6.75:9443/carbon, it works normally, but if I try it on another machine on the network, it gives timeout.

Some observations:

• ping works
• telnet respond on ssh port (22) but not in 23, 8080, 9443, etc
• I've already executed service firewalld stop, service iptables stop, and disabled the selinux, but no results.

There's another process involved blocking the requests?

Answer 1

Fedora 19 uses the firewall firewalld.service. You can see if it's running from a terminal using this command:

$ systemctl status firewalld.service 
firewalld.service - firewalld - dynamic firewall daemon
   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)
   Active: active (running) since Sat 2014-01-11 17:02:00 EST; 4 days ago
 Main PID: 564 (firewalld)
   CGroup: name=systemd:/system/firewalld.service
           └─564 /usr/bin/python /usr/sbin/firewalld --nofork --nopid

Jan 11 17:02:00 greeneggs.bubba.net systemd[1]: Started firewalld - dynamic firewall d...n.

You can disable it, temporarily like this:

$ sudo systemctl stop firewalld.service

Now it's off.

$ systemctl status firewalld.service 
firewalld.service - firewalld - dynamic firewall daemon
   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)
   Active: inactive (dead) since Thu 2014-01-16 10:20:42 EST; 11s ago
 Main PID: 564 (code=exited, status=0/SUCCESS)
   CGroup: name=systemd:/system/firewalld.service

Jan 11 17:02:00 greeneggs.bubba.net systemd[1]: Started firewalld - dynamic firewall d...n.
Jan 16 10:20:39 greeneggs.bubba.net systemd[1]: Stopping firewalld - dynamic firewall .....
Jan 16 10:20:42 greeneggs.bubba.net systemd[1]: Stopped firewalld - dynamic firewall d...n.

To restart it:

$ sudo systemctl start firewalld.service 

If you're new to Fedora, or just new to 19, I highly suggest reading the Fedora Project's documentation on firewalld.

• https://fedoraproject.org/wiki/FirewallD

What ports are open?

You can use the command line tool nmap to see what ports are accepting connections on your system.

$ sudo nmap -sS -P0  192.168.1.161/32

Starting Nmap 6.40 ( http://nmap.org ) at 2014-01-16 11:06 EST
Nmap scan report for 192.168.1.161
Host is up (0.000019s latency).
Not shown: 998 closed ports
PORT    STATE SERVICE
22/tcp  open  ssh
111/tcp open  rpcbind

Nmap done: 1 IP address (1 host up) scanned in 0.11 seconds

Be sure to substitute your system's IP address in the above command.

netstat

Alternatively you can use the command netstat to see what ports are in use and which PIDs and IP's they're bound on.

$ sudo netstat -anpt | grep :22
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      894/sshd            
tcp        0      0 192.168.1.161:52732     67.253.170.83:22        ESTABLISHED 5023/ssh            
tcp6       0      0 :::22                   :::*                    LISTEN      894/sshd            

NOTE: This lists the IP addresses that have sshd bound to port 22.

Binding to ports on specific interfaces

Many people get confused by this but each interface in IPv4 has it's own set of ports. You need ot make sure that when you start a service that you take care to tell the app that you want it to bind to IP address's 127.0.0.1's port XYZ vs. the IP address for you NIC card's port XYZ.

You application appears to provide this type of feature. It's discussed in this documentation.

• http://docs.wso2.org/display/ESB460/Setting+Up+Host+Names+and+Ports

There's an XML file according to the docs where you can change your IP to bind to.

<parameter name="bind-address" locked="false">hostname or IP address</parameter>