-
Notifications
You must be signed in to change notification settings - Fork 28.3k
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
unable to bind udp6 socket to a specific address #4274
Comments
What does strace show when you run that snippet? |
I'm on OSX. strace is not available. |
let me see if I can attach |
Running 'sudo dtruss -p
|
I just tried this on my linux box. Rather than
ipv4 works on my linux box, but ipv6 does not. |
oh, so I just tried binding to a non fe80 ipv6 address, and it seemed to work... |
also, it seems to work if I bind to |
it looks like for network peers to contact me on the fe80 address, they need to specify THEIR interface to contact me on, ex: |
ok, my linux buddies just gave me a refresher on link local addresses: https://en.wikipedia.org/wiki/Link-local_address It seems that the sender will have to specify their networking interface and the receiver also has to specify their listening interface. There may not be any bugs here. Let me think about this over lunch, and when I get back, I'll probably end up closing this bug. |
I would mark this bug as invalid. |
throws
Error: bind EADDRNOTAVAIL fe80::e46a:6cff:fe68:a76a
but works for ipv4 addresses listed fromos.networkInterfaces()
.https://stackoverflow.com/questions/34259279/node-js-cant-bind-a-udp6-socket-to-a-specific-address
The text was updated successfully, but these errors were encountered: