Search Issue Tracker
Fixed in 5.4.1
Votes
22
Found in
5.1.5f1
Issue ID
802395
Regression
No
UnityEngine.Ping does not work with ipv6 addresses
To Reproduce:
1. Open scene "Ping Test" in the attached project.
You need to be on an ipv6 network to test this ( can use if you're testing on ios/have a mac: https://developer.apple.com/library/mac/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/UnderstandingandPreparingfortheIPv6Transition/UnderstandingandPreparingfortheIPv6Transition.html#//apple_ref/doc/uid/TP40010220-CH213-SW1)
2. Run it and click on the "ping ipv6 address", observe that it fails with Ping.time = -1
(the address has ipv6 prefix https://tools.ietf.org/html/rfc6052, and can be pinged with ping6 util)
Tested on iOS and OSX
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Windows] The Unity import progress is not shown in the Windows taskbar
- Custom shader creation APIs are missing the AssetImportContext and thus can't handle includes correctly
- 2019.4: PackedMemorySnapshot: nativeObjects.gcHandleIndex contains -1 always
- [Hub] Project "Remove from list" option is behind notifications when selecting the most bottom project in the list
- [Android][Vulkan] Black Screen renders on devices with Adreno 640 and Mali GPU's
BillyMFT
Sep 07, 2016 09:28
yep, broken on 5.3.6
FundaySoftware
Aug 16, 2016 10:41
This is still not fixed in 5.4.0f3 even though this post suggests so. Please re-open.
ricardo_fb
Jun 29, 2016 04:40
Absolutely stuck because of this...
FundaySoftware
Jun 08, 2016 09:14
Yup, I'm not sure how 5.3.5 is fully IPv6 ready without the Ping class?
GameSpring
Jun 07, 2016 04:44
I have the same issue with Unity 5.3.5 even though it’s supposed to fully support IPv6.
Is there any update with this issue?