From: "Artūras Šlajus" <x11@arturaz.net>
To: netfilter@vger.kernel.org
Subject: Re: Mystics of packet forwarding
Date: Wed, 07 Jan 2009 11:28:11 +0200 [thread overview]
Message-ID: <496475AB.9040303@arturaz.net> (raw)
In-Reply-To: <4963B3EB.6090806@arturaz.net>
Ok, it seems that really - someone in LAN is attacking the internet.
If I turn on forwarding for few users like me, some other computer-literate
friends - digg.com still works :))
Now it's the question how do I catch bad guys? What should I look into? Packet
bursts? Lot's of new connections? Etc?
next prev parent reply other threads:[~2009-01-07 9:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 19:41 Mystics of packet forwarding Artūras Šlajus
2009-01-06 20:54 ` Billy Crook
2009-01-06 22:20 ` Artūras Šlajus
2009-01-06 22:52 ` Artūras Šlajus
2009-01-07 6:15 ` Amos Jeffries
2009-01-07 8:00 ` Ivan Petrushev
2009-01-07 8:50 ` Artūras Šlajus
2009-01-07 8:43 ` Artūras Šlajus
2009-01-07 9:28 ` Artūras Šlajus [this message]
2009-01-07 10:51 ` Ivan Petrushev
2009-01-07 11:26 ` Roman Fiedler
2009-01-07 13:59 ` Billy Crook
2009-01-07 15:07 ` Mart Frauenlob
2009-01-07 15:52 ` Ivan Petrushev
2009-01-07 22:36 ` Artūras Šlajus
2009-01-08 1:26 ` /dev/rob0
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=496475AB.9040303@arturaz.net \
--to=x11@arturaz.net \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox