netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: cebbert@redhat.com
Cc: yoshfuji@linux-ipv6.org, netdev@vger.kernel.org
Subject: Re: IPV6 source routing patch is still broken?
Date: Thu, 26 Apr 2007 15:31:42 -0700 (PDT)	[thread overview]
Message-ID: <20070426.153142.57441302.davem@davemloft.net> (raw)
In-Reply-To: <46311F76.9040803@redhat.com>

From: Chuck Ebbert <cebbert@redhat.com>
Date: Thu, 26 Apr 2007 17:53:58 -0400

> Looking at the patch that went into 2.6.20.9, I can't see
> how type 2 packets get through at all. Shouldn't this part
> read:
> 
> +       case IPV6_SRCRT_TYPE_2:
> +               if (accept_source_route >= 0)
> +                       break;
> +               kfree_skb(skb);
> +               return -1;
> +       case IPV6_SRCRT_TYPE_0:
> +               if (accept_source_route > 0)
> +                       break;
> +               kfree_skb(skb);
> +               return -1;

Yes, that looks like it matches the sysctl documentation more closely:

accept_source_route - INTEGER
	Accept source routing (routing extension header).

	> 0: Accept routing header.
	= 0: Accept only routing header type 2.
	< 0: Do not accept routing header.

Type 2 packets should get through as long as the value of the sysctl
is not negative.

Hmmm?

  parent reply	other threads:[~2007-04-26 22:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26 21:53 IPV6 source routing patch is still broken? Chuck Ebbert
2007-04-26 22:04 ` David Miller
2007-04-26 23:10   ` Chuck Ebbert
2007-04-26 23:52     ` YOSHIFUJI Hideaki / 吉藤英明
2007-04-27  2:29     ` David Miller
2007-04-26 22:31 ` David Miller [this message]
2007-04-26 22:57   ` Chuck Ebbert
2007-04-27  9:08     ` David Miller
2007-04-27  9:36       ` YOSHIFUJI Hideaki / 吉藤英明
2007-04-27  9:41         ` 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=20070426.153142.57441302.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=cebbert@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=yoshfuji@linux-ipv6.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 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).