Wireshark-bugs: [Wireshark-bugs] [Bug 3771] Teredo direct IPv6 connectivity test is not dissecte
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3771
Ivan Sy <ivan_jr@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #3481| |review_for_checkin?
Flag| |
--- Comment #1 from Ivan Sy <ivan_jr@xxxxxxxxx> 2009-08-07 16:00:12 PDT ---
Created an attachment (id=3481)
--> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=3481)
Patch to show teredo connectivity tests
see proposed patch
(fit for wireshark for now, will look into tshark later)
RFC 4380
Teredo: Tunneling IPv6 over UDP
through Network Address Translations (NATs)
...
5.2.9. Direct IPv6 Connectivity Test
...
When the client wants to send a packet to a native IPv6 node or a
6to4 node, it should check whether a valid peer entry already exists
for the IPv6 address of the destination. If this is not the case,
the client will pick a random number (a nonce) and format an ICMPv6
Echo Request message whose source is the local Teredo address, whose
destination is the address of the IPv6 node, and whose Data field is
set to the nonce. (It is recommended to use a random number at least
64 bits long.) The nonce value and the date at which the packet was
sent will be documented in a provisional peer entry for the IPV6
destination. The ICMPv6 packet will then be sent encapsulated in a
UDP packet destined to the Teredo server IPv4 address and to the
Teredo port. The rules of Section 5.2.3 specify how the reply to
this packet will be processed.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
