From: Tomasz Chmielewski <mangoo@wpkg•org>
To: David Miller <davem@davemloft•net>
Cc: ja@ssi•bg, eric.dumazet@gmail•com, netdev@vger•kernel.org,
bazsi@balabit•hu, hidden@balabit•hu
Subject: Re: what's causing "ip_rt_bug"?
Date: Tue, 28 Jun 2011 10:30:11 +0200 [thread overview]
Message-ID: <4E099113.6000801@wpkg.org> (raw)
In-Reply-To: <20110627.205544.111681152997205782.davem@davemloft.net>
On 28.06.2011 05:55, David Miller wrote:
>> The resulting handling should be:
>>
>> - REJECT TCP:
>> - in INPUT we can provide addr_type = RTN_LOCAL but
>> better allow rejecting traffic delivered with
>> local route (no IP address => use RTN_UNSPEC to
>> allow also RTN_UNICAST).
>> - FORWARD: RTN_UNSPEC => allow RTN_LOCAL/RTN_UNICAST
>> saddr, add fix to ignore RTN_BROADCAST and RTN_MULTICAST
>> - OUTPUT: RTN_UNSPEC
>>
>> - NAT, mangle, ip_queue, nf_ip_reroute: RTN_UNSPEC in LOCAL_OUT
>>
>> - IPVS:
>> - use RTN_LOCAL in LOCAL_OUT and FORWARD after SNAT
>> to restrict saddr to be local
>>
>> Signed-off-by: Julian Anastasov<ja@ssi•bg>
>
> Unless someone gives some negative feedback soon I'm going to
> apply this.
Can you tell me where it will be pushed?
I.e. 3.x kernels only, or does it have a chance to go into 2.6.39.x?
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2011-06-28 8:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 20:00 what's causing "ip_rt_bug"? Tomasz Chmielewski
2011-06-17 20:36 ` Eric Dumazet
2011-06-17 21:37 ` Tomasz Chmielewski
2011-06-17 23:56 ` Julian Anastasov
2011-06-18 8:31 ` Tomasz Chmielewski
2011-06-18 17:53 ` Julian Anastasov
2011-06-28 3:55 ` David Miller
2011-06-28 8:13 ` Julian Anastasov
2011-06-28 8:41 ` David Miller
2011-06-28 9:05 ` Julian Anastasov
2011-06-28 8:30 ` Tomasz Chmielewski [this message]
2011-06-28 8:40 ` David Miller
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=4E099113.6000801@wpkg.org \
--to=mangoo@wpkg$(echo .)org \
--cc=bazsi@balabit$(echo .)hu \
--cc=davem@davemloft$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=hidden@balabit$(echo .)hu \
--cc=ja@ssi$(echo .)bg \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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