I even set OUTPUT to drop ... what happens if you get a virus or a worm? (does linux have one of those?)

Or somebody on your network (most likely w/ a windows machine) gets a virus or worm? Those packets might go thru FORWARD but if they somehow hack into your firewall then those packets would be thru OUTPUT.

I go way paranoid on my rules. I set interface names, I allow each protocol out 1 by 1, set expected ip ranges, always tcp reset when I reject, etc.... It may be a pain to setup, but I only do that once; and it protects me better 24x7 IMO.

seems like it keeps getting hung up on digg.

Greetings,

For all future videos I will include links to the transcript and script (if applicable). Here is the transcript and firewall script for this one:

Transcript: http://dark-code.bulix.org/z5svtd-68680?raw
Script: http://dark-code.bulix.org/y8t9ur-68683

These will be available in the video description from now on.

Elliot

your gay

I was able to copy the script Elliot creates while watching the video. It's not exactly the same, but captures all the same stuff

#!/bin/sh

#locate iptables (this will cause issues if the command fails, but is flexible)
IPT=`which iptables`

#or possibly the following, but on CYGWIN it's not in the right format)
#IPT=`whereis iptables`

#flush iptables
$IPT -F

#-----------------------
# POLICIES
#-----------------------

#
# DEFAULT POLICIES
#-----------------------

#For outbound traffic
$IPT -P OUTPUT ACCEPT
#For inbound traffic
$IPT -P INPUT DROP
#For routed traffic is to drop for now
$IPT -P FORWARD DROP

#
# ALLOWED INBOUND TRAFFIC
#-----------------------------

#ALLOW loopback traffic
$IPT -A INPUT --in-interface lo -j ACCEPT

#ALLOW http
$IPT -A INPUT -p tcp --dport 80 -j ACCEPT
#ALLOW ssh
$IPT -A INPUT -p tcp --dport 22 -j ACCEPT
#ALLOW Responses
$IPT -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT

The text in the captured screen in not clear, I can not read it.

Advise: use black background and white foreground, do not use colors.

Well done Elliot. Your timing couldn't have been more perfect. IPTables has always been a pain in the butt to understand. Being able to see and hear someone explain how it works is a great way to learn. I have enjoyed watching the video and will definitely tune in for the next part.

I've just installed a new Linux server at work which acts as our internet gateway via an ADSL router modem. It took me two days to setup the iptable rules and it is finally working (after reading lots of HOWTO docs). Now it will be nice to verify that what I have done is actually correct, and be able to understand all the rules I copied from the HOWTO's. ;-)

As for a transcript.
That would be nice, but I simply did the following. If you use Firefox web browser, simply look in your profile's Cache directory for a 10Mb file. That's the local copy of the video clip you watched. Simply copy it out for archiving purposes and for later enjoyment. :-)

Regards,
- Graeme -

It would be nice if there were a transcript to these videos. A transcript can be read in a short amount of time to gain knowledge, or skimmed to see if the material is relevant, or used for later reference, or even used to capture notes so all eyes can be on the viewing.

Thank you.