My favorites | Sign in
Project Logo
Project Home
  
Downloads
  
Wiki
  
Issues
  
Source
    
Summary | Updates | People
Details: Show all Hide all

Last 30 days

  • Dec 02, 2009
    r340 (Added patch from S. Nordhausen and implemented suggestions. ) committed by drkjam   -   Added patch from S. Nordhausen and implemented suggestions.
    Added patch from S. Nordhausen and implemented suggestions.
  • Nov 26, 2009
    issue 51 (__iter__ operator for IPv6 network) Status changed by drkjam   -   Using list() on a /64 IPv6 network wouldn't be wise as it would chew up all the memory on your system and/or take a *very* long time to complete. When dealing with networks containing more than sys.maxint (2^31) addresses use the .size property (as suggested by Exception message) to find out how many addresses are within a given range and the iterator protocol to access to all addresses within it in an in an efficient way, the simplest being :- >>> for ip in IPNetwork("fd91:f405:c161:6f7a::/64"): ... # do something with your address OR something like :- >>> it = iter(IPNetwork("fd91:f405:c161:6f7a::/64")) >>> ip = it.next() IPAddress("fd91:f405:c161:6f7a::") HTH
    Status: WontFix
    Using list() on a /64 IPv6 network wouldn't be wise as it would chew up all the memory on your system and/or take a *very* long time to complete. When dealing with networks containing more than sys.maxint (2^31) addresses use the .size property (as suggested by Exception message) to find out how many addresses are within a given range and the iterator protocol to access to all addresses within it in an in an efficient way, the simplest being :- >>> for ip in IPNetwork("fd91:f405:c161:6f7a::/64"): ... # do something with your address OR something like :- >>> it = iter(IPNetwork("fd91:f405:c161:6f7a::/64")) >>> ip = it.next() IPAddress("fd91:f405:c161:6f7a::") HTH
    Status: WontFix
  • Nov 26, 2009
    issue 51 (__iter__ operator for IPv6 network) reported by pgurumur   -   Python 2.5.4 (r254:67916, Jul 3 2009, 22:17:21) [GCC 3.3.5 (propolice)] on openbsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from netaddr import IPNetwork >>> test = IPNetwork("fd91:f405:c161:6f7a::/64") >>> print test fd91:f405:c161:6f7a::/64 >>> list(test) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/local/lib/python2.5/site-packages/netaddr-0.7.3-py2.5.egg/netaddr/ip/__init__.py", line 931, in __len__ "IP addresses! Use the .size property instead." % _sys.maxint) IndexError: range contains more than 9223372036854775807 (sys.maxint) IP addresses! Use the .size property instead. >>> How would I go about getting a list? or is it not possible?
    Python 2.5.4 (r254:67916, Jul 3 2009, 22:17:21) [GCC 3.3.5 (propolice)] on openbsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from netaddr import IPNetwork >>> test = IPNetwork("fd91:f405:c161:6f7a::/64") >>> print test fd91:f405:c161:6f7a::/64 >>> list(test) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/local/lib/python2.5/site-packages/netaddr-0.7.3-py2.5.egg/netaddr/ip/__init__.py", line 931, in __len__ "IP addresses! Use the .size property instead." % _sys.maxint) IndexError: range contains more than 9223372036854775807 (sys.maxint) IP addresses! Use the .size property instead. >>> How would I go about getting a list? or is it not possible?
  • Nov 26, 2009
    issue 50 (CIDR block parsing) Status changed by drkjam   -   The constructor interface is little quirky and needs updating. I'll have a look at modifying this behaviour in future versions to make it less confusing. As a workaround, set implicit_prefix=True to obtain the result you need :- >>> netaddr.IPNetwork('10/8', True) IPNetwork('10.0.0.0/8')
    Status: Accepted
    The constructor interface is little quirky and needs updating. I'll have a look at modifying this behaviour in future versions to make it less confusing. As a workaround, set implicit_prefix=True to obtain the result you need :- >>> netaddr.IPNetwork('10/8', True) IPNetwork('10.0.0.0/8')
    Status: Accepted
  • Nov 25, 2009
    issue 50 (CIDR block parsing) commented on by pgurumur   -   I am using python 2.5, on OpenBSD 4.6 amd64 bit platform. Python 2.5.4 (r254:67916, Jul 3 2009, 22:17:21) [GCC 3.3.5 (propolice)] on openbsd4 Type "help", "copyright", "credits" or "license" for more information. >>> import platform >>> platform.python_version() '2.5.4' >>> platform.python_compiler() 'GCC 3.3.5 (propolice)' >>> platform.uname() ('OpenBSD', 'andromeda.kashyapa.net', '4.6', 'GENERIC.MP#3', 'amd64', 'AMD Athlon(tm) 64 X2 Dual Core Processor 5200+')
    I am using python 2.5, on OpenBSD 4.6 amd64 bit platform. Python 2.5.4 (r254:67916, Jul 3 2009, 22:17:21) [GCC 3.3.5 (propolice)] on openbsd4 Type "help", "copyright", "credits" or "license" for more information. >>> import platform >>> platform.python_version() '2.5.4' >>> platform.python_compiler() 'GCC 3.3.5 (propolice)' >>> platform.uname() ('OpenBSD', 'andromeda.kashyapa.net', '4.6', 'GENERIC.MP#3', 'amd64', 'AMD Athlon(tm) 64 X2 Dual Core Processor 5200+')
  • Nov 25, 2009
    issue 50 (CIDR block parsing) reported by pgurumur   -   >>> import netaddr >>> netaddr.__version__ '0.7.3' >>> from netaddr import IPNetwork >>> test = IPNetwork("10.108.10/24") >>> print test 10.108.0.10/24 >>> test1 = IPNetwork("10/8") >>> print test1 0.0.0.10/8 >>> Is this expected? it is kind of normal for network engineers to not write the trailing zeroes, although may not be accurate.
    >>> import netaddr >>> netaddr.__version__ '0.7.3' >>> from netaddr import IPNetwork >>> test = IPNetwork("10.108.10/24") >>> print test 10.108.0.10/24 >>> test1 = IPNetwork("10/8") >>> print test1 0.0.0.10/8 >>> Is this expected? it is kind of normal for network engineers to not write the trailing zeroes, although may not be accurate.
  • Nov 11, 2009
    issue 49 (Incorrect IP range recognition on IPs with leading zeros) commented on by ipsecpl   -   >>> import netaddr >>> netaddr.strategy.ipv4.OPT_IMPORTS True
    >>> import netaddr >>> netaddr.strategy.ipv4.OPT_IMPORTS True
  • Nov 11, 2009
    issue 49 (Incorrect IP range recognition on IPs with leading zeros) commented on by drkjam   -   I'm not able to replicate your error and get a completely different error :- >>> import netaddr >>> netaddr.__version__ 0.7.3 >>> r1 = '208.049.164.000' >>> r2 = '208.050.066.255' >>> netaddr.IPRange(r1, r2) Traceback (most recent call last): File "<string>", line 1, in ? File "/usr/local/lib/python2.4/site-packages/netaddr/ip/__init__.py", line 1163, in __init__ self._start = IPAddress(start) File "/usr/local/lib/python2.4/site-packages/netaddr/ip/__init__.py", line 262, in __init__ self.value = addr File "/usr/local/lib/python2.4/site-packages/netaddr/ip/__init__.py", line 290, in _set_value raise AddrFormatError('failed to detect IP version: %r' netaddr.core.AddrFormatError: failed to detect IP version: '208.049.164.000' This is both under Linux and Windows. From your output I take it you are using OpenBSD? Can you run the following and specify what the value of the OPT_IMPORTS variable is in your interpreter :- >>> import netaddr >>> netaddr.strategy.ipv4.OPT_IMPORTS
    I'm not able to replicate your error and get a completely different error :- >>> import netaddr >>> netaddr.__version__ 0.7.3 >>> r1 = '208.049.164.000' >>> r2 = '208.050.066.255' >>> netaddr.IPRange(r1, r2) Traceback (most recent call last): File "<string>", line 1, in ? File "/usr/local/lib/python2.4/site-packages/netaddr/ip/__init__.py", line 1163, in __init__ self._start = IPAddress(start) File "/usr/local/lib/python2.4/site-packages/netaddr/ip/__init__.py", line 262, in __init__ self.value = addr File "/usr/local/lib/python2.4/site-packages/netaddr/ip/__init__.py", line 290, in _set_value raise AddrFormatError('failed to detect IP version: %r' netaddr.core.AddrFormatError: failed to detect IP version: '208.049.164.000' This is both under Linux and Windows. From your output I take it you are using OpenBSD? Can you run the following and specify what the value of the OPT_IMPORTS variable is in your interpreter :- >>> import netaddr >>> netaddr.strategy.ipv4.OPT_IMPORTS
  • Nov 11, 2009
    issue 49 (Incorrect IP range recognition on IPs with leading zeros) commented on by ipsecpl   -   In 0.7.3 the message is different: Traceback (most recent call last): File "iblocklist2pf.py", line 16, in <module> iprange = netaddr.IPRange(r1,r2) File "/usr/local/lib/python2.5/site-packages/netaddr/ip/__init__.py", line 1167, in __init__ raise AddrFormatError('lower bound IP greater than upper bound!') netaddr.core.AddrFormatError: lower bound IP greater than upper bound!
    In 0.7.3 the message is different: Traceback (most recent call last): File "iblocklist2pf.py", line 16, in <module> iprange = netaddr.IPRange(r1,r2) File "/usr/local/lib/python2.5/site-packages/netaddr/ip/__init__.py", line 1167, in __init__ raise AddrFormatError('lower bound IP greater than upper bound!') netaddr.core.AddrFormatError: lower bound IP greater than upper bound!
  • Nov 11, 2009
    issue 49 (Incorrect IP range recognition on IPs with leading zeros) commented on by ipsecpl   -   BTW it's netaddr version 0.6.3
    BTW it's netaddr version 0.6.3
  • Nov 11, 2009
    issue 49 (Incorrect IP range recognition on IPs with leading zeros) reported by ipsecpl   -   Python 2.5.2 (r252:60911, Aug 12 2008, 11:14:20) [GCC 3.3.5 (propolice)] on openbsd4 Type "help", "copyright", "credits" or "license" for more information. >>> import netaddr >>> r1='208.049.164.000' >>> r2='208.050.066.255' >>> netaddr.IPRange(r1,r2) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/local/lib/python2.5/site-packages/netaddr/address.py", line 1122, in __init__ raise IndexError('start address is greater than stop address!') IndexError: start address is greater than stop address!
    Python 2.5.2 (r252:60911, Aug 12 2008, 11:14:20) [GCC 3.3.5 (propolice)] on openbsd4 Type "help", "copyright", "credits" or "license" for more information. >>> import netaddr >>> r1='208.049.164.000' >>> r2='208.050.066.255' >>> netaddr.IPRange(r1,r2) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/local/lib/python2.5/site-packages/netaddr/address.py", line 1122, in __init__ raise IndexError('start address is greater than stop address!') IndexError: start address is greater than stop address!

Earlier this year

  • Oct 02, 2009
    issue 48 (network recognition) commented on by peter.moody   -   ah, intersection was what I was thinking of. (sorted, for cleanliness) In [18]: sorted(set.intersection(set(addr1.supernet()), set(adr2.supernet()))) Out[18]: [IPNetwork('0.0.0.0/0'), IPNetwork('128.0.0.0/1'), IPNetwork('192.0.0.0/2'), IPNetwork('192.0.0.0/3'), IPNetwork('192.0.0.0/4'), IPNetwork('192.0.0.0/5'), IPNetwork('192.0.0.0/6'), IPNetwork('192.0.0.0/7'), IPNetwork('192.0.0.0/8'), IPNetwork('192.128.0.0/9'), IPNetwork('192.128.0.0/10'), IPNetwork('192.160.0.0/11'), IPNetwork('192.160.0.0/12'), IPNetwork('192.168.0.0/13'), IPNetwork('192.168.0.0/14'), IPNetwork('192.168.0.0/15'), IPNetwork('192.168.0.0/16'), IPNetwork('192.168.0.0/17'), IPNetwork('192.168.0.0/18'), IPNetwork('192.168.0.0/19'), IPNetwork('192.168.0.0/20'), IPNetwork('192.168.0.0/21'), IPNetwork('192.168.0.0/22'), IPNetwork('192.168.0.0/23')]
    ah, intersection was what I was thinking of. (sorted, for cleanliness) In [18]: sorted(set.intersection(set(addr1.supernet()), set(adr2.supernet()))) Out[18]: [IPNetwork('0.0.0.0/0'), IPNetwork('128.0.0.0/1'), IPNetwork('192.0.0.0/2'), IPNetwork('192.0.0.0/3'), IPNetwork('192.0.0.0/4'), IPNetwork('192.0.0.0/5'), IPNetwork('192.0.0.0/6'), IPNetwork('192.0.0.0/7'), IPNetwork('192.0.0.0/8'), IPNetwork('192.128.0.0/9'), IPNetwork('192.128.0.0/10'), IPNetwork('192.160.0.0/11'), IPNetwork('192.160.0.0/12'), IPNetwork('192.168.0.0/13'), IPNetwork('192.168.0.0/14'), IPNetwork('192.168.0.0/15'), IPNetwork('192.168.0.0/16'), IPNetwork('192.168.0.0/17'), IPNetwork('192.168.0.0/18'), IPNetwork('192.168.0.0/19'), IPNetwork('192.168.0.0/20'), IPNetwork('192.168.0.0/21'), IPNetwork('192.168.0.0/22'), IPNetwork('192.168.0.0/23')]
  • Oct 02, 2009
    issue 48 (network recognition) commented on by peter.moody   -   hm, I take that back. that doesn't seem right. nevermind.
    hm, I take that back. that doesn't seem right. nevermind.
  • Oct 02, 2009
    issue 48 (network recognition) commented on by peter.moody   -   you could find the supernets of each and the find the union of those sets. something like In [12]: addr1 = netaddr.IPNetwork('192.168.0.1') In [13]: addr2 = netaddr.IPNetwork('192.168.1.6') In [14]: set.union(set(addr1.supernet()), set(addr2.supernet())) Out[15]: set([IPNetwork('192.128.0.0/9'), IPNetwork('192.0.0.0/6'), IPNetwork('192.128.0.0/10'), IPNetwork('192.0.0.0/5'), IPNetwork('192.168.0.0/16'), IPNetwork('192.168.1.0/29'), IPNetwork('192.168.0.0/26'), IPNetwork('192.168.0.0/22'), IPNetwork('192.168.0.0/31'), IPNetwork('192.168.0.0/18'), IPNetwork('192.168.0.0/14'), IPNetwork('192.168.0.0/29'), IPNetwork('128.0.0.0/1'), IPNetwork('192.168.0.0/17'), IPNetwork('192.0.0.0/7'), IPNetwork('192.160.0.0/11'), IPNetwork('192.168.1.0/27'), IPNetwork('192.168.0.0/15'), IPNetwork('192.168.0.0/20'), IPNetwork('192.168.1.6/31'), IPNetwork('192.160.0.0/12'), IPNetwork('192.168.1.0/24'), IPNetwork('192.168.0.0/25'), IPNetwork('192.0.0.0/8'), IPNetwork('192.168.1.4/30'), IPNetwork('192.0.0.0/2'), IPNetwork('0.0.0.0/0'), IPNetwork('192.168.0.0/24'), IPNetwork('192.168.0.0/23'), IPNetwork('192.168.0.0/28'), IPNetwork('192.0.0.0/4'), IPNetwork('192.168.1.0/28'), IPNetwork('192.168.0.0/19'), IPNetwork('192.168.0.0/30'), IPNetwork('192.168.1.0/25'), IPNetwork('192.0.0.0/3'), IPNetwork('192.168.0.0/13'), IPNetwork('192.168.0.0/27'), IPNetwork('192.168.0.0/21'), IPNetwork('192.168.1.0/26')])
    you could find the supernets of each and the find the union of those sets. something like In [12]: addr1 = netaddr.IPNetwork('192.168.0.1') In [13]: addr2 = netaddr.IPNetwork('192.168.1.6') In [14]: set.union(set(addr1.supernet()), set(addr2.supernet())) Out[15]: set([IPNetwork('192.128.0.0/9'), IPNetwork('192.0.0.0/6'), IPNetwork('192.128.0.0/10'), IPNetwork('192.0.0.0/5'), IPNetwork('192.168.0.0/16'), IPNetwork('192.168.1.0/29'), IPNetwork('192.168.0.0/26'), IPNetwork('192.168.0.0/22'), IPNetwork('192.168.0.0/31'), IPNetwork('192.168.0.0/18'), IPNetwork('192.168.0.0/14'), IPNetwork('192.168.0.0/29'), IPNetwork('128.0.0.0/1'), IPNetwork('192.168.0.0/17'), IPNetwork('192.0.0.0/7'), IPNetwork('192.160.0.0/11'), IPNetwork('192.168.1.0/27'), IPNetwork('192.168.0.0/15'), IPNetwork('192.168.0.0/20'), IPNetwork('192.168.1.6/31'), IPNetwork('192.160.0.0/12'), IPNetwork('192.168.1.0/24'), IPNetwork('192.168.0.0/25'), IPNetwork('192.0.0.0/8'), IPNetwork('192.168.1.4/30'), IPNetwork('192.0.0.0/2'), IPNetwork('0.0.0.0/0'), IPNetwork('192.168.0.0/24'), IPNetwork('192.168.0.0/23'), IPNetwork('192.168.0.0/28'), IPNetwork('192.0.0.0/4'), IPNetwork('192.168.1.0/28'), IPNetwork('192.168.0.0/19'), IPNetwork('192.168.0.0/30'), IPNetwork('192.168.1.0/25'), IPNetwork('192.0.0.0/3'), IPNetwork('192.168.0.0/13'), IPNetwork('192.168.0.0/27'), IPNetwork('192.168.0.0/21'), IPNetwork('192.168.1.0/26')])
  • Oct 02, 2009
    issue 48 (network recognition) reported by thelonelywolf   -   Hi before all thanks for your commit #337 :P Sorry for the question, i've tried to search within documentation without success, however, let's say we have 2 (or more) different ip address: 192.168.0.1 and 192.168.1.6 Is there any way/method that return something like: "this 2 address belongs to two different networks"? Thanks for your attention :)
    Hi before all thanks for your commit #337 :P Sorry for the question, i've tried to search within documentation without success, however, let's say we have 2 (or more) different ip address: 192.168.0.1 and 192.168.1.6 Is there any way/method that return something like: "this 2 address belongs to two different networks"? Thanks for your attention :)
  • Sep 14, 2009
    issue 47 (IPNetwork cannot be evaluated as a boolean when it has a lar...) commented on by garron.moore   -   Wow, quick turnaround. Thanks!
    Wow, quick turnaround. Thanks!
  • Sep 14, 2009
    r339 (Release tag for netaddr 0.7.3 ) committed by drkjam   -   Release tag for netaddr 0.7.3
    Release tag for netaddr 0.7.3
  • Sep 14, 2009
    CHANGELOG Wiki page edited by drkjam   -   Revision r338 Edited wiki page through web user interface.
    Revision r338 Edited wiki page through web user interface.
  • Sep 14, 2009
    netaddr-0.7.3.tar.gz (netaddr release 0.7.3 (tarball)) file uploaded by drkjam   -  
    Labels: Featured OpSys-All Type-Source
    Labels: Featured OpSys-All Type-Source
  • Sep 14, 2009
    netaddr-0.7.3.zip (netaddr release 0.7.3 (zip archive)) file uploaded by drkjam   -  
    Labels: Featured OpSys-All Type-Archive
    Labels: Featured OpSys-All Type-Archive
  • Sep 14, 2009
    netaddr-0.7.3.win32.exe (netaddr release 0.7.3 (MS Windows Installer)) file uploaded by drkjam   -  
    Labels: Featured OpSys-Windows Type-Installer
    Labels: Featured OpSys-Windows Type-Installer
  • Sep 14, 2009
    issue 47 (IPNetwork cannot be evaluated as a boolean when it has a lar...) Status changed by drkjam   -  
    Status: Fixed
    Status: Fixed
  • Sep 14, 2009
    issue 47 (IPNetwork cannot be evaluated as a boolean when it has a lar...) commented on by drkjam   -   Fixed in branches/rel-0.7.x, revision 337.
    Fixed in branches/rel-0.7.x, revision 337.
  • Sep 14, 2009
    issue 47 (IPNetwork cannot be evaluated as a boolean when it has a lar...) commented on by drkjam   -   Fixed in branches/rel-0.7.x, revision 337.
    Fixed in branches/rel-0.7.x, revision 337.
  • Sep 14, 2009
    issue 46 (Question about IPv4 ranges) Status changed by drkjam   -   Fixed in branches/rel-0.7.x, revision 337.
    Status: Fixed
    Fixed in branches/rel-0.7.x, revision 337.
    Status: Fixed
  • Sep 14, 2009
    r337 (Release 0.7.3. ) committed by drkjam   -   Release 0.7.3.
    Release 0.7.3.
  • Sep 14, 2009
    issue 47 (IPNetwork cannot be evaluated as a boolean when it has a lar...) Status changed by drkjam   -   Thanks. I'll take a look.
    Status: Accepted
    Thanks. I'll take a look.
    Status: Accepted
  • Sep 14, 2009
    issue 47 (IPNetwork cannot be evaluated as a boolean when it has a lar...) Status changed by drkjam   -   Thanks. I'll take a look.
    Status: Accepted
    Thanks. I'll take a look.
    Status: Accepted
  • Sep 14, 2009
    issue 47 (IPNetwork cannot be evaluated as a boolean when it has a lar...) reported by garron.moore   -   What steps will reproduce the problem? 1. if IPNetwork('2002::/64'): pass What is the expected output? What do you see instead? The expected output is nothing but I get a traceback. Since IPNetwork does not implement __nonzero__(), the if statement results in the __len__() method getting called, which for a network with this many IP addresses, raises IndexError. What version of the product are you using? On what operating system? 0.7.2 Please provide any additional information below.
    What steps will reproduce the problem? 1. if IPNetwork('2002::/64'): pass What is the expected output? What do you see instead? The expected output is nothing but I get a traceback. Since IPNetwork does not implement __nonzero__(), the if statement results in the __len__() method getting called, which for a network with this many IP addresses, raises IndexError. What version of the product are you using? On what operating system? 0.7.2 Please provide any additional information below.
  • Sep 01, 2009
    issue 46 (Question about IPv4 ranges) Status changed by drkjam   -   Glad you are liking netaddr ;-) Sounds interesting. I'll take a look into the nmap range syntax and see how we can best work in support for it.
    Status: Accepted
    Glad you are liking netaddr ;-) Sounds interesting. I'll take a look into the nmap range syntax and see how we can best work in support for it.
    Status: Accepted
  • Sep 01, 2009
    issue 46 (Question about IPv4 ranges) reported by thelonelywolf   -   Hi, netaddr is really wonderful! :P I was reading documentation but i didn't find anything about a specific kind of ranges..well, it is possible to use netaddr to manage ipv4 ranges like: '192.168.0.1-254' OR '192.168.1-254.1-254' ? I saw IPGlob and it works perfectly, however, do you think it will be possibile to use this kind of notation (eg. nmap ip range style)? Let's say i am reading an input text file which contain: 192.168.1-2.1.254 can we manage it with netaddr? What steps will reproduce the problem? 1. >>> IPAddress('192.168.0.1') IPAddress('192.168.0.1') >>> IPAddress('192.168.0.1-4') Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python2.5/site-packages/netaddr-0.7.2-py2.5.egg/netaddr/ip/__init__.py", line 262, in __init__ self.value = addr File "/usr/lib/python2.5/site-packages/netaddr-0.7.2-py2.5.egg/netaddr/ip/__init__.py", line 291, in _set_value % value) netaddr.core.AddrFormatError: failed to detect IP version: '192.168.0.1-4' What is the expected output? What do you see instead? I beg your pardon if this feature is already available :) What version of the product are you using? On what operating system? 0.7.2 on Ubuntu Intrepid 64bit Please provide any additional information below. --- Thanks for your attention
    Hi, netaddr is really wonderful! :P I was reading documentation but i didn't find anything about a specific kind of ranges..well, it is possible to use netaddr to manage ipv4 ranges like: '192.168.0.1-254' OR '192.168.1-254.1-254' ? I saw IPGlob and it works perfectly, however, do you think it will be possibile to use this kind of notation (eg. nmap ip range style)? Let's say i am reading an input text file which contain: 192.168.1-2.1.254 can we manage it with netaddr? What steps will reproduce the problem? 1. >>> IPAddress('192.168.0.1') IPAddress('192.168.0.1') >>> IPAddress('192.168.0.1-4') Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python2.5/site-packages/netaddr-0.7.2-py2.5.egg/netaddr/ip/__init__.py", line 262, in __init__ self.value = addr File "/usr/lib/python2.5/site-packages/netaddr-0.7.2-py2.5.egg/netaddr/ip/__init__.py", line 291, in _set_value % value) netaddr.core.AddrFormatError: failed to detect IP version: '192.168.0.1-4' What is the expected output? What do you see instead? I beg your pardon if this feature is already available :) What version of the product are you using? On what operating system? 0.7.2 on Ubuntu Intrepid 64bit Please provide any additional information below. --- Thanks for your attention
  • Aug 26, 2009
    issue 45 (IPNetwork(<int>|<long>) fails) Status changed by drkjam   -   Thanks for adding a ticket to track this. I'll take a look into it.
    Status: Accepted
    Thanks for adding a ticket to track this. I'll take a look into it.
    Status: Accepted
  • Aug 26, 2009
    issue 45 (IPNetwork(<int>|<long>) fails) reported by peter.moody   -   What steps will reproduce the problem? >>> netaddr.IPNetwork(1) What is the expected output? something along the lines of IPNetwork('0.0.0.1/32') What do you see instead? >>> netaddr.IPNetwork(1) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "./netaddr/ip/__init__.py", line 632, in __init__ prefix, suffix = addr.split('/') AttributeError: 'int' object has no attribute 'split What version of the product are you using? On what operating system? exp_0.7.x_ip_only I think you call this netaddr.ip.lite Please provide any additional information below. I posted this on the ipaddr pep, I figured it would only make sense for me to give you a issue with which to track it.
    What steps will reproduce the problem? >>> netaddr.IPNetwork(1) What is the expected output? something along the lines of IPNetwork('0.0.0.1/32') What do you see instead? >>> netaddr.IPNetwork(1) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "./netaddr/ip/__init__.py", line 632, in __init__ prefix, suffix = addr.split('/') AttributeError: 'int' object has no attribute 'split What version of the product are you using? On what operating system? exp_0.7.x_ip_only I think you call this netaddr.ip.lite Please provide any additional information below. I posted this on the ipaddr pep, I figured it would only make sense for me to give you a issue with which to track it.
  • Aug 26, 2009
    NetBlockOperationsDraft (Draft: Operations on Network Blocks) Wiki page edited by drkjam   -   Revision r336 Edited wiki page through web user interface.
    Revision r336 Edited wiki page through web user interface.
  • Aug 26, 2009
    ReleasePolicy (Details on the netaddr release policy) Wiki page edited by drkjam   -   Revision r335 Edited wiki page through web user interface.
    Revision r335 Edited wiki page through web user interface.
  • Aug 26, 2009
    NetAddrAPI (netaddr API documentation) Wiki page edited by drkjam   -   Revision r334 Edited wiki page through web user interface.
    Revision r334 Edited wiki page through web user interface.
  • Aug 26, 2009
    WikiSideBar Wiki page edited by drkjam   -   Revision r333 Edited wiki page through web user interface.
    Revision r333 Edited wiki page through web user interface.
  • Aug 26, 2009
    PEP3144 (Analysis and Feedback on PEP 3144.) Wiki page added by drkjam   -   Revision r332 Created wiki page through web user interface.
    Revision r332 Created wiki page through web user interface.
  • Aug 26, 2009
    issue 44 (int/long type error) Status changed by drkjam   -   This issue was closed by revision r331.
    Status: Fixed
    This issue was closed by revision r331.
    Status: Fixed
  • Aug 26, 2009
    r331 (Fixed Issue 44. ) committed by drkjam   -   Fixed Issue 44 .
    Fixed Issue 44 .
  • Aug 26, 2009
    issue 44 (int/long type error) Status changed by drkjam   -   Thanks for raising this. I see what's happening and its an easy fix. These errors are all related to the way the new style unit test code compares generated vs expected results. There aren't actually any bugs in the code itself (phew).
    Status: Accepted
    Thanks for raising this. I see what's happening and its an easy fix. These errors are all related to the way the new style unit test code compares generated vs expected results. There aren't actually any bugs in the code itself (phew).
    Status: Accepted
  • Aug 26, 2009
    issue 44 (int/long type error) reported by yzlin.freebsd   -   What is the expected output? What do you see instead? ====================================================================== FAIL: Doctest: tutorial.txt ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/local/lib/python2.6/doctest.py", line 2145, in runTest raise self.failureException(self.format_failure(new.getvalue())) AssertionError: Failed doctest test for tutorial.txt File "/usr/local/tinderbox/portstrees/FreeBSD/ports/net/py-netaddr/work/netaddr-0.7.2/netaddr/tests/ip/tutorial.txt", line 0 ---------------------------------------------------------------------- File "/usr/local/tinderbox/portstrees/FreeBSD/ports/net/py-netaddr/work/netaddr-0.7.2/netaddr/tests/ip/tutorial.txt", line 69, in tutorial.txt Failed example: int(ip) Expected: 3221225985L Got: 3221225985 ====================================================================== FAIL: Doctest: eui64.txt ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/local/lib/python2.6/doctest.py", line 2145, in runTest raise self.failureException(self.format_failure(new.getvalue())) AssertionError: Failed doctest test for eui64.txt File "/usr/local/tinderbox/portstrees/FreeBSD/ports/net/py-netaddr/work/netaddr-0.7.2/netaddr/tests/eui/eui64.txt", line 0 ---------------------------------------------------------------------- File "/usr/local/tinderbox/portstrees/FreeBSD/ports/net/py-netaddr/work/netaddr-0.7.2/netaddr/tests/eui/eui64.txt", line 23, in eui64.txt Failed example: int(eui) Expected: 7731765737772285L Got: 7731765737772285 ====================================================================== FAIL: Doctest: tutorial.txt ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/local/lib/python2.6/doctest.py", line 2145, in runTest raise self.failureException(self.format_failure(new.getvalue())) AssertionError: Failed doctest test for tutorial.txt File "/usr/local/tinderbox/portstrees/FreeBSD/ports/net/py-netaddr/work/netaddr-0.7.2/netaddr/tests/eui/tutorial.txt", line 0 ---------------------------------------------------------------------- File "/usr/local/tinderbox/portstrees/FreeBSD/ports/net/py-netaddr/work/netaddr-0.7.2/netaddr/tests/eui/tutorial.txt", line 57, in tutorial.txt Failed example: int(mac) Expected: 117965411581L Got: 117965411581 ---------------------------------------------------------------------- File "/usr/local/tinderbox/portstrees/FreeBSD/ports/net/py-netaddr/work/netaddr-0.7.2/netaddr/tests/eui/tutorial.txt", line 243, in tutorial.txt Failed example: iab.registration() Expected: {'address': ['2101 Superior Avenue', 'Cleveland OH 44114', 'UNITED STATES'], 'iab': '00-50-C2-00-00-00', 'idx': 84680704L, 'offset': 68, 'org': 'T.L.S. Corp.', 'size': 133} Got: {'address': ['2101 Superior Avenue', 'Cleveland OH 44114', 'UNITED STATES'], 'iab': '00-50-C2-00-00-00', 'idx': 84680704, 'offset': 68, 'org': 'T.L.S. Corp.', 'size': 133} What version of the product are you using? On what operating system? Python 2.6.2 in FreeBSD 7.2R
    What is the expected output? What do you see instead? ====================================================================== FAIL: Doctest: tutorial.txt ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/local/lib/python2.6/doctest.py", line 2145, in runTest raise self.failureException(self.format_failure(new.getvalue())) AssertionError: Failed doctest test for tutorial.txt File "/usr/local/tinderbox/portstrees/FreeBSD/ports/net/py-netaddr/work/netaddr-0.7.2/netaddr/tests/ip/tutorial.txt", line 0 ---------------------------------------------------------------------- File "/usr/local/tinderbox/portstrees/FreeBSD/ports/net/py-netaddr/work/netaddr-0.7.2/netaddr/tests/ip/tutorial.txt", line 69, in tutorial.txt Failed example: int(ip) Expected: 3221225985L Got: 3221225985 ====================================================================== FAIL: Doctest: eui64.txt ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/local/lib/python2.6/doctest.py", line 2145, in runTest raise self.failureException(self.format_failure(new.getvalue())) AssertionError: Failed doctest test for eui64.txt File "/usr/local/tinderbox/portstrees/FreeBSD/ports/net/py-netaddr/work/netaddr-0.7.2/netaddr/tests/eui/eui64.txt", line 0 ---------------------------------------------------------------------- File "/usr/local/tinderbox/portstrees/FreeBSD/ports/net/py-netaddr/work/netaddr-0.7.2/netaddr/tests/eui/eui64.txt", line 23, in eui64.txt Failed example: int(eui) Expected: 7731765737772285L Got: 7731765737772285 ====================================================================== FAIL: Doctest: tutorial.txt ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/local/lib/python2.6/doctest.py", line 2145, in runTest raise self.failureException(self.format_failure(new.getvalue())) AssertionError: Failed doctest test for tutorial.txt File "/usr/local/tinderbox/portstrees/FreeBSD/ports/net/py-netaddr/work/netaddr-0.7.2/netaddr/tests/eui/tutorial.txt", line 0 ---------------------------------------------------------------------- File "/usr/local/tinderbox/portstrees/FreeBSD/ports/net/py-netaddr/work/netaddr-0.7.2/netaddr/tests/eui/tutorial.txt", line 57, in tutorial.txt Failed example: int(mac) Expected: 117965411581L Got: 117965411581 ---------------------------------------------------------------------- File "/usr/local/tinderbox/portstrees/FreeBSD/ports/net/py-netaddr/work/netaddr-0.7.2/netaddr/tests/eui/tutorial.txt", line 243, in tutorial.txt Failed example: iab.registration() Expected: {'address': ['2101 Superior Avenue', 'Cleveland OH 44114', 'UNITED STATES'], 'iab': '00-50-C2-00-00-00', 'idx': 84680704L, 'offset': 68, 'org': 'T.L.S. Corp.', 'size': 133} Got: {'address': ['2101 Superior Avenue', 'Cleveland OH 44114', 'UNITED STATES'], 'iab': '00-50-C2-00-00-00', 'idx': 84680704, 'offset': 68, 'org': 'T.L.S. Corp.', 'size': 133} What version of the product are you using? On what operating system? Python 2.6.2 in FreeBSD 7.2R
  • Aug 24, 2009
    r330 (This commit now only contains IP functionality. ) committed by drkjam   -   This commit now only contains IP functionality.
    This commit now only contains IP functionality.
  • Aug 24, 2009
    r329 (Experimental branch of netaddr containing only the IP subset...) committed by drkjam   -   Experimental branch of netaddr containing only the IP subset of functionality and no IANA files or lookup code.
    Experimental branch of netaddr containing only the IP subset of functionality and no IANA files or lookup code.
  • Aug 21, 2009
    IPTutorial (How to use netaddr with IP addresses and subnets.) Wiki page edited by drkjam   -   Revision r328 Edited wiki page through web user interface.
    Revision r328 Edited wiki page through web user interface.
  • Aug 20, 2009
    r327 (Tag for release 0.7.2 ) committed by drkjam   -   Tag for release 0.7.2
    Tag for release 0.7.2
  • Aug 20, 2009
    r326 (Release 0.7.2 final checkin. ) committed by drkjam   -   Release 0.7.2 final checkin.
    Release 0.7.2 final checkin.
  • Aug 20, 2009
    netaddr-0.7.2.tar.gz (netaddr release 0.7.2 (tarball)) file uploaded by drkjam   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • Aug 20, 2009
    netaddr-0.7.2.zip (netaddr release 0.7.2 (zip archive)) file uploaded by drkjam   -  
    Labels: Featured Type-Archive OpSys-All
    Labels: Featured Type-Archive OpSys-All
  • Aug 20, 2009
    netaddr-0.7.2.win32.exe (netaddr release 0.7.2 (MS Windows Installer)) file uploaded by drkjam   -  
    Labels: Featured Type-Installer OpSys-Windows
    Labels: Featured Type-Installer OpSys-Windows
 
Hosted by Google Code