|
IPv6 Protocol Number 0x2b (IPv6-Route) Not Supported
![[us]](/s/countries/us.gif) Shadow Hawkins on Tuesday, 26 June 2012 20:00:04
Hi
I found this issue in Mobile IPv6 experiments. When the Mobile Node switches interface from "wlan0" (Wi-Fi) to "sixxs" (AYIYA tunnel), it sends Binding Update to Home Agent and Home Agent replies Bind Acknowledgement. The acknowledgement packet has been sent to Internet (confirmed by Wireshark) but the Mobile Node could not receive that packet.
I tried ping from Home Agent to Mobile Node and it worked perfectly. So I tested with the tool sendip which could generate arbitrary IPv6 packets. It turns out that all packets with protocol number 0x2b (IPv6-Route) in the Next Header field of IPv6 header are dropped inside the tunnel, while all other packets can successfully reach the other end of the tunnel. I wonder why it happens.
The details of one of the dropped packets is shown below (from Wireshark):
IPv6 Header:
Version: 6
Traffic class: 0
Flowlabel: 0
Payload length: 40
Next header: Ipv6 routing (0x2b)
Hop limit: 64
Source: 2001:470:1f07:20c::1
Destination: 2001:4830:1100:1ef::2 (the address of "sixxs" interface on Mobile Node)
Routing Header:
Type: Mobile IP (2)
Next header: Mobile IPv6 (0x87)
Length: 2 (24 bytes)
Type: Mobile IP (2)
Left Segments: 1
Home Address: 2001:4830:1100:1ef::2
Mobile IPv6 Header:
... (irrelevant)
IPv6 Protocol Number 0x2b (IPv6-Route) Not Supported
It turns out that all packets with protocol number 0x2b (IPv6-Route) in the Next Header field of IPv6 header are dropped inside the tunnel,
For SixXS I can state that we do not drop anything except what is specified in the FAQ.
This should thus travel through quite fine. Also, I do not see why any other network would be dropping this.
Source: 2001:470:1f07:20c::1 Destination: 2001:4830:1100:1ef::2 (the address of "sixxs" interface on Mobile Node)
Is the source address valid for that packet? What path does it take and which intermediates does it cross?
Do you receive any ICMPv6 packets back indicating issues with the packet?
IPv6 Protocol Number 0x2b (IPv6-Route) Not Supported
Shadow Hawkins on Wednesday, 27 June 2012 20:30:45
Thank you very much for your reply!
Yes, the source address is valid. I've tried other packets without the 0x2b ipv6-routing header, while other fields remain the same, and those packets can be transmitted successfully.
Actually, 2001:470:1f07:20c::1 is an IPv6 address provided by Hurricane Electric. If I traceroute6 from the source to the destination, it would go through:
traceroute to 2001:4830:1100:1ef::2 (2001:4830:1100:1ef::2) from 2001:470:1f06:20c::2, port 33434, from port 35929, 30 hops max, 60 byte packets
1 rsquirrel-1.tunnel.tserv4.nyc4.ipv6.he.net (2001:470:1f06:20c::1) 6.636 ms 5.273 ms 5.132 ms
2 gige-g3-8.core1.nyc4.he.net (2001:470:0:5d::1) 6.335 ms 1.554 ms 8.917 ms
3 10gigabitethernet2-3.core1.ash1.he.net (2001:470:0:36::1) 9.237 ms 15.964 ms 6.995 ms
4 ibr01-ve96.asbn01.occaid.net (2001:504:0:2:0:3:71:1) 7.455 ms 7.368 ms 7.116 ms
5 bbr01-p2-1.nwrk01.occaid.net (2001:4830:ff:f150::1) 14.536 ms 14.718 ms 13.689 ms
6 bbr01-g1-0.bstn01.occaid.net (2001:4830:ff:b101::2) 20.591 ms 20.387 ms 20.192 ms
7 dcr01-g0-1.bstn01.occaid.net (2001:4830:ff:b100::2) 20.785 ms 21.948 ms 20.643 ms
8 sixxs-ic-1139-bos.customer.occaid.net (2001:4830:e1:b::2) 21.394 ms 20.598 ms 21.104 ms
9 gw-496.bos-01.us.sixxs.net (2001:4830:1100:1ef::1) 20.546 ms 21.099 ms 20.862 ms
10 cl-496.bos-01.us.sixxs.net (2001:4830:1100:1ef::2) 115.745 ms 115.786 ms 105.314 ms
Also, I've received no ICMPv6 packets when the packet is lost.
IPv6 Protocol Number 0x2b (IPv6-Route) Not Supported
You might want to try using 'hping3 -0 -H 43 -T <destination>' that gives you a traceroute with protocol 43 packets, which should show which hop is dropping them.
IPv6 Protocol Number 0x2b (IPv6-Route) Not Supported
Hmmm which might not work as hping3 is not very able to do IPv6... ;(
IPv6 Protocol Number 0x2b (IPv6-Route) Not Supported
Shadow Hawkins on Wednesday, 27 June 2012 20:49:03
Yeah, I just thought of this method and have provided more information. I am using sendip which could do that :)
IPv6 Protocol Number 0x2b (IPv6-Route) Not Supported
Shadow Hawkins on Wednesday, 27 June 2012 20:47:24
I manually set the hop limit to trace the original packet, and found that the packet is lost without any icmpv6 returned at the hop from (3) 2001:470:0:36::1 to (4) 2001:504:0:2:0:3:71:1.
I further did the trace backforwards from destination to source, and found the packet lost at the hop from (6) 2001:4830:ff:b101::1 to (5) 2001:4830:ff:f150::2.
Any idea what would happen at these routers? Thanks!
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 27 June 2012 17:33:50
Posting is only allowed when you are