All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: transparent bridge troubles?
Date: Fri, 7 Jan 2005 16:01:03 -0500	[thread overview]
Message-ID: <20050107210103.GA1193@bender.817west.com> (raw)
In-Reply-To: <002e01c4f4fb$4a24f080$3e0010ac@esonet18>

On Fri, Jan 07, 2005 at 03:55:58PM -0500, mdpeters wrote:
> OK. This is what I have loaded now.
> 
> /usr/local/sbin/iptables -P FORWARD DROP
> /usr/local/sbin/iptables -A FORWARD -j LOG --log-prefix 
> /var/iptablequeue/pre_queue
> /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
> /usr/local/sbin/iptables -A FORWARD -j LOG --log-prefix 
> /var/iptablequeue/post_queue
> 
> I should see some sort of log file in /var/iptablequeue/post_queue or 
> /var/iptablequeue/pre_queue now? Should I try sending packets through the 
> bridge to generate something?

uh--no.  those rules might not even load.  "--log-prefix" specifies a
string to prefix the log entries in your syslog files.  my rules were
literal:

/usr/local/sbin/iptables -A FORWARD -j LOG --log-prefix "PRE QUEUE: "

...

/usr/local/sbin/iptables -A FORWARD -j LOG --log-prefix "POST QUEUE: "

so the entries in /var/log/messages will have the strings "PRE QUEUE: "
and "POST QUEUE: " in them for identification purposes.

-j

--
"Kids, you tried your best and you failed miserably. The lesson is,
 never try."
        --The Simpsons


  reply	other threads:[~2005-01-07 21:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-07 20:42 transparent bridge troubles? Daniel Chemko
2005-01-07 20:44 ` Jason Opperisano
2005-01-07 20:55   ` mdpeters
2005-01-07 21:01     ` Jason Opperisano [this message]
2005-01-07 21:16       ` mdpeters
2005-01-07 21:35       ` mdpeters
  -- strict thread matches above, loose matches on Subject: below --
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
2005-01-07 20:24 Daniel Chemko
2005-01-07 20:36 ` mdpeters
2005-01-07 20:14 mdpeters
2005-01-07 18:53 mdpeters
2005-01-07 19:44 ` Jason Opperisano
2005-01-07 21:53 ` Jason Opperisano
2005-01-07 22:02   ` 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=20050107210103.GA1193@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.