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