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

Fail to push to node through WebSocket with IPv6 addr #44

Open
gnain opened this issue May 27, 2014 · 3 comments
Open

Fail to push to node through WebSocket with IPv6 addr #44

gnain opened this issue May 27, 2014 · 3 comments
Labels

Comments

@gnain
Copy link
Member

gnain commented May 27, 2014

The node I use has an IPv6 address in the Network information.
The model is here: https://gist.github.com/gnain/4d285501fa45d2195f97
The editor shows an error message:

Failed to construct 'WebSocket': The URL 'ws://fe80:0:0:0:be5f:f4ff:fe21:74e2%252:9000/' is invalid.
  1. The IPv6 address does not seem to be good. Should probably be (removing the scope):
    ws://fe80:0:0:0:be5f:f4ff:fe21:74e2:9000/

  2. The node also has a IPv4 address. It should try to reach the node through all the addresses till one is successful.

@gnain gnain added the bug label May 27, 2014
@maxleiko
Copy link
Member

1): Yup gonna have a look at this, thanks

2): When you push to a node, the editor will use the selected NetworkProperty, it won't iterate over all NetworkProperties

@gnain
Copy link
Member Author

gnain commented May 27, 2014

For 2), I can understand that you start with the one selected. It is a good strategy for performances. But you should then iterate on other addresses till you find one suitable.
This is why we have multiple addresses.

@maxleiko
Copy link
Member

I've totally disabled IPv6 connection for now until I find a suitable solution for client-side WebSocket using IPv6. In the mean time, I've made the fix so that all Network Properties are tried on Push/Pull

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants