* Trouble with router and iptables
@ 2005-01-14 16:05 Brian French
2005-01-14 16:36 ` Jason Opperisano
0 siblings, 1 reply; 11+ messages in thread
From: Brian French @ 2005-01-14 16:05 UTC (permalink / raw)
To: netfilter
In our office we have a router which used iptables to nat our office
computers.
within this we have fort forwarding setup for certian services.
some of them forward ok, yet some (like ssh) will not.
also, our connection to the net goes down intermitantly on a per-computer
basis, and all i can think is that the nat is somehow not setup correctly or
that certian packets are being dropped.
below is the script which sets up iptables, could you guys please look
through it and give me any suggestions at to what i should do.
i would GREATLY appreciate your help!!
i have replaced all origional ip addresses.
200.200.200.x is external ip addresses and 192.168.0.x in internal ip
addresses.
#!/bin/sh
############################################################################
###
# This is iptables, if you need help see:
#
# http://support.imagestream.com/
#
############################################################################
###
echo -n "Setting up firewalling rules..."
############################################################################
###
# Set the variables for this script
#
# Any line with the comment '# BMF' was added by Brian
#
############################################################################
###
# Change this subnet to correspond to your private
# ethernet subnet. Home will use 192.168.1.0/24 and
# Office will use 192.168.0.0/24.
PRIVATE=192.168.0.0/24
# Loopback address
LOOP=127.0.0.1
# External interface
EXT=Serial0
EXTIP=200.200.200.10
# Internal interface
INT=Ethernet0
INTIP=192.168.0.1
############################################################################
###
# Flushing all rules.
#
# Do not uncomment these lines unless you have NAT rules that require them.
#
############################################################################
###
#modprobe ip_nat_ftp
#modprobe ip_nat_irc
# flush all previous rulesets
iptables -F
############################################################################
###
# Do not uncomment this line unless you have NAT rules below.
#
############################################################################
###
iptables -F -t nat
# Set default policies
iptables -P OUTPUT ACCEPT # BMF
iptables -P INPUT DROP # BMF
iptables -P FORWARD DROP # BMF
# Prevent external packets from using loopback addr
iptables -A INPUT -i $EXT -s $LOOP -j DROP # BMF
iptables -A FORWARD -i $EXT -s $LOOP -j DROP # BMF
iptables -A INPUT -i $EXT -d $LOOP -j DROP # BMF
iptables -A FORWARD -i $EXT -d $LOOP -j DROP # BMF
# Anything coming from the Internet should have a real Internet address
iptables -A FORWARD -i $EXT -s 192.168.0.0/16 -j DROP # BMF
iptables -A FORWARD -i $EXT -s 172.16.0.0/12 -j DROP # BMF
iptables -A FORWARD -i $EXT -s 10.0.0.0/8 -j DROP # BMF
iptables -A INPUT -i $EXT -s 192.168.0.0/16 -j DROP # BMF
iptables -A INPUT -i $EXT -s 172.16.0.0/12 -j DROP # BMF
iptables -A INPUT -i $EXT -s 10.0.0.0/8 -j DROP # BMF
# Allow local loopback
iptables -A INPUT -s $LOOP -j ACCEPT # BMF
iptables -A INPUT -d $LOOP -j ACCEPT # BMF
############################################################################
###
# If you have NAT rules and get a "ip_conntrack: table full, dropping
packet."#
# message in your kernel message log (dmesg), increase the maximum number of
#
# connections that can be tracked by uncommenting the line below
#
# Each connection uses ~ 350 bytes of memory. 16384 = 5.7 MB
#
############################################################################
###
#echo 16384 > /proc/sys/net/ipv4/ip_conntrack_max
############################################################################
###
# Use this line to masquerade for the 172.16 class B network as 1.2.3.4.
#
############################################################################
###
#iptables -t nat -A POSTROUTING -s 172.16.0.0/16 -j SNAT --to 1.2.3.4
iptables -t nat -A POSTROUTING -o $EXT -j MASQUERADE
########################################################
# Additional firewall rules sensible for most networks #
########################################################
#---- Drop all MSBlaster-type worms with ICMP scans of 92 bytes
#---- For the lowest CPU usage, try this rule before using
#---- the limit rules below
iptables -A FORWARD -p icmp -m length --length 92 -j DROP
#---- Allow all good icmp traffic through the router
iptables -A INPUT -p icmp --icmp-type echo-reply -j ACCEPT
iptables -A OUTPUT -p icmp --icmp-type echo-request -j ACCEPT
iptables -A FORWARD -p icmp --icmp-type destination-unreachable -j ACCEPT
iptables -A FORWARD -p icmp --icmp-type source-quench -j ACCEPT
iptables -A FORWARD -p icmp --icmp-type time-exceeded -j ACCEPT
iptables -A FORWARD -p icmp --icmp-type parameter-problem -j ACCEPT
iptables -A FORWARD -p icmp --icmp-type echo-reply -j ACCEPT
iptables -A FORWARD -p icmp --icmp-type echo-request -j ACCEPT
#---- Limit inbound echo-request to 5 per second inbound from gateway
#---- Limit outbound echo-request to 10 per second outbound to each gateway
#---- XXXX is the border interface on the router (e.g. "Serial0" or
"Serial3.1")
#---- This helps limit the effect of ICMP scans from worms, etc.
iptables -A FORWARD -i $EXT -m limit --limit 10/s --limit-burst 10 -p
icmp --icmp-type echo-request -j ACCEPT
iptables -A FORWARD -o $EXT -m limit --limit 5/s --limit-burst 30 -p
icmp --icmp-type echo-request -j ACCEPT
#---- Drop any icmp traffic over the limits specified above
iptables -A FORWARD -p icmp -j DROP
#---- Block common worm traffic coming in via External interfaces
#---- where "XXXX" is your Internet gateway interface
iptables -A FORWARD -j DROP -i $EXT -p tcp --dport 135:139
iptables -A FORWARD -j DROP -i $EXT -p udp --dport 135:139
iptables -A FORWARD -j DROP -i $EXT -p tcp --dport 444
iptables -A FORWARD -j DROP -i $EXT -p udp --dport 444
iptables -A FORWARD -j DROP -i $EXT -p udp --dport 995:999
iptables -A FORWARD -j DROP -o $EXT -p udp --dport 8998
#---- Block access to backdoor on system infected by W32.Novarg.A@mm Worm
iptables -A FORWARD -p tcp --dport 3127:3149 -j DROP
#################################################
#
# below is not part of the origional file.
# added by Brian French 10.22.2004
#
#################################################
## Since i was unable to get openvpn to work here
## i have set it up on the fileserver and forward
## Allow connection from Brians home to his work computer
iptables -t nat -A PREROUTING -p tcp -i $EXT \
--dport 3389 -s 200.200.200.90 --sport 1024:65535 -j DNAT --to
192.168.0.250:3389
iptables -A FORWARD -p tcp -i $EXT \
-o $INT -d 192.168.0.250 --dport 3389 -s 200.200.200.90 --sport
1024:65535 -m state --state NEW -j ACCEPT
## Allow rheanna to connect to her computer
iptables -t nat -A PREROUTING -p tcp -i $EXT \
--dport 3389 -s 200.200.200.53 --sport 1024:65535 -j DNAT --to
192.168.0.210:3389
iptables -A FORWARD -p tcp -i $EXT \
-o $INT -d 192.168.0.210 --dport 3389 -s 200.200.200.53 --sport
1024:65535 -m state --state NEW -j ACCEPT
## Allow Brian to SSH to the fileserver
iptables -t nat -A PREROUTING -p tcp -i $EXT \
--dport 222 -s 200.200.200.90 --sport 1024:65535 -j DNAT --to
192.168.0.2:22
iptables -A FORWARD -p tcp -i $EXT \
-o $INT -d 192.168.0.2 --dport 222 -s 200.200.200.90 --sport
1024:65535 -m state --state NEW -j ACCEPT
iptables -A FORWARD -t filter -i $INT -m state --state
NEW,ESTABLISHED,RELATED -j ACCEPT
iptables -A FORWARD -t filter -i $EXT -m state --state
ESTABLISHED,RELATED -j ACCEPT
# Allow services such as www and ssh (can be disabled)
iptables -A INPUT -p tcp --dport ssh -j ACCEPT
# Block outgoing NetBios (if you have windows machines running
# on the private subnet). This will not affect any NetBios
# traffic that flows over the VPN tunnel, but it will stop
# local windows machines from broadcasting themselves to
# the internet.
iptables -A FORWARD -p tcp --sport 137:139 -o $EXT -j DROP
iptables -A FORWARD -p udp --sport 137:139 -o $EXT -j DROP
iptables -A OUTPUT -p tcp --sport 137:139 -o $EXT -j DROP
iptables -A OUTPUT -p udp --sport 137:139 -o $EXT -j DROP
# Allow incoming OpenVPN packets
# Duplicate the line below for each
# OpenVPN tunnel, changing --dport n
# to match the OpenVPN UDP port.
#
# In OpenVPN, the port number is
# controlled by the --port n option.
# If you put this option in the config
# file, you can remove the leading '--'
#
# If you taking the stateful firewall
# approach (see the OpenVPN HOWTO),
# then comment out the line below.
iptables -A INPUT -p udp --dport 5000 -j ACCEPT
# Allow packets from TUN/TAP devices.
# When OpenVPN is run in a secure mode,
# it will authenticate packets prior
# to their arriving on a tun or tap
# interface. Therefore, it is not
# necessary to add any filters here,
# unless you want to restrict the
# type of packets which can flow over
# the tunnel.
iptables -A INPUT -i tun+ -j ACCEPT
iptables -A FORWARD -i tun+ -j ACCEPT
iptables -A INPUT -i tap+ -j ACCEPT
iptables -A FORWARD -i tap+ -j ACCEPT
# Allow packets from private subnets
iptables -A INPUT -i $INT -j ACCEPT
iptables -A FORWARD -i $INT -j ACCEPT
# Keep state of connections from local machine and private subnets
iptables -A OUTPUT -m state --state NEW -o $EXT -j ACCEPT
iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A FORWARD -m state --state NEW -o $EXT -j ACCEPT
iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: Trouble with router and iptables
2005-01-14 16:05 Trouble with router and iptables Brian French
@ 2005-01-14 16:36 ` Jason Opperisano
2005-01-14 16:57 ` Brian French
0 siblings, 1 reply; 11+ messages in thread
From: Jason Opperisano @ 2005-01-14 16:36 UTC (permalink / raw)
To: netfilter
On Fri, Jan 14, 2005 at 11:05:54AM -0500, Brian French wrote:
> # External interface
> EXT=Serial0
> EXTIP=200.200.200.10
> # Internal interface
> INT=Ethernet0
> INTIP=192.168.0.1
i must be waaaaaaaay out of the loop...what linux distro/kernel are you
running that uses device names "Serial0" and "Ethernet0"
> ############################################################################
> ###
> # Flushing all rules.
> #
> # Do not uncomment these lines unless you have NAT rules that require them.
> #
> ############################################################################
> ###
> #modprobe ip_nat_ftp
> #modprobe ip_nat_irc
>
> # flush all previous rulesets
> iptables -F
> ############################################################################
> ###
> # Do not uncomment this line unless you have NAT rules below.
> #
> ############################################################################
> ###
> iptables -F -t nat
>
> # Set default policies
> iptables -P OUTPUT ACCEPT # BMF
> iptables -P INPUT DROP # BMF
> iptables -P FORWARD DROP # BMF
>
> # Prevent external packets from using loopback addr
> iptables -A INPUT -i $EXT -s $LOOP -j DROP # BMF
> iptables -A FORWARD -i $EXT -s $LOOP -j DROP # BMF
> iptables -A INPUT -i $EXT -d $LOOP -j DROP # BMF
> iptables -A FORWARD -i $EXT -d $LOOP -j DROP # BMF
stylistic--the linux routing code does this for you. since you're not
logging these packets--the drops are unnecessary.
> # Anything coming from the Internet should have a real Internet address
> iptables -A FORWARD -i $EXT -s 192.168.0.0/16 -j DROP # BMF
> iptables -A FORWARD -i $EXT -s 172.16.0.0/12 -j DROP # BMF
> iptables -A FORWARD -i $EXT -s 10.0.0.0/8 -j DROP # BMF
> iptables -A INPUT -i $EXT -s 192.168.0.0/16 -j DROP # BMF
> iptables -A INPUT -i $EXT -s 172.16.0.0/12 -j DROP # BMF
> iptables -A INPUT -i $EXT -s 10.0.0.0/8 -j DROP # BMF
>
> # Allow local loopback
> iptables -A INPUT -s $LOOP -j ACCEPT # BMF
> iptables -A INPUT -d $LOOP -j ACCEPT # BMF
personally--i would change these to:
iptables -A INPUT -i lo -j ACCEPT
> iptables -t nat -A POSTROUTING -o $EXT -j MASQUERADE
if you have a static IP--use "-j SNAT --to-source $EXTIP" instead of
MASQUERADE.
<-- snip icmp stuff -->
> #---- Block common worm traffic coming in via External interfaces
> #---- where "XXXX" is your Internet gateway interface
> iptables -A FORWARD -j DROP -i $EXT -p tcp --dport 135:139
> iptables -A FORWARD -j DROP -i $EXT -p udp --dport 135:139
> iptables -A FORWARD -j DROP -i $EXT -p tcp --dport 444
> iptables -A FORWARD -j DROP -i $EXT -p udp --dport 444
you sure you don't mean "--dport 445" there?
> ## Since i was unable to get openvpn to work here
openvpn is good stuff--sorry to hear it didn't work out for you.
<-- snip RDP port-forwarding stuff -->
> ## Allow Brian to SSH to the fileserver
> iptables -t nat -A PREROUTING -p tcp -i $EXT \
> --dport 222 -s 200.200.200.90 --sport 1024:65535 -j DNAT --to
> 192.168.0.2:22
> iptables -A FORWARD -p tcp -i $EXT \
> -o $INT -d 192.168.0.2 --dport 222 -s 200.200.200.90 --sport
> 1024:65535 -m state --state NEW -j ACCEPT
the reason this doesn't work is because the dport in the FORWARD rule
needs to be 22, not 222.
> iptables -A FORWARD -t filter -i $INT -m state --state
> NEW,ESTABLISHED,RELATED -j ACCEPT
> iptables -A FORWARD -t filter -i $EXT -m state --state
> ESTABLISHED,RELATED -j ACCEPT
ok...
> # Allow services such as www and ssh (can be disabled)
> iptables -A INPUT -p tcp --dport ssh -j ACCEPT
>
> # Block outgoing NetBios (if you have windows machines running
> # on the private subnet). This will not affect any NetBios
> # traffic that flows over the VPN tunnel, but it will stop
> # local windows machines from broadcasting themselves to
> # the internet.
> iptables -A FORWARD -p tcp --sport 137:139 -o $EXT -j DROP
> iptables -A FORWARD -p udp --sport 137:139 -o $EXT -j DROP
you do realize it too late for these rules, right? you already accepted
all NEW packets in FORWARD arriving on $INT--so a machine on the inside
can send all the tcp/udp 137:139 it wants.
> iptables -A OUTPUT -p tcp --sport 137:139 -o $EXT -j DROP
> iptables -A OUTPUT -p udp --sport 137:139 -o $EXT -j DROP
<-- snip openvpn stuff -->
> # Allow packets from private subnets
> iptables -A INPUT -i $INT -j ACCEPT
> iptables -A FORWARD -i $INT -j ACCEPT
again--this FORWARD rule seems redundant, as you've already done this
above.
> # Keep state of connections from local machine and private subnets
> iptables -A OUTPUT -m state --state NEW -o $EXT -j ACCEPT
> iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
> iptables -A FORWARD -m state --state NEW -o $EXT -j ACCEPT
> iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
stylistic--i normally put all my "-m state --state ESTABLISHED,RELATED"
rules as the first rule in each chain, as those are the ones that match
the bulk of your traffic.
as for the random, per-computer drops--i dunno.
-j
--
"Mmmm...free goo."
--The Simpsons
^ permalink raw reply [flat|nested] 11+ messages in thread* RE: Trouble with router and iptables
2005-01-14 16:36 ` Jason Opperisano
@ 2005-01-14 16:57 ` Brian French
2005-01-14 17:15 ` Jason Opperisano
2005-01-14 17:30 ` Samuel Jean
0 siblings, 2 replies; 11+ messages in thread
From: Brian French @ 2005-01-14 16:57 UTC (permalink / raw)
To: Jason Opperisano, netfilter
imagestream routers
www.imagestream.com
ok thank you sooo much for your help.
based on what you have said below, i have rewritten it.
could you please look it over.
thank you soo much for your help.
i'm just a novice forced to do this because i happen to be a developer.
#!/bin/sh
############################################################################
###
# This is iptables, if you need help see:
#
# http://support.imagestream.com/
#
############################################################################
###
echo -n "Setting up firewalling rules..."
############################################################################
###
# Set the variables for this script
#
# Any line with the comment '# BMF' was added by Brian
#
############################################################################
###
# Change this subnet to correspond to your private
# ethernet subnet. Home will use 192.168.1.0/24 and
# Office will use 192.168.0.0/24.
PRIVATE=192.168.0.0/24
# Loopback address
LOOP=127.0.0.1
# External interface
EXT=Serial0
EXTIP=200.200.200.200
# Interlan interface
INT=Ethernet0
INTIP=192.168.0.1
############################################################################
###
# Flushing all rules.
#
# Do not uncomment these lines unless you have NAT rules that require them.
#
############################################################################
###
#modprobe ip_nat_ftp
#modprobe ip_nat_irc
# flush all previous rulesets
iptables -F
############################################################################
###
# Do not uncomment this line unless you have NAT rules below.
#
############################################################################
###
iptables -F -t nat
# Set default policies
iptables -P OUTPUT ACCEPT # BMF
iptables -P INPUT DROP # BMF
iptables -P FORWARD DROP # BMF
# Keep state of connections from local machine and private subnets
iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
# Anything coming from the Internet should have a real Internet address
iptables -A FORWARD -i $EXT -s 192.168.0.0/16 -j DROP # BMF
iptables -A FORWARD -i $EXT -s 172.16.0.0/12 -j DROP # BMF
iptables -A FORWARD -i $EXT -s 10.0.0.0/8 -j DROP # BMF
iptables -A INPUT -i $EXT -s 192.168.0.0/16 -j DROP # BMF
iptables -A INPUT -i $EXT -s 172.16.0.0/12 -j DROP # BMF
iptables -A INPUT -i $EXT -s 10.0.0.0/8 -j DROP # BMF
# Allow local loopback
iptables -A INPUT -i lo -j ACCEPT
# Allow packets from private subnets
iptables -A INPUT -i $INT -j ACCEPT
iptables -A FORWARD -i $INT -j ACCEPT
############################################################################
###
# If you have NAT rules and get a "ip_conntrack: table full, dropping
packet."#
# message in your kernel message log (dmesg), increase the maximum number of
#
# connections that can be tracked by uncommenting the line below
#
# Each connection uses ~ 350 bytes of memory. 16384 = 5.7 MB
#
############################################################################
###
#echo 16384 > /proc/sys/net/ipv4/ip_conntrack_max
############################################################################
###
# Use this line to masquerade for the 172.16 class B network as 1.2.3.4.
#
############################################################################
###
#iptables -t nat -A POSTROUTING -s 172.16.0.0/16 -j SNAT --to 1.2.3.4
iptables -t nat -A POSTROUTING -o $EXT -j MASQUERADE
########################################################
# Additional firewall rules sensible for most networks #
########################################################
#---- Drop all MSBlaster-type worms with ICMP scans of 92 bytes
#---- For the lowest CPU usage, try this rule before using
#---- the limit rules below
iptables -A FORWARD -p icmp -m length --length 92 -j DROP
#---- Allow all good icmp traffic through the router
iptables -A INPUT -p icmp --icmp-type echo-reply -j ACCEPT
iptables -A OUTPUT -p icmp --icmp-type echo-request -j ACCEPT
iptables -A FORWARD -p icmp --icmp-type destination-unreachable -j ACCEPT
iptables -A FORWARD -p icmp --icmp-type source-quench -j ACCEPT
iptables -A FORWARD -p icmp --icmp-type time-exceeded -j ACCEPT
iptables -A FORWARD -p icmp --icmp-type parameter-problem -j ACCEPT
iptables -A FORWARD -p icmp --icmp-type echo-reply -j ACCEPT
iptables -A FORWARD -p icmp --icmp-type echo-request -j ACCEPT
#---- Limit inbound echo-request to 5 per second inbound from gateway
#---- Limit outbound echo-request to 10 per second outbound to each gateway
#---- XXXX is the border interface on the router (e.g. "Serial0" or
"Serial3.1")
#---- This helps limit the effect of ICMP scans from worms, etc.
iptables -A FORWARD -i $EXT -m limit --limit 10/s --limit-burst 10 -p
icmp --icmp-type echo-request -j ACCEPT
iptables -A FORWARD -o $EXT -m limit --limit 5/s --limit-burst 30 -p
icmp --icmp-type echo-request -j ACCEPT
#---- Drop any icmp traffic over the limits specified above
iptables -A FORWARD -p icmp -j DROP
#---- Block common worm traffic coming in via External interfaces
#---- where "XXXX" is your Internet gateway interface
iptables -A FORWARD -j DROP -i $EXT -p tcp --dport 135:139
iptables -A FORWARD -j DROP -i $EXT -p udp --dport 135:139
iptables -A FORWARD -j DROP -i $EXT -p tcp --dport 445
iptables -A FORWARD -j DROP -i $EXT -p udp --dport 445
iptables -A FORWARD -j DROP -i $EXT -p udp --dport 995:999
iptables -A FORWARD -j DROP -o $EXT -p udp --dport 8998
#---- Block access to backdoor on system infected by W32.Novarg.A@mm Worm
iptables -A FORWARD -p tcp --dport 3127:3149 -j DROP
#################################################
#
# below is not part of the origional file.
# added by Brian French 10.22.2004
#
#################################################
## Allow connection from Brians home to his work computer
iptables -t nat -A PREROUTING -p tcp -i $EXT \
--dport 3389 -s 200.200.200.90 --sport 1024:65535 -j DNAT --to
192.168.0.250:3389
iptables -A FORWARD -p tcp -i $EXT \
-o $INT -d 192.168.0.250 --dport 3389 -s 200.200.200.90 --sport
1024:65535 -m state --state NEW -j ACCEPT
## Allow rheanna to connect to her computer
iptables -t nat -A PREROUTING -p tcp -i $EXT \
--dport 3389 -s 200.200.200.53 --sport 1024:65535 -j DNAT --to
192.168.0.210:3389
iptables -A FORWARD -p tcp -i $EXT \
-o $INT -d 192.168.0.210 --dport 3389 -s 200.200.200.53 --sport
1024:65535 -m state --state NEW -j ACCEPT
## Allow Brian to SSH to the fileserver
iptables -t nat -A PREROUTING -p tcp -i $EXT \
--dport 22 -s 200.200.200.90 --sport 1024:65535 -j DNAT --to
192.168.0.2:22
iptables -A FORWARD -p tcp -i $EXT \
-o $INT -d 192.168.0.2 --dport 222 -s 200.200.200.90 --sport
1024:65535 -m state --state NEW -j ACCEPT
# iptables -A FORWARD -t filter -i $INT -m state --state
NEW,ESTABLISHED,RELATED -j ACCEPT
# iptables -A FORWARD -t filter -i $EXT -m state --state
ESTABLISHED,RELATED -j ACCEPT
# Allow ssh (can be disabled)
iptables -A INPUT -p tcp --dport ssh -j ACCEPT
# Block outgoing NetBios (if you have windows machines running
# on the private subnet). This will not affect any NetBios
# traffic that flows over the VPN tunnel, but it will stop
# local windows machines from broadcasting themselves to
# the internet.
iptables -A FORWARD -p tcp --sport 137:139 -o $EXT -j DROP
iptables -A FORWARD -p udp --sport 137:139 -o $EXT -j DROP
iptables -A OUTPUT -p tcp --sport 137:139 -o $EXT -j DROP
iptables -A OUTPUT -p udp --sport 137:139 -o $EXT -j DROP
# Allow incoming OpenVPN packets
# Duplicate the line below for each
# OpenVPN tunnel, changing --dport n
# to match the OpenVPN UDP port.
#
# In OpenVPN, the port number is
# controlled by the --port n option.
# If you put this option in the config
# file, you can remove the leading '--'
#
# If you taking the stateful firewall
# approach (see the OpenVPN HOWTO),
# then comment out the line below.
iptables -A INPUT -p udp --dport 5000 -j ACCEPT
# Allow packets from TUN/TAP devices.
# When OpenVPN is run in a secure mode,
# it will authenticate packets prior
# to their arriving on a tun or tap
# interface. Therefore, it is not
# necessary to add any filters here,
# unless you want to restrict the
# type of packets which can flow over
# the tunnel.
iptables -A INPUT -i tun+ -j ACCEPT
iptables -A FORWARD -i tun+ -j ACCEPT
iptables -A INPUT -i tap+ -j ACCEPT
iptables -A FORWARD -i tap+ -j ACCEPT
# Keep state of connections from local machine and private subnets
iptables -A OUTPUT -m state --state NEW -o $EXT -j ACCEPT
iptables -A FORWARD -m state --state NEW -o $EXT -j ACCEPT
# iptables -A FORWARD -i $INT -m state --state NEW,ESTABLISHED,RELATED -j
ACCEPT
# iptables -A FORWARD -i $EXT -m state --state ESTABLISHED,RELATED -j
ACCEPT
############################################################################
#################
Again thank you for your help!
-----Original Message-----
From: netfilter-bounces@lists.netfilter.org
[mailto:netfilter-bounces@lists.netfilter.org]On Behalf Of Jason
Opperisano
Sent: Friday, January 14, 2005 11:37 AM
To: netfilter@lists.netfilter.org
Subject: Re: Trouble with router and iptables
On Fri, Jan 14, 2005 at 11:05:54AM -0500, Brian French wrote:
> # External interface
> EXT=Serial0
> EXTIP=200.200.200.10
> # Internal interface
> INT=Ethernet0
> INTIP=192.168.0.1
i must be waaaaaaaay out of the loop...what linux distro/kernel are you
running that uses device names "Serial0" and "Ethernet0"
>
############################################################################
> ###
> # Flushing all rules.
> #
> # Do not uncomment these lines unless you have NAT rules that require
them.
> #
>
############################################################################
> ###
> #modprobe ip_nat_ftp
> #modprobe ip_nat_irc
>
> # flush all previous rulesets
> iptables -F
>
############################################################################
> ###
> # Do not uncomment this line unless you have NAT rules below.
> #
>
############################################################################
> ###
> iptables -F -t nat
>
> # Set default policies
> iptables -P OUTPUT ACCEPT # BMF
> iptables -P INPUT DROP # BMF
> iptables -P FORWARD DROP # BMF
>
> # Prevent external packets from using loopback addr
> iptables -A INPUT -i $EXT -s $LOOP -j DROP # BMF
> iptables -A FORWARD -i $EXT -s $LOOP -j DROP # BMF
> iptables -A INPUT -i $EXT -d $LOOP -j DROP # BMF
> iptables -A FORWARD -i $EXT -d $LOOP -j DROP # BMF
stylistic--the linux routing code does this for you. since you're not
logging these packets--the drops are unnecessary.
> # Anything coming from the Internet should have a real Internet address
> iptables -A FORWARD -i $EXT -s 192.168.0.0/16 -j DROP # BMF
> iptables -A FORWARD -i $EXT -s 172.16.0.0/12 -j DROP # BMF
> iptables -A FORWARD -i $EXT -s 10.0.0.0/8 -j DROP # BMF
> iptables -A INPUT -i $EXT -s 192.168.0.0/16 -j DROP # BMF
> iptables -A INPUT -i $EXT -s 172.16.0.0/12 -j DROP # BMF
> iptables -A INPUT -i $EXT -s 10.0.0.0/8 -j DROP # BMF
>
> # Allow local loopback
> iptables -A INPUT -s $LOOP -j ACCEPT # BMF
> iptables -A INPUT -d $LOOP -j ACCEPT # BMF
personally--i would change these to:
iptables -A INPUT -i lo -j ACCEPT
> iptables -t nat -A POSTROUTING -o $EXT -j MASQUERADE
if you have a static IP--use "-j SNAT --to-source $EXTIP" instead of
MASQUERADE.
<-- snip icmp stuff -->
> #---- Block common worm traffic coming in via External interfaces
> #---- where "XXXX" is your Internet gateway interface
> iptables -A FORWARD -j DROP -i $EXT -p tcp --dport 135:139
> iptables -A FORWARD -j DROP -i $EXT -p udp --dport 135:139
> iptables -A FORWARD -j DROP -i $EXT -p tcp --dport 444
> iptables -A FORWARD -j DROP -i $EXT -p udp --dport 444
you sure you don't mean "--dport 445" there?
> ## Since i was unable to get openvpn to work here
openvpn is good stuff--sorry to hear it didn't work out for you.
<-- snip RDP port-forwarding stuff -->
> ## Allow Brian to SSH to the fileserver
> iptables -t nat -A PREROUTING -p tcp -i $EXT \
> --dport 222 -s 200.200.200.90 --sport 1024:65535 -j DNAT --to
> 192.168.0.2:22
> iptables -A FORWARD -p tcp -i $EXT \
> -o $INT -d 192.168.0.2 --dport 222 -s 200.200.200.90 --sport
> 1024:65535 -m state --state NEW -j ACCEPT
the reason this doesn't work is because the dport in the FORWARD rule
needs to be 22, not 222.
> iptables -A FORWARD -t filter -i $INT -m state --state
> NEW,ESTABLISHED,RELATED -j ACCEPT
> iptables -A FORWARD -t filter -i $EXT -m state --state
> ESTABLISHED,RELATED -j ACCEPT
ok...
> # Allow services such as www and ssh (can be disabled)
> iptables -A INPUT -p tcp --dport ssh -j ACCEPT
>
> # Block outgoing NetBios (if you have windows machines running
> # on the private subnet). This will not affect any NetBios
> # traffic that flows over the VPN tunnel, but it will stop
> # local windows machines from broadcasting themselves to
> # the internet.
> iptables -A FORWARD -p tcp --sport 137:139 -o $EXT -j DROP
> iptables -A FORWARD -p udp --sport 137:139 -o $EXT -j DROP
you do realize it too late for these rules, right? you already accepted
all NEW packets in FORWARD arriving on $INT--so a machine on the inside
can send all the tcp/udp 137:139 it wants.
> iptables -A OUTPUT -p tcp --sport 137:139 -o $EXT -j DROP
> iptables -A OUTPUT -p udp --sport 137:139 -o $EXT -j DROP
<-- snip openvpn stuff -->
> # Allow packets from private subnets
> iptables -A INPUT -i $INT -j ACCEPT
> iptables -A FORWARD -i $INT -j ACCEPT
again--this FORWARD rule seems redundant, as you've already done this
above.
> # Keep state of connections from local machine and private subnets
> iptables -A OUTPUT -m state --state NEW -o $EXT -j ACCEPT
> iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
> iptables -A FORWARD -m state --state NEW -o $EXT -j ACCEPT
> iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
stylistic--i normally put all my "-m state --state ESTABLISHED,RELATED"
rules as the first rule in each chain, as those are the ones that match
the bulk of your traffic.
as for the random, per-computer drops--i dunno.
-j
--
"Mmmm...free goo."
--The Simpsons
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: Trouble with router and iptables
2005-01-14 16:57 ` Brian French
@ 2005-01-14 17:15 ` Jason Opperisano
2005-01-14 17:50 ` Brian French
2005-01-14 17:30 ` Samuel Jean
1 sibling, 1 reply; 11+ messages in thread
From: Jason Opperisano @ 2005-01-14 17:15 UTC (permalink / raw)
To: netfilter
On Fri, Jan 14, 2005 at 11:57:49AM -0500, Brian French wrote:
> imagestream routers
> www.imagestream.com
neat.
> ok thank you sooo much for your help.
> based on what you have said below, i have rewritten it.
> could you please look it over.
> thank you soo much for your help.
> i'm just a novice forced to do this because i happen to be a developer.
<-- snip -->
> # Set default policies
> iptables -P OUTPUT ACCEPT # BMF
> iptables -P INPUT DROP # BMF
> iptables -P FORWARD DROP # BMF
>
> # Keep state of connections from local machine and private subnets
> iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
> iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
nice.
<-- snip -->
> ## Allow connection from Brians home to his work computer
> iptables -t nat -A PREROUTING -p tcp -i $EXT \
> --dport 3389 -s 200.200.200.90 --sport 1024:65535 -j DNAT --to
> 192.168.0.250:3389
> iptables -A FORWARD -p tcp -i $EXT \
> -o $INT -d 192.168.0.250 --dport 3389 -s 200.200.200.90 --sport
> 1024:65535 -m state --state NEW -j ACCEPT
>
> ## Allow rheanna to connect to her computer
> iptables -t nat -A PREROUTING -p tcp -i $EXT \
> --dport 3389 -s 200.200.200.53 --sport 1024:65535 -j DNAT --to
> 192.168.0.210:3389
> iptables -A FORWARD -p tcp -i $EXT \
> -o $INT -d 192.168.0.210 --dport 3389 -s 200.200.200.53 --sport
> 1024:65535 -m state --state NEW -j ACCEPT
>
> ## Allow Brian to SSH to the fileserver
> iptables -t nat -A PREROUTING -p tcp -i $EXT \
> --dport 22 -s 200.200.200.90 --sport 1024:65535 -j DNAT --to
> 192.168.0.2:22
> iptables -A FORWARD -p tcp -i $EXT \
> -o $INT -d 192.168.0.2 --dport 222 -s 200.200.200.90 --sport
> 1024:65535 -m state --state NEW -j ACCEPT
whoops--we got turned around there. are you trying to ssh from the
Internet to the ip of the firewall on tcp port 222 and have that
forwarded to tcp port 22 on 192.168.0.2? if so:
iptables -t nat -A PREROUTING -p tcp -i $EXT --dport 222 \
-s 200.200.200.90 --sport 1024:65535 -j DNAT --to 192.168.0.2:22
iptables -A FORWARD -p tcp -i $EXT -o $INT -d 192.168.0.2 --dport 22 \
-s 200.200.200.90 --sport 1024:65535 -m state --state NEW -j ACCEPT
sorry--i don't think i was very clear in my last response.
> # iptables -A FORWARD -t filter -i $INT -m state --state
> NEW,ESTABLISHED,RELATED -j ACCEPT
> # iptables -A FORWARD -t filter -i $EXT -m state --state
> ESTABLISHED,RELATED -j ACCEPT
i think these are unnecessary now--with the additions you made above.
> # Allow ssh (can be disabled)
> iptables -A INPUT -p tcp --dport ssh -j ACCEPT
>
> # Block outgoing NetBios (if you have windows machines running
> # on the private subnet). This will not affect any NetBios
> # traffic that flows over the VPN tunnel, but it will stop
> # local windows machines from broadcasting themselves to
> # the internet.
> iptables -A FORWARD -p tcp --sport 137:139 -o $EXT -j DROP
> iptables -A FORWARD -p udp --sport 137:139 -o $EXT -j DROP
again--these would need to appear above your:
iptables -A FORWARD -i $INT -j ACCEPT
rule for them to have an effect. rules are matched in order--first
terminating match wins (ACCEPT and DROP are both terminating matches)
-j
--
"Dear Baby, Welcome to Dumpsville. Population: You"
--The Simpsons
^ permalink raw reply [flat|nested] 11+ messages in thread* RE: Trouble with router and iptables
2005-01-14 17:15 ` Jason Opperisano
@ 2005-01-14 17:50 ` Brian French
2005-01-14 18:19 ` Jason Opperisano
0 siblings, 1 reply; 11+ messages in thread
From: Brian French @ 2005-01-14 17:50 UTC (permalink / raw)
To: netfilter
ok, so taking your following advise, i have come up with what i have below.
(i'm only including the entire script so if people search the archives, they
have a full script as a reference.)
this seem to be ok?
#!/bin/sh
echo -n "Setting up firewall"
# Change this subnet to correspond to your private
# ethernet subnet. Home will use 192.168.1.0/24 and
# Office will use 192.168.0.0/24.
PRIVATE=192.168.0.0/24
# Loopback address
LOOP=127.0.0.1
# External interface
EXT=Serial0
EXTIP=200.200.200.200
# Interlan interface
INT=Ethernet0
INTIP=192.168.0.1
############################################################################
###
# Flushing all rules.
#
# Do not uncomment these lines unless you have NAT rules that require them.
#
############################################################################
###
#modprobe ip_nat_ftp
#modprobe ip_nat_irc
echo -n "Resetting firewall rules"
# flush all previous rulesets
iptables -F
############################################################################
###
# Do not uncomment this line unless you have NAT rules below.
#
############################################################################
###
iptables -F -t nat
echo -n "Setting default policy"
# Set default policies
iptables -P OUTPUT ACCEPT # BMF
iptables -P INPUT DROP # BMF
iptables -P FORWARD DROP # BMF
# Keep state of connections from local machine and private subnets
iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
# Anything coming from the Internet should have a real Internet address
iptables -A FORWARD -i $EXT -s 192.168.0.0/16 -j DROP # BMF
iptables -A FORWARD -i $EXT -s 172.16.0.0/12 -j DROP # BMF
iptables -A FORWARD -i $EXT -s 10.0.0.0/8 -j DROP # BMF
iptables -A INPUT -i $EXT -s 192.168.0.0/16 -j DROP # BMF
iptables -A INPUT -i $EXT -s 172.16.0.0/12 -j DROP # BMF
iptables -A INPUT -i $EXT -s 10.0.0.0/8 -j DROP # BMF
# Allow local loopback
iptables -A INPUT -i lo -j ACCEPT
# Block outgoing NetBios (if you have windows machines running
# on the private subnet). This will not affect any NetBios
# traffic that flows over the VPN tunnel, but it will stop
# local windows machines from broadcasting themselves to
# the internet.
iptables -A FORWARD -p tcp --sport 137:139 -o $EXT -j DROP
iptables -A FORWARD -p udp --sport 137:139 -o $EXT -j DROP
iptables -A OUTPUT -p tcp --sport 137:139 -o $EXT -j DROP
iptables -A OUTPUT -p udp --sport 137:139 -o $EXT -j DROP
# Allow packets from private subnets
iptables -A INPUT -i $INT -j ACCEPT
iptables -A FORWARD -i $INT -j ACCEPT
############################################################################
###
# If you have NAT rules and get a "ip_conntrack: table full, dropping
packet."#
# message in your kernel message log (dmesg), increase the maximum number of
#
# connections that can be tracked by uncommenting the line below
#
# Each connection uses ~ 350 bytes of memory. 16384 = 5.7 MB
#
############################################################################
###
#echo 16384 > /proc/sys/net/ipv4/ip_conntrack_max
############################################################################
###
# Use this line to masquerade for the 172.16 class B network as 1.2.3.4.
#
############################################################################
###
#iptables -t nat -A POSTROUTING -s 172.16.0.0/16 -j SNAT --to 1.2.3.4
echo -n "Setting up NAT"
iptables -t nat -A POSTROUTING -o $EXT -j MASQUERADE
########################################################
# Additional firewall rules sensible for most networks #
########################################################
#---- Drop all MSBlaster-type worms with ICMP scans of 92 bytes
#---- For the lowest CPU usage, try this rule before using
#---- the limit rules below
iptables -A FORWARD -p icmp -m length --length 92 -j DROP
#---- Allow all good icmp traffic through the router
iptables -A INPUT -p icmp --icmp-type echo-reply -j ACCEPT
iptables -A OUTPUT -p icmp --icmp-type echo-request -j ACCEPT
iptables -A FORWARD -p icmp --icmp-type destination-unreachable -j ACCEPT
iptables -A FORWARD -p icmp --icmp-type source-quench -j ACCEPT
iptables -A FORWARD -p icmp --icmp-type time-exceeded -j ACCEPT
iptables -A FORWARD -p icmp --icmp-type parameter-problem -j ACCEPT
iptables -A FORWARD -p icmp --icmp-type echo-reply -j ACCEPT
iptables -A FORWARD -p icmp --icmp-type echo-request -j ACCEPT
#---- Limit inbound echo-request to 5 per second inbound from gateway
#---- Limit outbound echo-request to 10 per second outbound to each gateway
#---- XXXX is the border interface on the router (e.g. "Serial0" or
"Serial3.1")
#---- This helps limit the effect of ICMP scans from worms, etc.
iptables -A FORWARD -i $EXT -m limit --limit 10/s --limit-burst 10 -p
icmp --icmp-type echo-request -j ACCEPT
iptables -A FORWARD -o $EXT -m limit --limit 5/s --limit-burst 30 -p
icmp --icmp-type echo-request -j ACCEPT
#---- Drop any icmp traffic over the limits specified above
iptables -A FORWARD -p icmp -j DROP
#---- Block common worm traffic coming in via External interfaces
#---- where "XXXX" is your Internet gateway interface
iptables -A FORWARD -j DROP -i $EXT -p tcp --dport 135:139
iptables -A FORWARD -j DROP -i $EXT -p udp --dport 135:139
iptables -A FORWARD -j DROP -i $EXT -p tcp --dport 445
iptables -A FORWARD -j DROP -i $EXT -p udp --dport 445
iptables -A FORWARD -j DROP -i $EXT -p udp --dport 995:999
iptables -A FORWARD -j DROP -o $EXT -p udp --dport 8998
#---- Block access to backdoor on system infected by W32.Novarg.A@mm Worm
iptables -A FORWARD -p tcp --dport 3127:3149 -j DROP
#################################################
#
# below is not part of the origional file.
# added by Brian French 10.22.2004
#
#################################################
echo -n "Setting up Port Forwarding Rules"
## Allow connection from Brians home to his work computer
iptables -t nat -A PREROUTING -p tcp -i $EXT \
--dport 3389 -s 200.200.200.90 --sport 1024:65535 -j DNAT --to
192.168.0.250:3389
iptables -A FORWARD -p tcp -i $EXT \
-o $INT -d 192.168.0.250 --dport 3389 -s 200.200.200.90 --sport
1024:65535 -m state --state NEW -j ACCEPT
## Allow rheanna to connect to her computer
iptables -t nat -A PREROUTING -p tcp -i $EXT \
--dport 3389 -s 200.200.200.53 --sport 1024:65535 -j DNAT --to
192.168.0.210:3389
iptables -A FORWARD -p tcp -i $EXT \
-o $INT -d 192.168.0.210 --dport 3389 -s 200.200.200.53 --sport
1024:65535 -m state --state NEW -j ACCEPT
## Allow Brian to SSH to the fileserver
iptables -t nat -A PREROUTING -p tcp -i $EXT --dport 222 \
-s 200.200.200.90 --sport 1024:65535 -j DNAT --to 192.168.0.2:22
iptables -A FORWARD -p tcp -i $EXT -o $INT -d 192.168.0.2 --dport 22 \
-s 200.200.200.90 --sport 1024:65535 -m state --state NEW -j ACCEPT
# Allow ssh (can be disabled)
iptables -A INPUT -p tcp --dport ssh -j ACCEPT
echo -n "Setting up OpenVPN Rules"
# Allow incoming OpenVPN packets
# Duplicate the line below for each
# OpenVPN tunnel, changing --dport n
# to match the OpenVPN UDP port.
#
# In OpenVPN, the port number is
# controlled by the --port n option.
# If you put this option in the config
# file, you can remove the leading '--'
#
# If you taking the stateful firewall
# approach (see the OpenVPN HOWTO),
# then comment out the line below.
iptables -A INPUT -p udp --dport 5000 -j ACCEPT
# Allow packets from TUN/TAP devices.
# When OpenVPN is run in a secure mode,
# it will authenticate packets prior
# to their arriving on a tun or tap
# interface. Therefore, it is not
# necessary to add any filters here,
# unless you want to restrict the
# type of packets which can flow over
# the tunnel.
iptables -A INPUT -i tun+ -j ACCEPT
iptables -A FORWARD -i tun+ -j ACCEPT
iptables -A INPUT -i tap+ -j ACCEPT
iptables -A FORWARD -i tap+ -j ACCEPT
# Keep state of connections from local machine and private subnets
iptables -A OUTPUT -m state --state NEW -o $EXT -j ACCEPT
iptables -A FORWARD -m state --state NEW -o $EXT -j ACCEPT
############################################################################
##
-----Original Message-----
From: netfilter-bounces@lists.netfilter.org
[mailto:netfilter-bounces@lists.netfilter.org]On Behalf Of Jason
Opperisano
Sent: Friday, January 14, 2005 12:16 PM
To: netfilter@lists.netfilter.org
Subject: Re: Trouble with router and iptables
On Fri, Jan 14, 2005 at 11:57:49AM -0500, Brian French wrote:
> imagestream routers
> www.imagestream.com
neat.
> ok thank you sooo much for your help.
> based on what you have said below, i have rewritten it.
> could you please look it over.
> thank you soo much for your help.
> i'm just a novice forced to do this because i happen to be a developer.
<-- snip -->
> # Set default policies
> iptables -P OUTPUT ACCEPT # BMF
> iptables -P INPUT DROP # BMF
> iptables -P FORWARD DROP # BMF
>
> # Keep state of connections from local machine and private subnets
> iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
> iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
nice.
<-- snip -->
> ## Allow connection from Brians home to his work computer
> iptables -t nat -A PREROUTING -p tcp -i $EXT \
> --dport 3389 -s 200.200.200.90 --sport 1024:65535 -j DNAT --to
> 192.168.0.250:3389
> iptables -A FORWARD -p tcp -i $EXT \
> -o $INT -d 192.168.0.250 --dport 3389 -s 200.200.200.90 --sport
> 1024:65535 -m state --state NEW -j ACCEPT
>
> ## Allow rheanna to connect to her computer
> iptables -t nat -A PREROUTING -p tcp -i $EXT \
> --dport 3389 -s 200.200.200.53 --sport 1024:65535 -j DNAT --to
> 192.168.0.210:3389
> iptables -A FORWARD -p tcp -i $EXT \
> -o $INT -d 192.168.0.210 --dport 3389 -s 200.200.200.53 --sport
> 1024:65535 -m state --state NEW -j ACCEPT
>
> ## Allow Brian to SSH to the fileserver
> iptables -t nat -A PREROUTING -p tcp -i $EXT \
> --dport 22 -s 200.200.200.90 --sport 1024:65535 -j DNAT --to
> 192.168.0.2:22
> iptables -A FORWARD -p tcp -i $EXT \
> -o $INT -d 192.168.0.2 --dport 222 -s 200.200.200.90 --sport
> 1024:65535 -m state --state NEW -j ACCEPT
whoops--we got turned around there. are you trying to ssh from the
Internet to the ip of the firewall on tcp port 222 and have that
forwarded to tcp port 22 on 192.168.0.2? if so:
iptables -t nat -A PREROUTING -p tcp -i $EXT --dport 222 \
-s 200.200.200.90 --sport 1024:65535 -j DNAT --to 192.168.0.2:22
iptables -A FORWARD -p tcp -i $EXT -o $INT -d 192.168.0.2 --dport 22 \
-s 200.200.200.90 --sport 1024:65535 -m state --state NEW -j ACCEPT
sorry--i don't think i was very clear in my last response.
> # iptables -A FORWARD -t filter -i $INT -m state --state
> NEW,ESTABLISHED,RELATED -j ACCEPT
> # iptables -A FORWARD -t filter -i $EXT -m state --state
> ESTABLISHED,RELATED -j ACCEPT
i think these are unnecessary now--with the additions you made above.
> # Allow ssh (can be disabled)
> iptables -A INPUT -p tcp --dport ssh -j ACCEPT
>
> # Block outgoing NetBios (if you have windows machines running
> # on the private subnet). This will not affect any NetBios
> # traffic that flows over the VPN tunnel, but it will stop
> # local windows machines from broadcasting themselves to
> # the internet.
> iptables -A FORWARD -p tcp --sport 137:139 -o $EXT -j DROP
> iptables -A FORWARD -p udp --sport 137:139 -o $EXT -j DROP
again--these would need to appear above your:
iptables -A FORWARD -i $INT -j ACCEPT
rule for them to have an effect. rules are matched in order--first
terminating match wins (ACCEPT and DROP are both terminating matches)
-j
--
"Dear Baby, Welcome to Dumpsville. Population: You"
--The Simpsons
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: Trouble with router and iptables
2005-01-14 17:50 ` Brian French
@ 2005-01-14 18:19 ` Jason Opperisano
2005-01-14 18:53 ` Brian French
0 siblings, 1 reply; 11+ messages in thread
From: Jason Opperisano @ 2005-01-14 18:19 UTC (permalink / raw)
To: netfilter
On Fri, Jan 14, 2005 at 12:50:19PM -0500, Brian French wrote:
> ok, so taking your following advise, i have come up with what i have below.
>
> (i'm only including the entire script so if people search the archives, they
> have a full script as a reference.)
>
> this seem to be ok?
s'alright by me. but that's just IMHO.
-j
--
"To alcohol: the cause of, and solution to, all of life's problems."
--The Simpsons
^ permalink raw reply [flat|nested] 11+ messages in thread* RE: Trouble with router and iptables
2005-01-14 18:19 ` Jason Opperisano
@ 2005-01-14 18:53 ` Brian French
0 siblings, 0 replies; 11+ messages in thread
From: Brian French @ 2005-01-14 18:53 UTC (permalink / raw)
To: netfilter
ok, well i'll impliment it and see if anything happens, etc.
again, thank you for your help.
-----Original Message-----
From: netfilter-bounces@lists.netfilter.org
[mailto:netfilter-bounces@lists.netfilter.org]On Behalf Of Jason
Opperisano
Sent: Friday, January 14, 2005 1:20 PM
To: netfilter@lists.netfilter.org
Subject: Re: Trouble with router and iptables
On Fri, Jan 14, 2005 at 12:50:19PM -0500, Brian French wrote:
> ok, so taking your following advise, i have come up with what i have
below.
>
> (i'm only including the entire script so if people search the archives,
they
> have a full script as a reference.)
>
> this seem to be ok?
s'alright by me. but that's just IMHO.
-j
--
"To alcohol: the cause of, and solution to, all of life's problems."
--The Simpsons
^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: Trouble with router and iptables
2005-01-14 16:57 ` Brian French
2005-01-14 17:15 ` Jason Opperisano
@ 2005-01-14 17:30 ` Samuel Jean
2005-01-14 17:34 ` Brian French
1 sibling, 1 reply; 11+ messages in thread
From: Samuel Jean @ 2005-01-14 17:30 UTC (permalink / raw)
To: Brian French; +Cc: netfilter
On Fri, January 14, 2005 11:57 am, Brian French said:
> # External interface
> EXT=Serial0
> EXTIP=200.200.200.200
> # Interlan interface
> INT=Ethernet0
> INTIP=192.168.0.1
Uhmm.. Does anyone ported netfilter to Cisco's IOS ?
Just kidding.. 8)
Cheers!
^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: Trouble with router and iptables
2005-01-14 17:30 ` Samuel Jean
@ 2005-01-14 17:34 ` Brian French
0 siblings, 0 replies; 11+ messages in thread
From: Brian French @ 2005-01-14 17:34 UTC (permalink / raw)
Cc: netfilter
imagestream created a a program called 'sand'
it's interface and config file looks just like Cisco's IOS' files.
-----Original Message-----
From: Samuel Jean [mailto:sj-netfilter@cookinglinux.org]
Sent: Friday, January 14, 2005 12:31 PM
To: Brian French
Cc: netfilter@lists.netfilter.org
Subject: RE: Trouble with router and iptables
On Fri, January 14, 2005 11:57 am, Brian French said:
> # External interface
> EXT=Serial0
> EXTIP=200.200.200.200
> # Interlan interface
> INT=Ethernet0
> INTIP=192.168.0.1
Uhmm.. Does anyone ported netfilter to Cisco's IOS ?
Just kidding.. 8)
Cheers!
^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: Trouble with router and iptables
@ 2005-01-14 17:39 Hudson Delbert J Contr 61 CS/SCBN
2005-01-14 17:58 ` Brian French
0 siblings, 1 reply; 11+ messages in thread
From: Hudson Delbert J Contr 61 CS/SCBN @ 2005-01-14 17:39 UTC (permalink / raw)
To: Brian French; +Cc: netfilter
what does 'sand' do? as there isnt any other info in this message. so i cant
tell what the thread is.
url ? for imagestream is ????
~piranha
-----Original Message-----
From: netfilter-bounces@lists.netfilter.org
[mailto:netfilter-bounces@lists.netfilter.org]On Behalf Of Brian French
Sent: Friday, January 14, 2005 9:35 AM
Cc: netfilter@lists.netfilter.org
Subject: RE: Trouble with router and iptables
imagestream created a a program called 'sand'
it's interface and config file looks just like Cisco's IOS' files.
-----Original Message-----
From: Samuel Jean [mailto:sj-netfilter@cookinglinux.org]
Sent: Friday, January 14, 2005 12:31 PM
To: Brian French
Cc: netfilter@lists.netfilter.org
Subject: RE: Trouble with router and iptables
On Fri, January 14, 2005 11:57 am, Brian French said:
> # External interface
> EXT=Serial0
> EXTIP=200.200.200.200
> # Interlan interface
> INT=Ethernet0
> INTIP=192.168.0.1
Uhmm.. Does anyone ported netfilter to Cisco's IOS ?
Just kidding.. 8)
Cheers!
^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: Trouble with router and iptables
2005-01-14 17:39 Hudson Delbert J Contr 61 CS/SCBN
@ 2005-01-14 17:58 ` Brian French
0 siblings, 0 replies; 11+ messages in thread
From: Brian French @ 2005-01-14 17:58 UTC (permalink / raw)
To: Hudson Delbert J Contr 61 CS/SCBN; +Cc: netfilter
www.imagestream.com
the page that talks about SAND:
http://www.imagestream.com/SAND.html
-----Original Message-----
From: Hudson Delbert J Contr 61 CS/SCBN
[mailto:Delbert.Hudson@LOSANGELES.AF.MIL]
Sent: Friday, January 14, 2005 12:39 PM
To: Brian French
Cc: netfilter@lists.netfilter.org
Subject: RE: Trouble with router and iptables
what does 'sand' do? as there isnt any other info in this message. so i cant
tell what the thread is.
url ? for imagestream is ????
~piranha
-----Original Message-----
From: netfilter-bounces@lists.netfilter.org
[mailto:netfilter-bounces@lists.netfilter.org]On Behalf Of Brian French
Sent: Friday, January 14, 2005 9:35 AM
Cc: netfilter@lists.netfilter.org
Subject: RE: Trouble with router and iptables
imagestream created a a program called 'sand'
it's interface and config file looks just like Cisco's IOS' files.
-----Original Message-----
From: Samuel Jean [mailto:sj-netfilter@cookinglinux.org]
Sent: Friday, January 14, 2005 12:31 PM
To: Brian French
Cc: netfilter@lists.netfilter.org
Subject: RE: Trouble with router and iptables
On Fri, January 14, 2005 11:57 am, Brian French said:
> # External interface
> EXT=Serial0
> EXTIP=200.200.200.200
> # Interlan interface
> INT=Ethernet0
> INTIP=192.168.0.1
Uhmm.. Does anyone ported netfilter to Cisco's IOS ?
Just kidding.. 8)
Cheers!
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2005-01-14 18:53 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-01-14 16:05 Trouble with router and iptables Brian French
2005-01-14 16:36 ` Jason Opperisano
2005-01-14 16:57 ` Brian French
2005-01-14 17:15 ` Jason Opperisano
2005-01-14 17:50 ` Brian French
2005-01-14 18:19 ` Jason Opperisano
2005-01-14 18:53 ` Brian French
2005-01-14 17:30 ` Samuel Jean
2005-01-14 17:34 ` Brian French
-- strict thread matches above, loose matches on Subject: below --
2005-01-14 17:39 Hudson Delbert J Contr 61 CS/SCBN
2005-01-14 17:58 ` Brian French
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.