From: "Artūras Šlajus" <x11@arturaz.net>
To: Billy Crook <billycrook@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Mystics of packet forwarding
Date: Wed, 07 Jan 2009 00:20:20 +0200 [thread overview]
Message-ID: <4963D924.9040905@arturaz.net> (raw)
In-Reply-To: <a43edf1b0901061254t1e3a6fb1v3a4f75b870bae810@mail.gmail.com>
Billy Crook wrote:
> Has your ISP ever indicated hostility verbally, or in writing, toward
> NAT? Is it forbidden by your Terms of Service?
Well, it says that NAT is allowed in one house. Also a friend of mine that works
as main admin on that ISP says they didn't do anything like that.
> I find it difficult to believe that your ISP would do something so
> elaborate to discourage NAT, especially if they don't explicitly
> forbid it. Try disconnecting your lan from this machine, and testing
> for this anomaly.
An idea. But it seems that only actually forwarded packets make it happen...
> I suspect one of the machines on your lan may be
> attacking yahoo or digg, and causing those sites to temporarily block
> your [public] IP.
An idea too. I'll try to get an temporary ip and monitor logs for a while...
How could this attack look like? Packet bursts? Lot of connections?
next prev parent reply other threads:[~2009-01-06 22:20 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 [this message]
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
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=4963D924.9040905@arturaz.net \
--to=x11@arturaz.net \
--cc=billycrook@gmail.com \
--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 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.