Text 12825, 155 rader
Skriven 2009-06-16 15:56:32 av WAYNE CHIRNSIDE (1:123/140)
     Kommentar till en text av WAYNE CHIRNSIDE
Ärende: firewalls
=================
         THIS MESSAGE WAS ORIGINALLY ADDRESSED TO MARTIN ATKINS
                 AND A CARBON COPY HAS BEEN SENT TO YOU.
-------------------------------------------------------------------------
-> -=> WAYNE CHIRNSIDE wrote to MARTIN ATKINS <=-
-> 
->  WC> With a tip or two you gave me plus something I remembered from the
->  WC> rc_firewall script I'm making progress on eliminating the errors
->  WC> one by one.
-> 
-> You've already introduced a new one.:) I'll explain in a minute.
-> 
->  WC> If I get all the errors out, questionable, I'll
->  WC> just mv rc_firewall in /etc/rc.d to rc_firewall.old
->  WC> and your firewall mv rc_firewall.
-> 
-> You don't need to keep swaping in and out of /etc/rc.d.
-> 
-> The scripts can be run after you boot. Put them in the path and make
-> them exicutable.
-> 
-> Call my one waynewall.sh shd keep your one as rc_firewall.
-> 
-> You can then call them from the command line.

I knew that much but I've lost a lot in tghe last 2+ years.

For instance, how do I run your script and output the errors
into a file???
I can create files and append them from the command line but 
redirecting the output of the run of the ./firewall ??? eludes me.

->  WC> Failing that I'll just save stuff I've downloaded to /dev/hda3
->  WC> and reinstall Slack 10.2 and
->  WC> your firewall as originally written, or nearly so before I found
->  WC> an inconsistency in it either not liking iptables in caps or vise
->  WC> versa.
-> 
-> The words in caps are not commands, they are strings that point to
-> a command or device.

Nevertheless they broke the original you sent on Slack 10.2 and I
noting the correspondence between line numbers
and iptables in caps, altered only those lines and off she went. 
 
->  WC> I think I'm to line 38 before she hits an error except
->  WC> for certain commands preceeding that near the first part of the
script
->  WC> are IIRC located elsewhere from where they were in previous scripts
-> 
->  Let's start again.
-> 
->  WC> # next line: not found
->  WC>  !/bin/sh/


->  WC> # Load modules/
-> 
-> #!/bin/sh/
-> 
-> The above line invokes the shell. It is not a comment. It's as far as I
-> know the only time the hash "#" in a script is not treated as a comment.

I removed the hash, still not found.

I removed it nevertheless and it bombed on that line, not found.



-> # Load modules
-> 
-> The above line is a comment and doesn't require a forward slash unless
it
-> reminds you to do something. It's not read by the script.

Got them out also, figured introduced by going through these gossh darned
WinBlows machines at the library before I cobbled mine together at home.
-> 
-> WC> # nor are these recognized, /sbin/modprobe
-> 
-> That's ok because they may be loaded at the kernel level. I will look
-> into it tonight and see if they are loading and where we can find them.
-> They will probaly show up in proc.
-> 
-> 
-> WC> # Load modules
-> WC> # Not all needed in this script but what the hell
->  
->  WC> /sbin/modprobe ip_conntrack_ftp
->  WC> /sbin/modprobe ip_tables
->  WC> /sbin/modprobe ip_conntrack
->  WC> /sbin/modprobe iptable_filter
->  WC> /sbin/modprobe iptable_mangle
->  WC> /sbin/modprobe iptable_nat
->  WC> /sbin/modprobe ipt_LOG
->  WC> /sbin/modprobe ipt_limit
->  WC> /sbin/modprobe ipt_state
-> 
->  WC> Then I've gotten the errors out till line 43 IIRC
-> 
->  We will get there when we deal with each issue.

That one's already gone, what I get now is directories and files not found
throuout.
A little help in redirecting that output of a command line run
./fire1 ?????, would go a l;ong ways to making it possible to send that
info to you.

I kludged LiLo and somehow fragged bzimage this morning but just booted
to disk one install, removed all the check marks and only overwrote lilo
and image.
Tada, back in full operation having lost nothing.


->  
->  your script should look exactly like this.
->   
-> #!/bin/sh/
-> 
-> /sbin/modprobe ip_conntrack_ftp
-> /sbin/modprobe ip_tables
-> /sbin/modprobe ip_conntrack
-> /sbin/modprobe iptable_filter
-> /sbin/modprobe iptable_mangle
-> /sbin/modprobe iptable_nat
-> /sbin/modprobe ipt_LOG
-> /sbin/modprobe ipt_limit
-> /sbin/modprobe ipt_state 
-> 
-> Now we are going to introduce the first string.
-> 
-> IPTABLES="/sbin/iptables"
-> 
-> From here on any time you see $IPTABLES in the script, this is what it's
-> pointing too so make sure your iptables executable is /sbin/iptables.
-> 
-> Note any errors besides the modules not loading.
-> 
-> If you have rc_firewall in the path and it is executable, envoke it at
-> the command line. Then see if all is well with iptables -L
-> 
-> If you haven't moved it yet then just go to /etc/rc.d and restart it. 
->  

I'm going to forward this to me, I'm at the library,
and take your advice from home as it will again appear in my inbox.

I had hoped top install a used DVD-CD-RW however bought used it's not
recognised.

I even tried just eject /dev/hdc through h as instructed on a installation
help text, no go.
Cable's OK as it's now on the old CDROM with the same setup as master on
IDE channel 2
--- Platinum Xpress/Win/WINServer v3.0pr5
 * Origin: Doc's Place BBS Fido Since 1991 docsplace.tzo.com (1:123/140)