All of lore.kernel.org
 help / color / mirror / Atom feed
From: Payam Chychi <pchychi@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Scott Mcdermott <scott@omnisys.com>, netfilter@vger.kernel.org
Subject: Re: empty filter on FORWARD chain with rp_filter means safe right?
Date: Fri, 08 Oct 2010 09:18:57 -0700	[thread overview]
Message-ID: <4CAF4471.8030903@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1010080700580.15349@obet.zrqbmnf.qr>

Jan Engelhardt wrote:
> On Friday 2010-10-08 06:40, Payam Chychi wrote:
>
>   
>> Thats correct Scott,
>> in order for any systems to abuse your setup they will need to be directly
>> connected to a segment that has knowledge of valid route to the end system...
>> meaning if a computer is 2 hops away and the router in between has no knowledge
>> of how to get to your private rfc1918 then pkts get dropped.
>>
>> Keep in mind that as ipv4 exhaustion gets extreme, some isps will use rcf1918
>> blocks and route them either in their IGP or even EGP (aka internet routes)...
>>     
>
> Internally yes, but externally no. And it's not really RFC1918 routes being
> "used in the Internet" - instead, it is "enlarging our NAT domain". (Mobile
> UMTS/HSDPA providers do this in Germany already.)
>
>   
Perhaps re-look at what rfc1918 is... also as you can read above i 
stated IGP which is internal routing and is not to increase NAT domains 
and with a "even" EGP which would be considered external to your network 
and as you can see the latter was meant for extreme cases... but what do 
i know


  reply	other threads:[~2010-10-08 16:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-08  4:31 empty filter on FORWARD chain with rp_filter means safe right? Scott Mcdermott
2010-10-08  4:40 ` Payam Chychi
2010-10-08  5:02   ` Jan Engelhardt
2010-10-08 16:18     ` Payam Chychi [this message]
2010-10-08 14:16 ` Pascal Hambourg

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=4CAF4471.8030903@gmail.com \
    --to=pchychi@gmail.com \
    --cc=jengelh@medozas.de \
    --cc=netfilter@vger.kernel.org \
    --cc=scott@omnisys.com \
    /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.