All of lore.kernel.org
 help / color / mirror / Atom feed
From: "D. Stimits" <stimits@attbi.com>
To: lartc@vger.kernel.org
Subject: [LARTC] looking for bridging/filtering info
Date: Sun, 22 Jun 2003 22:34:40 +0000	[thread overview]
Message-ID: <marc-lartc-105632118924526@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105633880201561@msgid-missing>

I'm using a linux bridge with ipchains (will be setting up some shaping 
in the near future), and looking for any current doc on specifics of 
ipchains filtering on a bridge (e.g., input and output chains become a 
bit of a paradox). At the moment, I'm looking for ways to defeat 
Microsoft popup spammers from www.byebyeads.com (they want the end user 
to pay them an extortion fee to stop sending popups that crash some 
windows apps). I already had ports 137 through 139 blocked to all 
tcp/udp, and recently added 135, but there also seem to be some 
broadcast methods of getting in, plus NetBEUI or variants, which will 
require more interesting ipchains rules. Thus, I'm especially interested 
in getting more info on how (using a linux bridge) I can stop various 
forms of broadcast attacks (which I am very unclear on the nature of).

D. Stimits, stimits AT attbi DOT com

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      reply	other threads:[~2003-06-22 22:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-22 15:24 [LARTC] looking for bridging/filtering info Trevor Warren
2003-06-22 22:34 ` D. Stimits [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=marc-lartc-105632118924526@msgid-missing \
    --to=stimits@attbi.com \
    --cc=lartc@vger.kernel.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.