From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: Dave Johnson <djohnson+linux-kernel@sw.starentnetworks.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
lksctp-developers@lists.sourceforge.net,
sakkiped@starentnetworks.com
Subject: Re: [Lksctp-developers] [PATCH] IPv6: ipv6_addr_type() doesn't know about RFC4193 addresses
Date: Thu, 26 Jul 2007 13:59:04 -0400 [thread overview]
Message-ID: <46A8E0E8.6080209@hp.com> (raw)
In-Reply-To: <18087.62656.490978.692574@zeus.sw.starentnetworks.com>
Dave Johnson wrote:
> David Miller writes:
>> Contrarily, there may be ipv6_addr_type() call sites that really
>> do want to reject rfc4193 addresses.
>
> A quick look through the callers and only these functions should be
> effected, they check either RESERVED or UNICAST from ipv6_addr_type():
>
> net/ipv6/addrconf.c: ipv6_dev_get_saddr()
> net/ipv6/exthdrs.c: ipv6_dest_hao()
> net/ipv6/ip6_tunnel.c: ip6_tnl_set_cap()
> net/ipv6/netfilter/ip6t_REJECT.c: send_reset()
> net/ipv6/route.c: ip6_route_add()
> net/ipv6/route.c: ip6_pkt_drop()
> net/sctp/ipv6.c: sctp_v6_available()
> net/sctp/ipv6.c: sctp_v6_addr_valid()
>
Well, it's not just for SCTP. ULA address are considered of Global scope.
See this message
http://marc.info/?l=linux-netdev&m=118492205915816&w=2
-vlad
next prev parent reply other threads:[~2007-07-26 18:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 23:49 [PATCH] IPv6: ipv6_addr_type() doesn't know about RFC4193 addresses Dave Johnson
2007-07-26 0:12 ` David Miller
2007-07-26 1:11 ` Dave Johnson
2007-07-26 17:59 ` Vlad Yasevich [this message]
2007-07-26 18:37 ` YOSHIFUJI Hideaki / 吉藤英明
2007-07-26 17:21 ` Simon Arlott
2007-07-26 18:00 ` Dave Johnson
2007-07-26 18:10 ` [Lksctp-developers] " Vlad Yasevich
2007-07-26 18:06 ` Rémi Denis-Courmont
2007-07-26 18:34 ` YOSHIFUJI Hideaki / 吉藤英明
2007-07-31 0:21 ` 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=46A8E0E8.6080209@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=davem@davemloft.net \
--cc=djohnson+linux-kernel@sw.starentnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=sakkiped@starentnetworks.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.