| 1 | <html><head>
|
|---|
| 2 |
|
|---|
| 3 | <title>IP Database</title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
|---|
| 4 |
|
|---|
| 5 | <link rel="stylesheet" type="text/css" href="/ip/ipdb.css" />
|
|---|
| 6 |
|
|---|
| 7 | </head>
|
|---|
| 8 | <body bgcolor="#ffffff" text="#000000" link="#000000" vlink="#000000" alink="#ff0000" leftmargin="0" topmargin="0" marginwidth="0">
|
|---|
| 9 |
|
|---|
| 10 | <table class="regular">
|
|---|
| 11 |
|
|---|
| 12 | <tr><td class="heading" colspan=2>Changes to the IPDB</td><tr>
|
|---|
| 13 |
|
|---|
| 14 | <tr class="color2">
|
|---|
| 15 | <td valign=top>03/10/2005</td>
|
|---|
| 16 | <td>Finally! Support for "container"/"reserve" netblocks to make tracking superblocks like
|
|---|
| 17 | 209.91.191.0/24 easier. Also supports "dynamically routed DSL netblocks"; ie,
|
|---|
| 18 | netblock-aligned chunks of static DSL IPs with netblock-ish subnet masks such as
|
|---|
| 19 | 209.91.186.0/25.
|
|---|
| 20 | </td></tr>
|
|---|
| 21 | <tr class="color1">
|
|---|
| 22 | <td valign=top>02/09/2005</td>
|
|---|
| 23 | <td>Pool handling has been cleaned up - all PPP-ish pools (modem, DSL, WiFi) now generate a
|
|---|
| 24 | full list of IPs rather than reserving the network, gateway, and broadcast IPs necessary on
|
|---|
| 25 | a "real" subnet. They will also not display this incorrect and useless information.
|
|---|
| 26 | </td></tr>
|
|---|
| 27 | <tr class="color2">
|
|---|
| 28 | <td valign=top>01/27/2005</td>
|
|---|
| 29 | <td>New cities/locations can now be added to the database here.
|
|---|
| 30 | </td></tr>
|
|---|
| 31 | <tr class="color1">
|
|---|
| 32 | <td valign=top>11/30/2004</td>
|
|---|
| 33 | <td>Overhauled the city listings; they should be somewhat more complete now. Still needs a
|
|---|
| 34 | mechanism to easily add new cities.
|
|---|
| 35 | </td></tr>
|
|---|
| 36 | <tr class="color2">
|
|---|
| 37 | <td valign=top>11/26/2004</td>
|
|---|
| 38 | <td>Allocating a static IP is now a little different. Use the "Customer Location" field to
|
|---|
| 39 | enter the customer's actual city, and use the "Route from/through" field to pick the POP or
|
|---|
| 40 | cable node the IP should come from.
|
|---|
| 41 | </td></tr>
|
|---|
| 42 | </table>
|
|---|
| 43 |
|
|---|
| 44 |
|
|---|
| 45 | </body></html>
|
|---|
![[ DeepNet IP Database ]](/images/ipdb-logo.png){kind=logo}
