Description Samuel Mannehed 2014-05-22 09:39:43 CEST

Found on RHEL6 server, if you choose Yes to configure firewall in tl-setup, iptables will be started if it wasn't running. This does not happen on Fedora 18 with firewalld (if firewalld isn't running you don't get the firewall part in tl-setup).


[root@dhcp-253-24 tltest]# sudo service iptables status
iptables: Firewall is not running.
[root@dhcp-253-24 tltest]# /opt/thinlinc/sbin/tl-setup

...

Configure the firewall for ThinLinc [Yes/no]?Yes

The local firewall has been configured to allow ThinLinc services to
be accessed.

...

[root@dhcp-253-24 tltest]# sudo service iptables status
Table: filter
Chain INPUT (policy ACCEPT)
num  target     prot opt source               destination         
1    ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED 
2    ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0           
3    ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           
4    ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:22 
5    ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:300 
6    ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:1010 
7    ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:9000 
8    ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:904 
9    REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited 

Chain FORWARD (policy ACCEPT)
num  target     prot opt source               destination         
1    REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited 

Chain OUTPUT (policy ACCEPT)
num  target     prot opt source               destination