All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven M Campbell <Netfilter@SCampbell.net>
To: netfilter@lists.netfilter.org
Subject: Re: It seems I've found why conntrack blocks some packets
Date: Fri, 31 Mar 2006 08:20:15 -0500	[thread overview]
Message-ID: <442D2C8F.1020505@SCampbell.net> (raw)
In-Reply-To: <cc4fcc140603300601j169864eexddc8fe3dd06c1a24@mail.gmail.com>

We know from the message that we fell off of the end of the FORWARD chain (because the --log-prefix "FORWARD blocked: " is the only one to match the message....

Carlos Pastorino wrote:
	
> 
> $IPTABLES -A FORWARD -p ALL -m state --state ESTABLISHED,RELATED -j ACCEPT
> 
> $IPTABLES -A FORWARD -p ICMP -i $DMZ_IFACE -s $DMZ_RANGE -j ACCEPT
> 
> $IPTABLES -A FORWARD -p TCP -i $DMZ_IFACE -o $INET_IFACE -s $DMZ_RANGE
> -d $0/0 --syn --dport domain -j ACCEPT
> $IPTABLES -A FORWARD -p TCP -i $DMZ_IFACE -o $INET_IFACE -s $DMZ_RANGE
> -d 0/0 --syn --dport ftp -j ACCEPT
> $IPTABLES -A FORWARD -p TCP -i $DMZ_IFACE -o $INET_IFACE -s $DMZ_RANGE
> -d 0/0 --syn --dport http -j ACCEPT
> $IPTABLES -A FORWARD -p TCP -i $DMZ_IFACE -o $INET_IFACE -s $DMZ_RANGE
> -d 0/0 --syn --dport smtp -j ACCEPT
> $IPTABLES -A FORWARD -p UDP -i $DMZ_IFACE -o $INET_IFACE -s $DMZ_RANGE
> -d 0/0 --dport domain -j ACCEPT
> $IPTABLES -A FORWARD -p UDP -i $DMZ_IFACE -o $INET_IFACE -s $DMZ_RANGE
> -d 0/0 --dport ntp -j ACCEPT
> 

deleted a bunch of drop and logs, these aren't the problem

> 
> $IPTABLES -A FORWARD -p TCP -i $INET_IFACE -s 0/0 -j pre_analysis
> 

I'm removing lines that deal with ports other than http

> $IPTABLES -A FORWARD -p ICMP -i $INET_IFACE -o $DMZ_IFACE -s
> $MONITORING -d $DMZ_RANGE -j ACCEPT
> $IPTABLES -A FORWARD -p TCP -i $INET_IFACE -o $DMZ_IFACE -s 0/0 -d
> $DMZ_WEBSERVER --syn --dport http -j ACCEPT
> $IPTABLES -A FORWARD -p TCP -i $INET_IFACE -o $DMZ_IFACE -s 0/0 -d
> $DMZ_WEBSERVER --syn --dport https -j ACCEPT
> 
> 
> [SOME FORWARD LINES SUPPRESSED]
> 
> $IPTABLES -A FORWARD -j LOG --log-prefix "FORWARD blocked: "
> 
> 

Unfortunately, you've needed to obscure the actual ip address (I understand) but I can't match the 'customerip' and 'webserverip' to the ${variables} above because I don't know the actual values for any of them.

Try to walk through the rules in your forward chain using the ip addresses you've captured and identify the rule you believe should allow these ack packets to go out.


  reply	other threads:[~2006-03-31 13:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-30  5:13 It seems I've found why conntrack blocks some packets Gary W. Smith
2006-03-30 14:01 ` Carlos Pastorino
2006-03-31 13:20   ` Steven M Campbell [this message]
2006-03-31 13:43     ` Steven M Campbell
2006-04-01 20:59       ` Carlos Pastorino
2006-04-02  4:08         ` Steven M Campbell
2006-04-04 12:36           ` Carlos Pastorino
2006-04-05 14:55             ` Steven M Campbell
2006-04-06 18:33               ` Carlos Pastorino
2006-04-01 20:46     ` Carlos Pastorino
  -- strict thread matches above, loose matches on Subject: below --
2006-03-29 13:45 Carlos Pastorino
2006-03-29 13:52 ` Steven M Campbell
2006-03-29 15:11   ` Roger Hamilton
2006-03-29 15:17     ` Steven M Campbell
2006-03-29 18:04       ` Carlos Pastorino
2006-03-30  5:05         ` Carlos Pastorino

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=442D2C8F.1020505@SCampbell.net \
    --to=netfilter@scampbell.net \
    --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 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.