ipaddress 0.8.0 → 0.8.2

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: fec38076134eaf8fe0a449f7e96d9be946d37b0f
+  data.tar.gz: 43c5c532b9d10c030e27a490eab789107a5c2680
+SHA512:
+  metadata.gz: ffd4cc11627aa588ef044a35767addb3a9498221746727435561439729e04e51fe1b70a660ffbc1f79ed952fdcd46fec30c5e88ef79667e9d68099eb9953a8b6
+  data.tar.gz: b273220fcdc8584a5841e16841a68f0b271d183d0e40c96ac1160cdc23bcd868f7460c0e6c4c1d2e590e1aa3e4ad7fc046540b5610a517637df1268818d3a262

data/.gitignore

@@ -0,0 +1,18 @@
+*.a
+/.bundle/
+*.bundle
+/coverage/
+/doc/
+.DS_Store
+/Gemfile.lock
+ipaddr.html
+mkmf.log
+*.o
+/pkg/
+rdoc
+server.rb
+*.so
+/spec/reports/
+*.sw?
+/tmp/
+/_yardoc/

data/.rock.yml

@@ -0,0 +1,5 @@
+runtime: ruby21
+doc: exec rake rdoc
+build: |
+  rock clean
+  {{parent}}

data/CHANGELOG.rdoc

@@ -1,5 +1,19 @@
+== ipaddress 0.8.2
+
+CHANGED:: merged bundler branch to cleanup gemspec and Rakefiles
+FIXED:: IPAddress::IPv4.split handling (Issue #40)
+NEW:: Added #[]= method to IPv4/6 classes to add octet writing support. (Issue #24)
+NEW:: IPV4#multicast?
+NEW:: IPV4#loopback?
+NEW:: IPV4#to()
+
+== ipaddress 0.8.1
+
+CHANGED:: ipaddress now uses minitest for testing, all tests passing
+
 == ipaddress 0.8.0
 
+CHANGED:: ipaddress now uses this[https://gist.github.com/cpetschnig/294476] regexp to validate IPv6 addresses. Thanks to Christoph Petschnig for his regexp and to Bronislav Robenek for fixing this.
 CHANGED:: Removed extension methods and extension directory to facilitate integration with the stdlib
 CHANGED:: Reworked IPv4#<=>, now intuitively sorts objects based on the prefix
 CHANGED:: IPv4#supernet now returns "0.0.0.0/0" if supernetting with a prefix less than 1
@@ -10,6 +24,7 @@ NEW::     IPv6#broadcast_u128
 NEW::     IPv6#each
 NEW::     IPv6#<=>
 NEW::     IPv4#split
+NEW::     IP#ntoa
 
 == ipaddress 0.7.5
 

data/Gemfile

@@ -0,0 +1,3 @@
+source "https://rubygems.org"
+
+gemspec

data/{LICENSE → LICENSE.txt}

@@ -1,4 +1,4 @@
-Copyright (c) 2009-2011 Marco Ceresa
+Copyright (c) 2009-2015 Marco Ceresa
 
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the

data/README.rdoc

@@ -1,3 +1,7 @@
+== <b>IPAddress 1.0 is currently under development and will be released soon! Stay tuned!</b>
+
+---
+
 = IPAddress
 
 IPAddress is a Ruby library designed to make the use of IPv4 and IPv6
@@ -17,7 +21,7 @@ examples of typical usage.
 * Ruby >= 1.8.7 (not tested with previous versions)
 * Ruby 1.9.2 or later is strongly recommended 
 
-IPAddress 0.8.0 has been tested on:
+IPAddress 0.8.2 has been tested on:
 
 * ruby-1.8.7-p334 [ i386 ]
 * ree-1.8.7-2011.03 [ i386 ]
@@ -25,6 +29,8 @@ IPAddress 0.8.0 has been tested on:
 * jruby-1.6.1 [ linux-i386-java ]
 * ruby-1.9.1-p431 [ i386 ]
 * ruby-1.9.2-p180 [ i386 ]
+* ruby-2.0.0-p353 [ x86_64-darwin14.0.0 ]
+* ruby-2.1.3-p242 [ x86_64-darwin14.0.0 ]
 
 If you want to collaborate feel 
 free to send a small report to my email address, or 
@@ -63,14 +69,14 @@ The latest documentation can be found online at
  
 == IPv4
 
-Class IPAddress::IPv4 is used to handle IPv4 type addresses. IPAddress
+Class `IPAddress::IPv4` is used to handle IPv4 type addresses. IPAddress
 is similar to other IP Addresses libraries, like Ruby's own
 IPAddr. However it works slightly different, as we will see.
 
 === Create a new IPv4 address
 
 The usual way to express an IP Address is using its dotted decimal
-form, such as 172.16.10.1, and a prefix, such as 24, separated by a
+form, such as `172.16.10.1`, and a prefix, such as `24`, separated by a
 slash. 
 
   172.16.10.1/24
@@ -83,11 +89,11 @@ or, in a easier way, using the IPAddress parse method
 
   ip = IPAddress.parse "172.16.10.1/24"
 
-which accepts and parses any kind of IP (IPv4, IPV6 and 
+which accepts and parses any kind of IP (uint32, IPv4, IPV6 and 
 IPv4 IPv6 Mapped addresses).
 
 If you like syntactic sugar, you can use the wrapper method
-IPAddress(), which is built around IPAddress::parse:
+`IPAddress()`, which is built around `IPAddress::parse`:
 
   ip = IPAddress "172.16.10.1/24"
 
@@ -96,13 +102,13 @@ You can specify an IPv4 address in any of two ways:
   IPAddress "172.16.10.1/24"
   IPAddress "172.16.10.1/255.255.255.0"
   
-In this example, prefix /24 and netmask 255.255.255.0 are the same and
+In this example, prefix `/24` and netmask `255.255.255.0` are the same and
 you have the flexibility to use either one of them.
 
 If you don't explicitly specify the prefix (or the subnet mask), 
 IPAddress thinks you're dealing with host addresses and not with 
-networks. Therefore, the default prefix will be /32, or
-255.255.255.255. For example:
+networks. Therefore, the default prefix will be `/32`, or
+`255.255.255.255`. For example:
 
   # let's declare an host address
   host = IPAddress::IPv4.new "10.1.1.1"
@@ -110,11 +116,18 @@ networks. Therefore, the default prefix will be /32, or
   puts host.to_string
     #=> "10.1.1.1/32"
   
-The new created object has prefix /32, which is the same 
+The new created object has prefix `/32`, which is the same 
 as we created the following:
 
   host = IPAddress::IPv4.new "10.1.1.1/32"
-  
+
+You can also pass a `uint32` to obtain an `IPAddress::IPv4` object:
+
+  # Create host object
+  ip = IPAddress 167837953
+  puts ip.to_string
+    #=> "10.1.1.1/32"
+
 === Handling the IPv4 address
 
 Once created, you can obtain the attributes for an IPv4 object:
@@ -127,25 +140,25 @@ Once created, you can obtain the attributes for an IPv4 object:
     #=> 24
 
 In case you need to retrieve the netmask in IPv4 format, you can use
-the IPv4#netmask method:
+the `IPv4#netmask` method:
 
   ip.netmask
     #=> "255.255.255.0"
 
-A special attribute, IPv4#octets, is available to get the four 
+A special attribute, `IPv4#octets`, is available to get the four 
 decimal octets from the IP address:
 
   ip.octets
     #=> [172,16,10,1]
 
-Shortcut method IPv4#[], provides access to a given octet whithin the
+Shortcut method `IPv4#[]`, provides access to a given octet whithin the
 range:
 
   ip[1]
     #=> 16
 
 If you need to print out the IPv4 address in a canonical form, you can
-use IPv4#to_string
+use `IPv4#to_string`:
 
   ip.to_string
     #=> "172.16.10.l/24"
@@ -161,7 +174,7 @@ object. For example:
     #=> "172.16.10.l/25"
     
 If you need to use a netmask in IPv4 format, you can achive so by
-using the IPv4#netmask= method
+using the `IPv4#netmask=` method:
 
   ip.netmask = "255.255.255.252"
 
@@ -174,7 +187,7 @@ Some very important topics in dealing with IP addresses are the
 concepts of +network+ and +broadcast+, as well as the addresses
 included in a range.
 
-When you specify an IPv4 address such as "172.16.10.1/24", you are
+When you specify an IPv4 address such as `172.16.10.1/24`, you are
 actually handling two different information: 
  
 * The IP address itself, "172.16.10.1"
@@ -183,11 +196,11 @@ actually handling two different information:
 The network number is the IP which has all zeroes in the host
 portion. In our example, because the prefix is 24, we identify our
 network number to have the last 8 (32-24) bits all zeroes.  Thus, IP
-address "172.16.10.1/24" belongs to network "172.16.10.0/24".
+address `172.16.10.1/24` belongs to network `172.16.10.0/24`.
 
-This is very important because, for instance, IP "172.16.10.1/16" is
+This is very important because, for instance, IP `172.16.10.1/16` is
 very different to the previous one, belonging to the very different
-network "172.16.0.0/16".
+network `172.16.0.0/16`.
 
 ==== Networks
 
@@ -208,7 +221,7 @@ number, calculated after the original object. We want to outline here
 that the network address is a perfect legitimate IPv4 address, which
 just happen to have all zeroes in the host portion. 
 
-You can use method IPv4#network? to check whether an IP address is a
+You can use method `IPv4#network?` to check whether an IP address is a
 network or not:
 
   ip1 = IPAddress "172.16.10.1/24"
@@ -223,11 +236,11 @@ network or not:
 
 The broadcast address is the contrary than the network number: where
 the network number has all zeroes in the host portion, the broadcast
-address has all one's. For example, ip "172.16.10.1/24" has broadcast
-"172.16.10.255/24", where ip "172.16.10.1/16" has broadcast
-"172.16.255.255/16".
+address has all one's. For example, ip `172.16.10.1/24` has broadcast
+`172.16.10.255/24`, where ip `172.16.10.1/16` has broadcast
+`172.16.255.255/16`.
 
-Method IPv4#broadcast has the same behavior as is #network
+Method `IPv4#broadcast` has the same behavior as is `#network`
 counterpart: it creates a new IPv4 object to handle the broadcast
 address:
  
@@ -245,7 +258,7 @@ address:
 So we see that the netmask essentially specifies a range for IP
 addresses that are included in a network: all the addresses between
 the network number and the broadcast. IPAddress has many methods to
-iterate between those addresses. Let's start with IPv4#each, which
+iterate between those addresses. Let's start with `IPv4#each`, which
 iterates over all addresses in a range
 
   ip = IPAddress "172.16.10.1/24"
@@ -258,7 +271,7 @@ It is important to note that it doesn't matter if the original IP is a
 host IP or a network number (or a broadcast address): the #each method
 only considers the range that the original IP specifies. 
 
-If you only want to iterate over hosts IP, use the IPv4#each_host
+If you only want to iterate over hosts IP, use the `IPv4#each_host`
 method:
 
   ip = IPAddress "172.16.10.1/24"
@@ -267,7 +280,7 @@ method:
     puts host
   end
 
-Methods IPv4#first and IPv4#last return a new object containing
+Methods `IPv4#first` and `IPv4#last` return a new object containing
 respectively the first and the last host address in the range
 
   ip = IPAddress "172.16.10.100/24"
@@ -278,6 +291,28 @@ respectively the first and the last host address in the range
   ip.last.to_string
     #=> "172.16.10.254/24"
 
+Checking if an address is loopback is easy with the `IPv4#loopback?`
+method:
+
+  ip = IPAddress "127.0.0.1"
+
+  ip.loopback?
+    #=> true
+
+Checking if an address is in the multicast range can be done using the `IPv4#multicast?`
+method:
+
+  ip = IPAddress "224.0.0.1/32"
+
+  ip.multicast?
+    #=> true
+
+The ability to generate a range also exists by using the `IPv4#to()` method. This allows you to create a subnet agnostic range based off a fixed amount.
+
+  ip = IPAddress "172.16.10.100/24"
+  ip.to('172.16.10.110')
+    #=> ["172.16.10.100", ..., "172.16.10.110"]
+
 === IP special formats    
 
 The IPAddress library provides a complete set of methods to access an
@@ -295,38 +330,43 @@ The first thing to highlight here is that all these conversion methods
 only take into consideration the address portion of an IPv4 object and
 not the prefix (netmask).
 
-So, to express the address in binary format, use the IPv4#bits method:
+So, to express the address in binary format, use the `IPv4#bits` method:
 
   ip.bits
     #=> "10101100000100000000101000000001"
 
 To calculate the 32 bits unsigned int format of the ip address, use
-the IPv4#to_u32 method
+the `IPv4#to_u32` method
 
   ip.to_u32
     #=> 2886732289
 
-This method is the equivalent of the Unix call pton(), expressing an
+This method is the equivalent of the Unix call `pton()`, expressing an
 IP address in the so called +network byte order+ notation. However, if
 you want to transmit your IP over a network socket, you might need to
-transform it in data format using the IPv4#data method:
+transform it in data format using the `IPv4#data` method:
 
   ip.data
     #=> "\254\020\n\001"
 
-Finally, you can transform an IPv4 address into a format which is
+Also, you can transform an IPv4 address into a format which is
 suitable to use in IPv4-IPv6 mapped addresses:
 
   ip.to_ipv6
     #=> "ac10:0a01"
 
+Finally, much like `IPv4#to_ipv6` you can use to `IPv4#to_h` method to return a non-semicolon delineated string (useful with pcap/byte level usage):
+
+  ip.to_h
+    #=> "ac100a01"
+
 === Classful networks
 
 IPAddress allows you to create and manipulate objects using the old 
 and deprecated (but apparently still popular) classful networks concept.
 
 Classful networks and addresses don't have a prefix: their subnet mask
-is univocally identified by their address, and therefore diveded in classes.
+is univocally identified by their address, and therefore divided in classes.
 As per RFC 791, these classes are:
 
 * Class A, from 0.0.0.0 to 127.255.255.255
@@ -388,7 +428,7 @@ Subnetting is easy with IPAddress. You actually have two options:
 * IPv4#subnet: specify a new prefix
 * IPv4#split: tell IPAddress how many subnets you want to create.
 
-Let's examine IPv4#subnet first. Say you have network "172.16.10.0/24"
+Let's examine `IPv4#subnet` first. Say you have network "172.16.10.0/24"
 and you want to subnet it into /26 networks. With IPAddress it's very 
 easy:
 
@@ -408,7 +448,7 @@ representing the new subnets.
 Another way to create subnets is to tell IPAddress how many subnets you'd 
 like to have, and letting the library calculate the new prefix for you.
 
-Let's see how it works, using IPv4#split method. Say you want 4 new subnets:
+Let's see how it works, using `IPv4#split` method. Say you want 4 new subnets:
 
   network = IPAddress("172.16.10.0/24")
 
@@ -421,15 +461,15 @@ Let's see how it works, using IPv4#split method. Say you want 4 new subnets:
          "172.16.10.192/26"]
 
 Hey, that's the same result as before! This actually makes sense, as the
-two operations are complementary. When you use IPv4#subnet with the new
+two operations are complementary. When you use `IPv4#subnet` with the new
 prefix, IPAddress will always create a number of subnets that is a power 
 of two. This is equivalent to use IPv4#split with a power of 2.
 
-Where IPv4#split really shines is with the so called "uneven subnetting".
+Where `IPv4#split` really shines is with the so called "uneven subnetting".
 You are not limited to split a network into a power-of-two numbers of
 subnets: IPAddress lets you create any number of subnets, and it will
 try to organize the new created network in the best possible way, making
-an efficent allocation of the space.
+an efficient allocation of the space.
 
 An example here is worth a thousand words. Let's use the same network
 as the previous examples:
@@ -447,8 +487,8 @@ How do we split this network into 3 subnets? Very easy:
 
 As you can see, IPAddress tried to perform a good allocation by filling up
 all the address space from the original network. There is no point in splitting
-a network into 3 subnets like "172.16.10.0/26", "172.16.10.64/26" and 
-"172.16.10.128/26", as you would end up having "172.16.10.192/26" wasted (plus,
+a network into 3 subnets like `172.16.10.0/26`, `172.16.10.64/26` and 
+`172.16.10.128/26`, as you would end up having `172.16.10.192/26` wasted (plus,
 I suppose I wouldn't need a Ruby library to perform un-efficient IP 
 allocation, as I do that myself very well ;) ).
 
@@ -460,8 +500,8 @@ We can go even further and split into 11 subnets:
          "172.16.10.96/28", "172.16.10.112/28", "172.16.10.128/27",
          "172.16.10.160/27", "172.16.10.192/26"]
 
-As you can see, most of the networks are /28, with a few /27 and one
-/26 to fill up the remaining space.
+As you can see, most of the networks are `/28`, with a few `/27` and one
+`/26` to fill up the remaining space.
 
 ==== Summarization
 
@@ -489,10 +529,10 @@ instance the following two networks:
 These two networks can be expressed using only one IP address
 network if we change the prefix. Let Ruby do the work:
 
-  IPAddress::IPv4::summarize(ip1,ip2).to_string
+  IPAddress::IPv4::summarize(ip1,ip2).map(&:to_string)
     #=> "172.16.10.0/23"
 
-We note how the network "172.16.10.0/23" includes all the
+We note how the network `172.16.10.0/23` includes all the
 addresses specified in the above networks, and (more important) includes
 ONLY those addresses.
 
@@ -509,7 +549,7 @@ is not an aggregate network for +ip1+ and +ip2+.
 If it's not possible to compute a single aggregated network for
 all the original networks, the method returns an array with all the
 aggregate networks found. For example, the following four networks can be
-aggregated in a single /22:
+aggregated in a single `/22`:
 
   ip1 = IPAddress("10.0.0.1/24")
   ip2 = IPAddress("10.0.1.1/24")
@@ -531,7 +571,7 @@ network:
     #=> ["10.0.1.0/24","10.0.2.0/23","10.0.4.0/24"]
 
 In this case, the two summarizables networks have been aggregated into
-a single /23, while the other two networks have been left untouched.
+a single `/23`, while the other two networks have been left untouched.
 
 ==== Supernetting
 
@@ -550,13 +590,13 @@ you can supernet it with a new /23 prefix
   ip.supernet(23).to_string
     #=> "172.16.10.0/23"
 
-However if you supernet it with a /22 prefix, the network address will
+However if you supernet it with a `/22` prefix, the network address will
 change: 
 
   ip.supernet(22).to_string
     #=> "172.16.8.0/22"
 
-This is because "172.16.10.0/22" is not a network anymore, but an host
+This is because `172.16.10.0/22` is not a network anymore, but an host
 address.
 
 == IPv6
@@ -638,7 +678,7 @@ methods:
     #=> 64
 
 A compressed version of the IPv6 address can be obtained with the
-IPv6#compressed method:
+`IPv6#compressed` method:
 
   ip6 = IPAddress "2001:0db8:0000:0000:0008:200c:417a:00ab/64"
 
@@ -648,7 +688,7 @@ IPv6#compressed method:
 === Handling the IPv6 address
 
 Accessing the groups that form an IPv6 address is very easy with the
-IPv6#groups method:
+`IPv6#groups` method:
 
   ip6 = IPAddress "2001:db8::8:800:200c:417a/64"
  
@@ -656,7 +696,7 @@ IPv6#groups method:
     #=> [8193, 3512, 0, 0, 8, 2048, 8204, 16762]
 
 As with IPv4 addresses, each individual group can be accessed using
-the IPv6#[] shortcut method:
+the `IPv6#[]` shortcut method:
 
   ip6[0]
     #=> 8193
@@ -668,14 +708,14 @@ the IPv6#[] shortcut method:
     #=> 0
 
 Note that each 16 bits group is expressed in its decimal form. You can
-also obtain the groups into hexadecimal format using the IPv6#hexs
+also obtain the groups into hexadecimal format using the `IPv6#hexs`
 method:
 
   ip6.hexs
     #=> => ["2001", "0db8", "0000", "0000", "0008", "0800", "200c", "417a"]
 
 A few other methods are available to transform an IPv6 address into
-decimal representation, with IPv6.to_i
+decimal representation, with `IPv6.to_i`
 
   ip6.to_i
     #=> 42540766411282592856906245548098208122
@@ -685,8 +725,8 @@ or to hexadecimal representation
   ip6.to_hex
     #=> "20010db80000000000080800200c417a"
 
-To print out an IPv6 address in human readable form, use the IPv6#to_s, IPv6#to_string
-and IPv6#to_string_uncompressed methods
+To print out an IPv6 address in human readable form, use the `IPv6#to_s`, `IPv6#to_string`
+and `IPv6#to_string_uncompressed` methods
 
   ip6 = IPAddress "2001:db8::8:800:200c:417a/64"
  
@@ -696,8 +736,8 @@ and IPv6#to_string_uncompressed methods
   ip6.to_string_uncompressed
     #=> "2001:0db8:0000:0000:0008:0800:200c:417a/96"
 
-As you can see, IPv6.to_string prints out the compressed form, while
-IPv6.to_string_uncompressed uses the expanded version.
+As you can see, `IPv6.to_string` prints out the compressed form, while
+`IPv6.to_string_uncompressed` uses the expanded version.
 
 ==== Compressing and uncompressing
 
@@ -731,7 +771,7 @@ actually created internally).
 You can create a new IPv6 address from different formats than just a
 string representing the colon-hex groups.
 
-For instance, if you have a data stream, you can use IPv6::parse_data,
+For instance, if you have a data stream, you can use `IPv6::parse_data`,
 like in the following example:
 
   data = " \001\r\270\000\000\000\000\000\b\b\000 \fAz"
@@ -772,7 +812,7 @@ support for unspecified, loopback and mapped IPv6 addresses.
 ==== Unspecified address
 
 The address with all zero bits is called the +unspecified+ address
-(corresponding to 0.0.0.0 in IPv4). It should be something like this:
+(corresponding to `0.0.0.0` in IPv4). It should be something like this:
 
   0000:0000:0000:0000:0000:0000:0000:0000
 
@@ -814,7 +854,7 @@ packets with the unspecified address.
 
 ==== Loopback address
 
-The loopback  address is a unicast localhost address. If an
+The loopback address is a unicast localhost address. If an
 application in a host sends packets to this address, the IPv6 stack
 will loop these packets back on the same virtual interface.
 
@@ -841,13 +881,13 @@ or by using the wrapper:
   ip.to_string
     #=> "::1/128"
 
-Checking if an address is loopback is easy with the IPv6#loopback?
+Checking if an address is loopback is easy with the `IPv6#loopback?`
 method:
 
   ip.loopback?
     #=> true
   
-The IPv6 loopback address corresponds to 127.0.0.1 in IPv4.
+The IPv6 loopback address corresponds to `127.0.0.1` in IPv4.
 
 ==== Mapped address
 
@@ -857,7 +897,7 @@ structure of the address is
 
   ::ffff:w.y.x.z
 
-where w.x.y.z is a normal IPv4 address. For example, the following is
+where `w.x.y.z` is a normal IPv4 address. For example, the following is
 a mapped IPv6 address:
 
   ::ffff:192.168.100.1
@@ -881,7 +921,7 @@ Let's check it's really a mapped address:
   ip6.to_string
     #=> "::ffff:172.16.10.1/128"
 
-Now with the +ipv4+ attribute, we can easily access the IPv4 portion
+Now with the `#ipv4` attribute, we can easily access the IPv4 portion
 of the mapped IPv6 address:
 
   ip6.ipv4.address
@@ -902,7 +942,7 @@ following format:
   
   ip6 = IPAddress "::172.16.10.1"
 
-That is, two colons and the IPv4 address. However, as by RFC, the ffff 
+That is, two colons and the IPv4 address. However, as by RFC, the `ffff`
 group will be automatically added at the beginning
 
   ip6.to_string
@@ -955,7 +995,4 @@ feedback and bug reports.
   
 == Copyright
 
-Copyright (c) 2009-2011 Marco Ceresa. See LICENSE for details.
-
-
- 
+Copyright (c) 2009-2015 Marco Ceresa and Mike Mackintosh. See LICENSE for details.