tytan652
tytan652
@WizardCM From my point of view, there is no need to force the user to choose between IPv4 and IPv6 for interface binding. Edit: under Linux
@WizardCM And about the Bug fix label, like I demonstrated, it's not a bug because `ping` show the same behavior. If I bind an address of `enp4s0` it will work...
~~This functionality could work on macOS and FreeBSD systems, if `SO_BINDTODEVICE` analogue `IP_SENDIF` is one day implemented. So I'm asking, should I keep the future possible implementation of interface binding...
@WizardCM On my computer, binding a address not "owned" by my "default" interface will cause this issue, but if I bind an interface and bind one of his address it...
The issue here seems that on Linux system, the gateway chosen for the socket is the one of the "default" interface (the one with the lowest metrics), it doesn't matter...
@WizardCM Can you put Linux tag on this PR ? And also Seeking testers if you think it's worth it (only me tested it).
Thank you Jim (@jp9000)
~~Switch to draft, waiting #5143 to be merged. The network UI change may need some change.~~
> I say that using `SO_BINDTODEVICE` is unnecessary because most implementations of interface binding that I see for streaming purposes bind only to an IP address. I'm a nerd for...
This PR is drafted, the plan in the future is to reintroduce service and output property view thanks to the RFC39 and then rework this PR to be only in...