Michael Felt <aixto...@felt.demon.nl> added the comment: On 22/05/2019 10:43, Michael Felt wrote: > 'fe80::1%1' <> 'fe80::1' - ... I am not 'experienced' with IPv6 and scope.
>From what I have just read (again) - scope seems to be a way to indicate the interface used (e.g., eth0, or enp0s25) as a "number". Further, getsockname() (and getpeername()) seem to be more for after a fork(), or perhaps after a pthread_create(). What remains unclear is why would I ever care what the scopeid is. Is it because it is "shiney", does it add security (if so, how)? And, as this has been added - what breaks in Python when "scopeid" is not available? I am thinking, if adding a scopeid is a way to assign an IPv6 address to an interface - what is to prevent abuse? Why would I even want the same (link-local IP address on eth0 and eth1 at the same time? Assuming that it what it is making possible - the same IPv6/64 address on multiple interfaces and use scope ID to be more selective/aware. It this an alternative way to multiplex interfaces - now in the IP layer rather than in the LAN layer? If I understand why this is needed I may be able to come up with a way to "get it working" for the Python model of interfaces - although, probably not "fast". Regards, Michael ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue35545> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
