This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Ivan.Pozdeev
Recipients Ivan.Pozdeev
Date 2017-09-29.21:37:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1506721038.97.0.213398074469.issue31643@psf.upfronthosting.co.za>
In-reply-to
Content
Ethernet emulation for some devices like Android phones' tethering use all-zero MAC addresses (which is okay since they don't actually pass Ethernet frames to other NICs). This results in a node ID of 0 if I'm currently connected to the Net via such a device. Which fails range checks in the corresponding tests.

RFC 4122 doesn't actually have any prohibitions of using a node ID of 0. Neither does IEEE 802.3 (or rather, whatever info I gathered on it since the standard's text is not freely available) assign any special meaning to an all-zero MAC address.

The patch also corrects the check call in test_windll_getnode since the tested function always generates UUID from a MAC address.
History
Date User Action Args
2017-09-29 21:37:19Ivan.Pozdeevsetrecipients: + Ivan.Pozdeev
2017-09-29 21:37:18Ivan.Pozdeevsetmessageid: <1506721038.97.0.213398074469.issue31643@psf.upfronthosting.co.za>
2017-09-29 21:37:18Ivan.Pozdeevlinkissue31643 messages
2017-09-29 21:37:18Ivan.Pozdeevcreate