Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Tasha Smith <natasha3641@yahoo.com>
To: netfilter@lists.netfilter.org
Subject: Re: iptables: exe
Date: Sat, 21 Sep 2002 15:11:08 -0700 (PDT)	[thread overview]
Message-ID: <20020921221108.11280.qmail@web20303.mail.yahoo.com> (raw)
In-Reply-To: <20020921211246.84065.qmail@web20302.mail.yahoo.com>

Thanks Anthony for your tips..:) im just starting out
with iptables soo it is really helping..and yes i have
2 interfaces soo i will move the forwarding rule to
the end, and add these rules:
iptables --policy OUTPUT DROP
iptables --policy FORWARD DROP
iptables -t nat --policy PREROUTING DROP
iptables -t nat --policy OUTPUT DROP
iptables -t nat --policy FORWARD DROP

HEHEHE...now only if i could get them to startup :)
properly!!


--- Tasha Smith <natasha3641@yahoo.com> wrote:
> Ok...i have my own iptables script trying to get it
> going...here what i have soo far in it...just
> starting
>  
> SPECS: 
> RedHat 7.2 
> 2.4.19 Kernel 
> iptables-1.2.3 
> 
> ####################################### 
> #!/bin/bash 
> 
> echo 1 = > /proc/sys/net/ipv4//ip_forward 
> iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
> 
> 
> # Remove any existing rules from all chains. 
> iptables --flush 
> iptables -t nat --flush 
> 
> # Unlimited access on the loopback interface 
> iptables -A INPUT -i lo -j ACCEPT 
> iptables -A OUPUT -o lo -j ACCPET 
> 
> # Set the fefault policy to Drop 
> iptables --policy INPUT DROP 
> ####################################### 
> Now... to get this to run on start-up here is what i
> did but it didnt start up it gave me an error. 
> chown root.root /etc/init.d/firewall 
> chmod u=rwx /etc/init.d /firewall 
> 
> And when i restart I GET ERROR... which is 
> "iptables: execvp: Permission Denied 
> rc. Starting iptables: Failed"  
> 
> I also have this line sh /etc/init.d/firewall at the
> end of my "rc.local" file 
> 
> HOW CAN I FIX THIS OR GET THEM TO START-UP PROPERLY?
> EDIT: > OOPPPPPPSS guys  i forgot to mention the
> original iptables script that came installed already
> on my system in the "/etc/init.d/" i moved that to
> somewhere else.... was i suppose to do that or just
> leave them there???
> 
> 
> 
> =====
> 
> Image by MackDaddy
> 
> __________________________________________________
> Do you Yahoo!?
> New DSL Internet Access from SBC & Yahoo!
> http://sbc.yahoo.com
> 


__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com


  parent reply	other threads:[~2002-09-21 22:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-21 21:12 iptables: exe Tasha Smith
2002-09-21 21:28 ` Antony Stone
2002-09-21 22:11 ` Tasha Smith [this message]
2002-09-21 22:37 ` Stewart Thompson
2002-09-21 22:58   ` Tasha Smith
2002-09-21 23:13     ` Stewart Thompson
2002-09-21 22:58   ` Tasha Smith
2002-09-24 20:24   ` internal ftp/port forwarding problem skmail
     [not found] <20020921220721.11083.qmail@web20303.mail.yahoo.com>
2002-09-21 22:19 ` iptables: exe Antony Stone
  -- strict thread matches above, loose matches on Subject: below --
2002-09-22  1:36 Tasha Smith
2002-09-22  1:57 ` Stewart Thompson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020921221108.11280.qmail@web20303.mail.yahoo.com \
    --to=natasha3641@yahoo.com \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox