netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe W Damasio <felipewd@gmail.com>
To: netfilter@vger.kernel.org
Cc: Bruno Gustavo Wallauer <brunogw@gmail.com>, pascal.mail@plouf.fr.eu.org
Subject: Re: ebtables broute DROP problem in production environment
Date: Wed, 30 Dec 2009 02:08:18 -0200	[thread overview]
Message-ID: <8a87046f0912292008t518031e1l8a1e21f8765e4616@mail.gmail.com> (raw)
In-Reply-To: <8a87046f0912291418x11b37daen604665a94108f128@mail.gmail.com>

  Hi All,

2009/12/29 Felipe W Damasio <felipewd@gmail.com>:
>  - The traffic is passing through the bridge just fine;
>  - When I plug a single client everything works great;
>  - When I plug in the CMTS (all the cable modem clients, then),
> everything stops.

  I now see that iptables -t mangle -L -v shows growing matches:

pkts bytes target     prot opt in     out     source
destination
 7508  466K DIVERT     tcp  --  any    any     anywhere
anywhere            socket
37713   13M TPROXY     tcp  --  eth0   any     anywhere
anywhere            tcp dpt:http TPROXY redirect 0.0.0.0:3128 mark
0x1/0x1

  So the traffic _seems_ to be routed to port 3128. But how can I make
sure that squid is getting it?

  I don't get why it's not working....since it works with a single user.

  Thanks,

Felipe Damasio

      reply	other threads:[~2009-12-30  4:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8a87046f0912231019l76e69a9eg52a529023d02237b@mail.gmail.com>
2009-12-23 18:22 ` ebtables broute DROP problem in production environment Felipe W Damasio
2009-12-23 20:48   ` Pascal Hambourg
2009-12-24 13:13   ` Felipe W Damasio
2009-12-29 22:18     ` Felipe W Damasio
2009-12-30  4:08       ` Felipe W Damasio [this message]

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=8a87046f0912292008t518031e1l8a1e21f8765e4616@mail.gmail.com \
    --to=felipewd@gmail.com \
    --cc=brunogw@gmail.com \
    --cc=netfilter@vger.kernel.org \
    --cc=pascal.mail@plouf.fr.eu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).