Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Artūras Šlajus" <x11@arturaz.net>
To: netfilter@vger.kernel.org
Subject: Mystics of packet forwarding
Date: Tue, 06 Jan 2009 21:41:31 +0200	[thread overview]
Message-ID: <4963B3EB.6090806@arturaz.net> (raw)

Hello fellow netfilter users,

I have a strange problem and I think I should blame my ISP for that...

Recently I lost connectivity to some sites (i.e. digg.com, yahoo). The best part 
is that I can regain connectivity by clearing out all the rules from iptables.

So if I have empty chains - I can connect to digg. After I add one rule:

iptables -t nat -A POSTROUTING -s 192.168.0.0/16 -j MASQUERADE (or SNAT, doesn't 
make a difference)

and bam! in 3-5 seconds I lose connectivity to these sites. Others work just fine.

The delay of impact is one thing that bothers me and makes me wonder about magic 
in ISP side.

Other thingie is if I do:

iptables -t nat -I POSTROUTING -s 192.168.0.0/16 -j DROP

After 3-5 seconds I regain connectivity... It seems that my ISP is somehow 
monitoring nat'ing and dropping access to some sites...

Any ideas why could this be happening and what is so special about digg.com and 
some of yahoo servers that they connectivity to them get affected like this?

Any ideas welcome.

Thanks, Arthur.

             reply	other threads:[~2009-01-06 19:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06 19:41 Artūras Šlajus [this message]
2009-01-06 20:54 ` Mystics of packet forwarding 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
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=4963B3EB.6090806@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