similar to: /etc/sysconfig/iptables on a stock CentOS 5 install

Hello CentOS, I'm curious... there seems to be a couple of default firewall rules that I'm not familiar with in the CentOS 4.0 # Firewall configuration written by system-config-securitylevel # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :RH-Firewall-1-INPUT - [0:0] -A INPUT -j RH-Firewall-1-INPUT -A FORWARD

Below is my firewall rules for iptables. everything is working fine except for NFS I cannot mount my drive. If I turn off iptables I can mount. Looking at this : http://www.centos.org/docs/5/html/Deployment_Guide-en-US/ch-nfs.html Important In order for NFS to work with a default installation of Red Hat Enterprise Linux with a firewall enabled, IPTables with the default TCP port 2049

My firewall config is below... I am trying to figure out why another machine has access to port 5038 on my machine based on these firewall rules. I thought the reject at the bottom would take care of all other ports? It does not. I have restarted with "server iptables restart" and same thing. I can connect from another machine to my machine on port 5038. How do I prevent this?

Dear CentOS community, I have install centos via CD, DVD and Directly off the net via http and FTP. Now I want to do a NFS install from a local server and a client. Both, client and server are in the same vlan 10.14.10.0/255.255.255.0. The server has a static 10.14.10.15 address and the client gets its own address via DHCP. I download the DVD image from one of the mirrors and placed it under

Hi, I have an existing iptables as follows:- # Firewall configuration written by system-config-securitylevel # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :RH-Firewall-1-INPUT - [0:0] -A INPUT -j RH-Firewall-1-INPUT -A FORWARD -j RH-Firewall-1-INPUT -A RH-Firewall-1-INPUT -i lo -j ACCEPT -A RH-Firewall-1-INPUT -p

Hello everyone, I am setting up a new system for use as a testing/demo/trial-and-error system. I have installed CentOS 4.4 on it. There is not an X-environment, so I will need to fix this from the command line (via ssh access). I am trying to do an nfs export from this box to another on my internal home network. I have figured out that it is a firewall issue on the CentOS box (I turn off the

Hello, I have just installed XEN2.0 on a fresh installation of Fedora Core 3 and iptables does not work properly ===================================================================== [root@aquarius ~]# /etc/init.d/iptables start Applying iptables firewall rules: iptables-restore v1.2.11: iptables-restore: unable to initialize table ''filter'' Error occurred at line: 3 Try

Hello again, unfortunately the following /etc/sysconfig/iptables file does not work: *nat :INPUT ACCEPT :OUTPUT ACCEPT :PREROUTING ACCEPT :POSTROUTING ACCEPT #-A PREROUTING -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 8080 -A PREROUTING -p tcp -m tcp -d 144.76.184.154/32 --dport 80 -j REDIRECT --to-ports 8080 COMMIT *filter :INPUT DROP :OUTPUT ACCEPT :FORWARD DROP -A INPUT -m state --state

Hello Gordon and others On Tue, Jun 21, 2016 at 4:13 PM, Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 06/21/2016 02:30 AM, Alexander Farber wrote: > >> -A PREROUTING -p tcp -m tcp -d 144.76.184.154/32 --dport 80 -j REDIRECT >> --to-ports 8080 >> > > > I think you have the ports backward, here. > here the problem description again: I have

Hi all, I am trying to get fail2ban going on my server and its log message reports the following error 2009-02-16 17:42:05,339 ERROR: 'iptables -L INPUT | grep -q fail2ban-SSH' returned 256 2009-02-16 17:42:05,354 ERROR: 'iptables -D INPUT -p tcp --dport ssh -j fail2ban-SSH Is this because of the way the RedHat tool sets up the firewall? Thanks for any responses. -- "The

Good evening, on a CentOS 7 LAMP (not gateway) dedicated server I am using iptables-services with the following /etc/sysconfig/iptables: *filter :INPUT DROP [0:0] :FORWARD DROP [0:0] :OUTPUT ACCEPT [294:35064] -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type any -j ACCEPT -A INPUT -p tcp -m state --state NEW -m tcp -m

On Tue, 2016-06-21 at 15:46 +0100, Always Learning wrote: > On Tue, 2016-06-21 at 16:24 +0200, Alexander Farber wrote: > > > *nat > > :INPUT ACCEPT > > :OUTPUT ACCEPT > > :PREROUTING ACCEPT > > :POSTROUTING ACCEPT > > -A PREROUTING -p tcp --dst 144.76.184.154 --dport 8080 -j REDIRECT > > --to-port 80 > >

This is a standard RedHat / CentOS firewall configuration, where I told it, through the standard RH setup GUI, that I want ssh and snmp allowed through. Chain INPUT (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain FORWARD (policy ACCEPT) target prot opt source

I have a computer that I needed to put 2.6.21 on. Everything is working fine after recompile except when iptables is starting up it errors with iptables-restore: line 23 failed. This is the normal centos 5 iptables. nothing special. What might I be missing in the new kernel that I get this error? Thanks, The file is below. Jerry --------------------------------------- # Firewall configuration

In following up on the rsh "problem" I was having earlier, I decided to try out the suggestion Felipe sent about using system-config-securitylevel-tui to open up ports 513 and 514, but that doesn't seem to do the job, either. # iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere

On 5/22/2016 9:45 PM, Eero Volotinen wrote: > Firewalld is preferred way. You should learn it.. Are there any good tools for converting an iptables-save file to a Firewalld configuration?

Some day ago, a friend post one problem for mi. whist this texts: I have a server whit 2 interfaces of network, where eth0 is the interfaces connetc to internet and eth1 to the internal network. This server hace a Squid only, but i setting the iptables for protection to the server. Iptables run from script and in this script i setting the redirection for the other server in my internal network to

I just did a fresh install of centos 5.0 from cd, followed by yum update which installed 399 packages. No failures or errors that I can see. I have three nics in the box, but am only setting up one at the moment. The box can ping others in my network, but if I try ssh, telnet, ftp, etc I get this: [root at cm network-scripts]# ftp watchdog ftp: connect: No route to host ftp> [root at cm

The closest thing I could find to an iptables to firewalld conversion tool was Offline Configuation. The firewall-offline-cmd command was created to help setup firewall rules when Firewalld is not running. For instance, to open the tcp port 22, you would type in the /etc/sysconfig/iptables file: -A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT Instead, you can now execute the

On 23 May 2016 21:03, "Mike" <1100100 at gmail.com> wrote: > > The closest thing I could find to an iptables to firewalld conversion tool > was Offline Configuation. > The firewall-offline-cmd command was created to help setup firewall rules > when Firewalld is not running. > > For instance, to open the tcp port 22, you would type in the >