From: "Seong Moon" <seong@etri.re.kr>
To: <netdev@oss.sgi.com>
Subject: IPv6 : ICMPV6_DEST_UNREACH type with ICMPV6_NOROUTE code
Date: Tue, 6 May 2003 19:18:47 +0900 [thread overview]
Message-ID: <003e01c313b8$e55db620$28acfe81@seong> (raw)
Hi, there.
I'm recently analyzing the kernel source for IPv6 router.
I found that when the kernel has no forwarding entry of a packet,
the kernel sends an ICMPV6_DEST_UNREACH icmp message with
ICMPV6_ADDR_UNREACH code
to the source of the packet.
But According to RFC 2463, If the kerenl has no forwarding entry of a
packet,
the kernel must send an ICMPV6_DEST_UNREACH icmp message with ICMPV6_NOROUTE
code.
In my opinion, ip6_pkt_discard() should be modified as follows :
int ip6_pkt_discard(struct sk_buff *skb)
{
IP6_INC_STATS(Ip6OutNoRoutes);
/* icmpv6_send(skb, ICMPV6_DEST_UNREACH, ICMPV6_ADDR_UNREACH, 0,
skb->dev); */
icmpv6_send(skb, ICMPV6_DEST_UNREACH, ICMPV6_NOROUTE, 0, skb->dev);
kfree_skb(skb);
return 0;
}
How about you ? Am I right ?
And I found another doubtable thing,
ipv6_routing_header() sends an ICMPv6 Parameter Problem message if the
extention header's length is odd value.
Then ICMPv6 Parameter Problem Message includes the pointer that indicates
the byte offset of errorneous field in a packet.
ipv6_routing_header() calculates the byte offset from the beginning of the
extention header.
In my opinion, ipv6_routing_header() must calculates the byte offset from
the beginning of the
IPv6 packet.
Is this right ?
bye.
next reply other threads:[~2003-05-06 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 10:18 Seong Moon [this message]
2003-05-09 11:34 ` IPv6 : ICMPV6_DEST_UNREACH type with ICMPV6_NOROUTE code Robert Olsson
2003-05-09 11:44 ` YOSHIFUJI Hideaki / 吉藤英明
2003-05-09 15:58 ` David S. 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='003e01c313b8$e55db620$28acfe81@seong' \
--to=seong@etri.re.kr \
--cc=netdev@oss.sgi.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).