Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add IPv6 support #5

Open
Killeroo opened this issue Dec 7, 2016 · 2 comments
Open

Add IPv6 support #5

Killeroo opened this issue Dec 7, 2016 · 2 comments

Comments

@Killeroo
Copy link
Owner

Killeroo commented Dec 7, 2016

Can maybe be done by changing port type depending on IP Version ping property (that would need to be added)

@Killeroo
Copy link
Owner Author

Would require different socket running ICMPv6, which is already done depending on querried addressed. Forcev6 and Forcev4 both return correct addresses.

http://www.tcpipguide.com/free/t_ICMPCommonMessageFormatandDataEncapsulation.htm
Guide to ICMPv4 and v6 message structure. Both versions have a common message structure which are basically identical, only noticeable difference is type differenced. might require some modfication of orginal ICMP.cs (seems to be reading wrong parts of packet to get type and code info)

May also require new Ping_V6 class?

@Killeroo
Copy link
Owner Author

Killeroo commented Jun 4, 2017

@Killeroo Killeroo modified the milestones: v1.2.5, v1.3.0 Oct 1, 2017
@Killeroo Killeroo removed this from the v1.4.0 milestone Dec 2, 2019
boczar pushed a commit to boczar/PowerPing that referenced this issue Apr 22, 2021
@Killeroo Killeroo moved this to To do in PowerPing v2.0.0 May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: To do
Development

No branches or pull requests

1 participant