From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: transparent bridge troubles?
Date: Fri, 7 Jan 2005 14:44:06 -0500 [thread overview]
Message-ID: <20050107194406.GA900@bender.817west.com> (raw)
In-Reply-To: <074001c4f4ea$388d1070$3e0010ac@esonet18>
On Fri, Jan 07, 2005 at 01:53:48PM -0500, mdpeters wrote:
> This is what my iptables setup looks like.
>
> /usr/local/sbin/iptables -P FORWARD DROP
k--so all packets traversing FORWARD that don't match one of the
following rules will get dropped.
> /usr/local/sbin/iptables -A FORWARD -p tcp --syn -m state --state NEW -j QUEUE
> /usr/local/sbin/iptables -A FORWARD -p tcp -m state --state RELATED,ESTABLISHED -j QUEUE
> /usr/local/sbin/iptables -A FORWARD -p udp -j QUEUE
> /usr/local/sbin/iptables -A FORWARD -p icmp -j QUEUE
and all we've done is QUEUE packets.
> #/usr/local/sbin/iptables -L
please use "iptables -vnxL" in the future when posting output.
> Chain INPUT (policy ACCEPT)
> target prot opt source destination
>
> Chain FORWARD (policy DROP)
> target prot opt source destination
> QUEUE all -- anywhere anywhere
> QUEUE tcp -- anywhere anywhere tcp
> flags:SYN,RST,ACK/SYN state NEW
> QUEUE tcp -- anywhere anywhere state
> RELATED,ESTABLISHED
> QUEUE udp -- anywhere anywhere
> QUEUE icmp -- anywhere anywhere
>
> Chain OUTPUT (policy ACCEPT)
> target prot opt source destination
well--you're queuing all your packets to a userspace daemon--what are
you doing with them when they get there?
-j
--
"To alcohol: the cause of, and solution to, all of life's problems."
--The Simpsons
next prev parent reply other threads:[~2005-01-07 19:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 18:53 transparent bridge troubles? mdpeters
2005-01-07 19:44 ` Jason Opperisano [this message]
2005-01-07 21:53 ` Jason Opperisano
2005-01-07 22:02 ` mdpeters
-- strict thread matches above, loose matches on Subject: below --
2005-01-07 20:14 mdpeters
2005-01-07 20:24 Daniel Chemko
2005-01-07 20:36 ` mdpeters
2005-01-07 20:42 Daniel Chemko
2005-01-07 20:44 ` Jason Opperisano
2005-01-07 20:55 ` mdpeters
2005-01-07 21:01 ` Jason Opperisano
2005-01-07 21:16 ` mdpeters
2005-01-07 21:35 ` mdpeters
2005-01-07 21:38 Daniel Chemko
2005-01-07 22:01 ` mdpeters
2005-01-07 22:18 ` Jason Opperisano
2005-01-08 0:40 ` mdpeters
2005-01-08 2:00 ` Jason Opperisano
2005-01-08 3:53 ` mdpeters
2005-01-08 4:15 ` Jason Opperisano
2005-01-08 12:12 ` mdpeters
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=20050107194406.GA900@bender.817west.com \
--to=opie@817west.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 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.