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

fping should support IPv6 transparently #80

Closed
cranderson opened this issue Jul 29, 2015 · 2 comments
Closed

fping should support IPv6 transparently #80

cranderson opened this issue Jul 29, 2015 · 2 comments

Comments

@cranderson
Copy link
Contributor

I'm not sure how I feel about this, but since Fedora is bugging me about it:

https://bugzilla.redhat.com/show_bug.cgi?id=1221496

Description of problem:

The current system of using different software (fping vs fping6) for different versions of the IP stack is broken. As the IPv6 transition moves ahead its unreasonable to expect the user to do the IP address parsing and decide to use the appropriate tool for the address.

fping should work like traceroute, ssh or all other applications supporting both protocol versions by default.

How reproducible:
Always

Steps to Reproduce:

  1. fping 2a03:2880:20:4f06:face:b00c:0:1

Actual results:
2a03:2880:20:4f06:face:b00c:0:1 address not found

Expected results:
2a03:2880:20:4f06:face:b00c:0:1 is alive

@schweikert
Copy link
Owner

I agree... That's why I started a "unification" project a while ago:
#40
https://github.com/schweikert/fping/tree/feature/unify

Once the internal storage format is made the same, it should be easier to make fping support transparently both IPv4 and IPv6

@schweikert
Copy link
Owner

Implemented in develop branch and to be released with fping 3.16 (see also: fping-3.16-rc2)

schweikert added a commit that referenced this issue Jan 31, 2017
schweikert added a commit that referenced this issue Feb 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants