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

[Enhancement] Force v6/v4 for ping, trace etc #34

Open
FredNeuberger opened this issue Mar 9, 2018 · 6 comments
Open

[Enhancement] Force v6/v4 for ping, trace etc #34

FredNeuberger opened this issue Mar 9, 2018 · 6 comments
Assignees

Comments

@FredNeuberger
Copy link

Hey there,

Wouldn't it be nice to be able to copy paste paste a hostname and force the LG to use a specific IP version?

@gmazoyer
Copy link
Owner

It could be an interesting feature.

I believe that it could be a configuration option like supported_ip_version. But should it be global or per router? I can see a use case for per router but it would involve some Javascript to hide/show a new field in the form.

What do you guys think?

@pautiina
Copy link
Contributor

supported_ip_version - If this option is entered, then for per router

about copying the host address and inserting it is a good idea.

@martijn-schmidt
Copy link
Contributor

I actually discussed such a feature as a potential "long term wish list" item with my colleagues as well, but rather than forcing it to one IP version we figured we'd simply have the looking glass perform ping/traceroute for both address-families where A and AAAA records are available - much like the behaviour for the AS and regex lookup commands.

@gmazoyer
Copy link
Owner

That's actually not a bad idea. The current behavior is to use IPv6 if it is available (we are in 2018 for god sake). But using both IPv6 and IPv4 could be much simpler than implementing a supported_ip_version feature.

I do not exclude implementing a feature to force the IP version to use per router. I have been asked for this kind of features several times. But I guess we can do both of ideas. One should just be much faster and easier to implement.

@FredNeuberger
Copy link
Author

Yes, if both of them are getting processed, I guess thats almost enough. Can't think of any case where you'd want to enter a hostname and really force the address family and not get the other one as well.

@gmazoyer
Copy link
Owner

Let's do that this way then 👍

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

4 participants