similar to: Firewall IPtables to use the SAMBA server

I've just tried setting up a Shrike (9) version of Redhat. Using the medium settings of lokkit, then adding manually accept commands for ports 137/udp 138/udp, 139/tcp and 445/tcp, I thought I should have been ready to go. This isn't the case, however. I know it's not the smb.conf settup because when I kill iptables samba works. When iptables IS running however, it will respond

Hello all. I''m about to set up a new firewall on an old 400 MHz K6-2 machine. What is the recommended, or most common way to go about it? I was thinking of doing a MINIMUM install of RedHat 8 (the option where they actually say "used for setting up things like firewalls") and then installing shorewall on top of that. Would this leave me with anything crucial missing in my

iptables -I INPUT -s 0.0.0.0/0 -p tcp --dport 5901 -j ACCEPT I'm going strictly off memoy here so you may need to man iptables. :) hadi motamedi <motamedi24 at gmail.com> wrote: >Dear All >To open a port , I know that I need to go to "System -> Administration -> >Security Level and Firewall" -> Other ports and then I can open port-5901 as >tcp

I have used lokkit to setup iptables ( I have a big script that does this) basically just ports I want with "--port=https:tcp" etc... I wish to allow igmp and add igmp to the lokkit command line? How do I do that? I can add this to /etc/sysconfig/iptables: iptables -A RH-Firewall-1-INPUT -i eth1 -j ACCEPT iptables -A RH-Firewall-1-INPUT -i eth1 -p igmp -j ACCEPT iptables-save >

hi All - I tried doing: yum provides "/usr/sbin/lokkit" on CentOS 8 and got No Matches found. Where can I get his for C8? Jerry

I have a CentOS 4.2 machine. lokkit shows that a firewall is enabled, and it is customized to allow SSH, Web, and DNS traffic only. But if I run nmap against the server IP (from my home machine, outside the local network) it shows over 1000 open ports. Am I not understanding nmap, or is there something seriously wrong here? Here is a small snip of the nmap output (I can include it all if

I have a server that I screwed up iptables on. Now when the server restarts it locks up trying to apply the firewall rules. How can I remove the rules (set to all ACCEPT) in a linux rescue mode or knoppix or other way of getting to the file system? Any suggestions how to fix this? Thanks, James

I apologize if this has been asked and answered, but I googled and attempted things for several hours today without success. I have a freshly installed CentOS 7 system that I'd like to disable the firewall and all iptables rules. Basically the equivalent of doing iptables -F In a nutshell I've tried the following commands, in many different ways and orders, but when the system

The following two patches fixes / reimplements the oVirt appliance project, installing the entire oVirt stack including all server and node components on one machine. These patches are intended to be checked out and used to build the appliance rpm, after which it is installed provides the /usr/sbin/ovirt-appliance-ctrl script to install/uninstall the appliance. The first patch merely removes

Hi, I am new to this list, and am really stumped on this issue with my samba servers. I woould really appreciate some help. Question: I am having the same type of issue. I was copping a huge set of files over to my samba server, and now, neither server works. Servers: 1) RH 7.1 running Samba, SSH, HTTPD 2) RH 7.1 running Samba, SSH, HTTPD The file trasfer crashed due to lack of space on both

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?

Hi All, Over the last 20 some years I have a file with about 200K worth of address that have "wrongly" tried to connect to my boxes running centos. So the file has one line per address or group of addresses like: 2.244.112.0/24 So using the OLD iptables I would run through my file build the iptables.txt file and start that with DROP for the IP address. iptables ran through the big

Data Wed, 22 Mar 2017 19:56:03 -0400 James Pifer <jep at obrien-pifer.com> wrote: > I apologize if this has been asked and answered, but I googled and > attempted things for several hours today without success. Iptables isn't used by default, at least not directly. Easiest way to do dosable firewall is: # systemctl mask firewalld and restart the machine. 192.168.122. subnet is

?????? 23 ???? 2016 05:56,? "Mike" <1100100 at gmail.com> ???: > > > After using iptables for a long time, I can't figure out where this syntax > comes from. > Can anyone point me in the right direction to understand the proper syntax > necessary in /etc/sysconfig/iptables? > The syntax comes from the output of the 'iptables-save' command. You can

> > If I'm understanding correctly, write out all rules in a bash terminal and > run them, and then do /usr/sbin/iptables-save --- > > ~#/usr/sbin/iptables rule; > ~#/usr/sbin/iptables rule; > ~#/usr/sbiniptables rule; > ~#/usr/sbin/iptables rule; > ~#/usr/sbin/iptables rule; > ~#/usr/sbiniptables rule; > ~#/usr/sbin/iptables rule; > ~#/usr/sbin/iptables

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

I had turned off firewalld and was using iptables when I originally installed CentOS 7.0. Two days ago I upgraded my CentOS 7.0 to 7.1. Everything seemed to be fine. Today I discovered that my iptables configuration was removed with the update. Has anyone else experienced this on doing upgrade? Literally the /etc/sysconfig/iptables is gone and the /etc/sysconfig/iptables-config is the blank

The last two router/firewall servers I had used Slackware and Gentoo. I'm used to writing complete and explicit iptables rules; however, when I set up /etc/sysconfig/iptables in CentOS 7 my usual syntax is unusable. For example, I'm used to stating postrouting masquerade as: /usr/sbin/iptables -t nat -A POSTROUTING -o eth0 -s 10.10.10.0/24 -j MASQUERADE But when I use the rule above,

Is there a CentOS equivalent to config-system-firewall in Fedora, allowing specified services to pass through? -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

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