netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shan Wei <shanwei@cn.fujitsu.com>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: brian.haley@hp.com, davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: IPV6_RTHDR with a type-0 routing header
Date: Fri, 21 Aug 2009 09:09:29 +0800	[thread overview]
Message-ID: <4A8DF3C9.8000808@cn.fujitsu.com> (raw)
In-Reply-To: <20090820111152.GA20295@uio.no>

Steinar H. Gunderson wrote, at 08/20/2009 07:11 PM:
> Hi,
> 
> I've tried attaching a type-0 routing header to my IPv6 packets with
> setsockopt(..., IPV6_RTHDR, ...), but the kernel just returns EINVAL.
> looking at the source, it seems it simply refuses anything that's not type-2;
> should that really be right? I found the following commit:
> 
>   http://kerneltrap.org/mailarchive/linux-netdev/2008/11/11/4064594
> 
> However, it only seems to change EPERM into EINVAL. I don't see any

About the cause of changing EPERM into EINVAL, can refer to 
http://marc.info/?l=linux-netdev&m=122046709502496&w=3.

-- 
Best Regards
Shan Wei

> reasonable explanation why it should not be simply success; in fact, RFC 3452
> only seems to talk about using type-0 headers with this option.
> 
> Any ideas?
> 
> /* Steinar */


      parent reply	other threads:[~2009-08-21  1:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-20 11:11 IPV6_RTHDR with a type-0 routing header Steinar H. Gunderson
2009-08-20 11:29 ` Jens Rosenboom
2009-08-20 11:29 ` Rémi Denis-Courmont
2009-08-20 12:18   ` Steinar H. Gunderson
2009-08-20 12:39     ` Steinar H. Gunderson
2009-08-20 12:53       ` Jens Rosenboom
2009-08-20 13:00         ` Steinar H. Gunderson
2009-08-20 13:11           ` Steinar H. Gunderson
2009-08-21  1:09 ` Shan Wei [this message]

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=4A8DF3C9.8000808@cn.fujitsu.com \
    --to=shanwei@cn.fujitsu.com \
    --cc=brian.haley@hp.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=sgunderson@bigfoot.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).