From: bill4carson@gmail.com (bill4carson)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Question about tunnels, IPsec and redirect
Date: Sun, 29 Sep 2013 10:23:37 +0800 [thread overview]
Message-ID: <52478F29.8080704@gmail.com> (raw)
In-Reply-To: <CAGXs5wXQ1ay2ADRN7BNLoAUtGR_yWEAYASNJXnjBFJP+P=8acw@mail.gmail.com>
Hi, Kevin
On 2013?09?26? 15:31, Kevin Wilson wrote:
> Hi,
> Of course.
> But the (unanswered) question is:
> when sp is non NULL and we are working with IPsec, why shoudn't we
> send redirect in such a case ?
Apologize for replying late.
I think you probably missing what "ICMP redirect" does, if so please
take a look at this link:
http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094702.shtml
My understanding is:
If host is protected by gateway A using IPsec, even if a better routing for host is
gateway B, gateway A cannot tell host to using gateway B as next hop(sending redirect),
as IPsec policy is on gateway A only, not necessarily on gateway B.
I think this is scenario that the patch is try to describe.
> rgs
> Kevin
>
> On Thu, Sep 26, 2013 at 10:02 AM, bill4carson<bill4carson@gmail.com> wrote:
>> Hi Kevin
>>
>>
>> On 2013?09?25? 02:52, Kevin Wilson wrote:
>>>
>>> Hi,
>>> I am looking at this patch:
>>> http://lists.openwall.net/netdev/2007/08/24/29
>>> and I cannot understand it. Can somebody please try
>>> to explain ?
>>> more specifically:
>>> Can somebody please give an example of some setup of IPsec tunnel
>>> where the ip_rt_send_redirect() method should not be called when the
>>> skb->sp is not NULL ?
>>
>>
>> + if (rt->rt_flags&RTCF_DOREDIRECT&& !opt->srr&& !skb->sp)
>> ^^^^^^^
>> If IPsec policy is not enabled for a specific flow that this skb matches,
>> skb->sp is NULL.
>>
>>
>>
>>> (in other words, why if the SKB is and IPsec SKB, we should not send a
>>> redirect in such a case while forwarding a packet; note I am talking
>>> about IPv4)
>>>
>>> Note that the check for skb->sp was changed in recent kernels to
>>> skb_sec_path(skb), but it is essentially the same.
>>>
>>>
>>> Regards,
>>> Kevin
>>>
>>> _______________________________________________
>>> Kernelnewbies mailing list
>>> Kernelnewbies at kernelnewbies.org
>>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>>
>>
>> --
>> ?????????,??????????
>>
>> --bill
>
--
?????????,??????????
--bill
next prev parent reply other threads:[~2013-09-29 2:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 18:52 Question about tunnels, IPsec and redirect Kevin Wilson
2013-09-26 7:02 ` bill4carson
2013-09-26 7:31 ` Kevin Wilson
2013-09-29 2:23 ` bill4carson [this message]
2013-09-29 2:36 ` bill4carson
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=52478F29.8080704@gmail.com \
--to=bill4carson@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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.