Displaying 20 results from an estimated 80000 matches similar to: "firewall question"
2009 Aug 04
4
firewall setup for nfs
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
2011 Jan 04
9
Netinstall & NFS using local server.
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
2008 Feb 26
1
/etc/sysconfig/iptables on a stock CentOS 5 install
Greetings:
i have a pretty stock CentOS 5 machine with ports 80 and 22 exposed, so
my /etc/sysconfig/iptables file is pretty standard/straightforward.
my question is: how is this config file initially generated? i'd
like to
re-create it, and add a couple of rules .... so i don't want to lose
what's
in there already.
i see that my /etc/sysconfig/system-config-securitylevel has
2005 Apr 11
3
Default Firewall Entries
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
2006 Sep 30
2
firewall issue
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
2007 Jun 07
2
Standard RH iptables analysis
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
2009 Mar 01
2
Fail2Ban
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
2013 May 21
1
samba4 AD - strange slowness after enable iptables based firewall
Hi; I sucesyfully ran AD on samba4 software. All required by me
functions works properly but when I turn on firewall my enviroment is
getting very slow - logon process is 3 times longer then on system
with disabled firewall service. Below I pasted my firewall
configuration - I based on samba tutorial and aexples and official
microsoft web page with needed ports:
Have you similar problems after
2005 Nov 30
2
Default CentOS(Redhat) iptables, Secure?
Hi All,
whilst not being an expert on iptables, the below ouput of iptables -L
seems too insecure to me. Does anyone agree.? Perhaps I'm not
understanding it as well as I think I am.? Please give your thoughts on
this. Cheers.
Mark Sargent.
[root at localhost racket]# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all
2008 Jul 10
3
Iptables not blocking UDP port 53
I'm attempting to block access to port 53 from internet hosts for an
internal server. This device is behind a gateway router so all
traffic appears to come from source ip 10.100.1.1. Here are my
(non-working) iptables rules:
-A RH-Firewall-1-INPUT -s 10.100.1.1 -m tcp -p tcp --dport 53 -j REJECT
-A RH-Firewall-1-INPUT -s 10.100.1.1 -m udp -p udp --dport 53 -j REJECT
Further down the
2009 Mar 31
4
Samba and iptables - woes
Hi folk,
I am trying to get iptables working on a samba server but find it is
blocking something that prevents the windoze clients from being able to
access the share.
here are the bits from iptables:
> # nmb provided netbios-ns
> -A RH-Firewall-1-INPUT -p udp -m udp -s 192.168.230.100/24 -i eth1
> --dport 137 -j ACCEPT
> # nmb provided netbios-dgm
> -A RH-Firewall-1-INPUT -p udp
2007 Apr 27
0
kernel 2.6.21 on centos 5
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
2009 Jun 27
1
2 problems I can't solve without any help
Problem 1 :
Incoming conversations from the SIP-provider come into the
[default]-context and to the 's'-extension.
I am unable to change this, even if I have :
sip.conf
[general]
;context=default ; Default context for incoming calls
register => 092779077:XXXX at 85.119.188.3
; incoming
[092779077]
type=user
host=85.119.188.3
context=from3starsnet
So I define no
2009 Sep 15
2
iptables
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
2005 Jan 13
1
iptables not working with XEN2.0 on Fedora Core 3
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
2013 Oct 14
1
centos 6.x glusterfs 3.2.7 firewall blocking
centos 6.x
gluster --version
glusterfs 3.2.7 built on Jun 11 2012 13:22:29
The problem is that when i'm trying to probe like this:
gluster peer probe [hostname]
It never probe's because the firewall is blocking (when I turn it of on both
sides everything works)
But I want to keep the firewall running.
A google search give's me serveral possible ports to open , so I
2008 Jul 15
2
Help with iptables rule for blocking UDP port 53
I would like to block all DNS queries that come from one particular ip
address. I used TCPdump to verify that the queries were in fact,
coming from this IP:
[scarolan at server:~]$ sudo tcpdump -n udp port 53 and src 10.100.1.1
tcpdump: listening on eth0
11:12:17.162100 10.100.1.1.19233 > 10.100.1.61.domain: 14270+ A?
server.domain.com. (32) (DF)
Could someone help with the proper syntax
2008 Feb 28
1
Networking problems with fresh install
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
2019 Feb 12
1
Samba and ufw (Martin McGlensey)
Louis,
Made the changes. Still unable to mount office. Firewall also blocks
Thunderbird mail and maybe internet. Will check that more fully
later.Any thoughts ob Tony's response?
Outputs:
martin at radio:/etc$ sudo apt-get install ufw
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no
2013 Aug 15
2
Samba4 and iptables
Hi everyone,
I had posted recently about getting Samba4 to work on CentOS 6.4 but
having changes only replicating in one direction, from the Win2k3 AD but
not back to it. I solved the problem, this time, by disabling iptables.
I find it a bit hard to understand. These are the rules I have set up:
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [52:5888]
-A INPUT -m state