https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254212
--- Comment #5 from Jason A. Donenfeld <[email protected]> --- Woof, I see what you mean now. That problem also applies to v4 sockets too! Basically if there's no interface with an address in the family, then bind fails. We could check for ret==EADDRNOTAVAIL and just let things continue in that case, but the fact that this can happen for both v4 and v6 means the user might find themselves in a very confusing state. Returning a failing rc from the ioctl and maybe even warning in dmesg seems more useful. But I also wish there was a more robust solution for this too. Maybe we should go in the direction of allowing sockets to bind to 0.0.0.0 and ::/0 even in the case in which there's not yet an interface with an address in that addr family? That'd certainly make things easier. Thoughts? -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
