Nick Coghlan added the comment:
The Interface classes are actually designed to cover any association of an IP
address with a specific network, not just host interface addresses. We knew it
was a slight misnomer when we chose it, but network and broadcast addresses
weren't considered special en
Вячеслав added the comment:
Probably worth noting that network is unnumbered in ip_network and ip_interface
functions. Based on this flag to decide whether there is a possibility to use
the network address and broadcast address in the network
What do you think about this?
--
_
Вячеслав added the comment:
These addresses are used by each interface in the network and they can not be
the address of the interface, of course have the technology ip-unnumbered. But
it's more a special case.
but I was confused behavior:
>>> set(ip_network(u'192.168.1.0/29'))
set([IPv4Addre
R. David Murray added the comment:
Well, it can be the network, even though it isn't typically (and some devices
don't support it...I'm pretty sure I remember doing it on a Cisco, though I
wouldn't swear to it without testing :). Same is true for broadcast, though
that would be *really* quest
New submission from Вячеслав:
ip_interface can't be network or broadcast address. Probably should throw an
exception in such cases
>>> ip_interface(u'192.168.1.0/25')
IPv4Interface(u'192.168.1.0/25')
>>> ip_interface(u'192.168.1.127/25')
IPv4Interface(u'192.168.1.127/25')
--
component
