From: "Artūras Šlajus" <x11@arturaz.net>
To: Ivan Petrushev <ivanatora@gmail.com>
Cc: Amos Jeffries <squid3@treenet.co.nz>, netfilter@vger.kernel.org
Subject: Re: Mystics of packet forwarding
Date: Wed, 07 Jan 2009 10:50:19 +0200 [thread overview]
Message-ID: <49646CCB.9060803@arturaz.net> (raw)
In-Reply-To: <d39744a20901070000m1491882x6665a88a22b839a4@mail.gmail.com>
Ivan Petrushev wrote:
> One think I can come with is TTL limiting (largely known here where I
> live). Try pinging these "troubling" sites from your home gateway and
> see if TTL is 1 or 2 or some bigger value.
I don't quite understand what are you saying? TTL too small and expires in path?
TTL too big and gets filtered some how?
> And one other thing - you said these sites disappear, but I didin't
> understood where from are you testing? From the home gateway or from
> the NATed boxes behind it?
From both sites..
> Could you add SNAT rule for non-existant box (IP that is not present
> on your network, like 192.168.0.200) and see if these sites work.
>
> And one other thing - /16 ? Do you really have such big network? :)
No, but I have a lot of dumbass users who love to set static ips to ones that
servers use :)) And I doubt that this is the problem...
next prev parent reply other threads:[~2009-01-07 8:50 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 [this message]
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=49646CCB.9060803@arturaz.net \
--to=x11@arturaz.net \
--cc=ivanatora@gmail.com \
--cc=netfilter@vger.kernel.org \
--cc=squid3@treenet.co.nz \
/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