Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.6f1
Issue ID
1091392
Regression
No
[Windows] Ping class does not work with IPv6 numerical or AAAA addresses
How to reproduce:
1. Open attached project "PingTest.zip" and scene "Ping"
2. In Project window, open "TestPing" script
3. Change 25th line to your IPv4 address (to get your address, go to Start -> Run -> cmd -> ipconfig -> IPv4 Address)
4. Change 46th line to your IPv6 address (to get your address, go to Start -> Run -> cmd -> ipconfig -> IPv4 Address)
5. Save the script, Enter Play mode and after a few seconds observe Console window
Expected result: "Ping time is 0 (IPv4) and 0 (IPv6)" is printed
Actual result: "Ping time is 0 (IPv4) and 2147483647 (IPv6)" is printed
Reproducible with: 2017.4.16f1, 2018.3.0b12, 2019.1.0a9
Additional notes:
Reproducible on: Windows 10, Windows 7
Not reproducible on: Mac
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note:
As UNet is Deprecated we are closing this bug as part of cleaning-up the Bug List.