All of lore.kernel.org
 help / color / mirror / Atom feed
From: "mdpeters" <michael.peters@lazarusalliance.com>
To: netfilter@lists.netfilter.org
Subject: transparent bridge troubles?
Date: Fri, 7 Jan 2005 15:14:13 -0500	[thread overview]
Message-ID: <001501c4f4f5$749ae690$3e0010ac@esonet18> (raw)

Here is the output you requested:

#/usr/local/sbin/iptables -vnxL

Chain INPUT (policy ACCEPT 1177615 packets, 73906075 bytes)
    pkts      bytes target     prot opt in     out     source               destination

Chain FORWARD (policy DROP 0 packets, 0 bytes)
    pkts      bytes target     prot opt in     out     source               destination
       0        0 QUEUE      tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           tcp flags:0x16/0x02 state NEW
       0        0 QUEUE      tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED
       0        0 QUEUE      udp  --  *      *       0.0.0.0/0            0.0.0.0/0
       0        0 QUEUE      icmp --  *      *       0.0.0.0/0            0.0.0.0/0

Chain OUTPUT (policy ACCEPT 2283371 packets, 3277380013 bytes)
    pkts      bytes target     prot opt in     out     source               destination

I am queuing all of the packets to a userspace daemon for Snort-inline to process. If Snort is the problem then could you advise me on the iptables to pass everything through the transparent bridge to eliminate it from the equation?

Best regards,

Michael

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

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-07 20:14 mdpeters [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-07 21:38 transparent bridge troubles? 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: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 20:24 Daniel Chemko
2005-01-07 20:36 ` 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='001501c4f4f5$749ae690$3e0010ac@esonet18' \
    --to=michael.peters@lazarusalliance.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.