|
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
- 2.1 What license does the project use?
- 2.2 Are your pictures copyright protected?
- 2.3 What is the status of the project?
- 2.4 I am an Internet Service / major up-stream provider and I want to find or prove dominance of my route points on the Internet, can the opte project help me with this?
- 2.5 I am a programmer and want to help Opte, how do I do this?
- 2.6 What about private IP address ranges that are routed inside networks?
2.1 What license does the project use?
| All code that is released by this project is protected under the GNU General Public License (GPL). That license can be found here: http://www.gnu.org/licenses/gpl.html |
2.2 Are your pictures copyrigtht protected?
| The pictures are copy protected under the Creative Commons License. The details of that license are available here: http://creativecommons.org/licenses/by-nc-sa/1.0/ |
2.3 What is the status of the project?
| The Status of the project and code can be found in the middle of the page at www.opte.org/status/ |
2.4 I am an Internet Service / major up-stream provider and I want to find or prove dominance of my route points on the Internet, can the opte project help me with this?
| Opte is not currently looking to provide services for ISPs or up-stream providers, however each request is dealt with on a case-by-case basis. If you think our project could benefit your company, feel free to contact our project leader at: blyon [.at.] netpr.com. |
2.5 I am a programmer and want to help Opte, how do I do this?
| The best way to join the project is to get on Efnet IRC and join #opte. There you can ask questions about the project and donate time to the project. We are in need of programmers to help optimize the current PHP / SQL / LGL code platform. |
2.6 What about private IP address ranges that are routed inside networks?
| RFC1918 is the standard for routing inside private networks.
Sometimes Internet companies who own route points through out the internet
may use private IP ranges to route points inside there own network. Although
the Internet community frowns upon this practice, it is still used. This
can cause some major discrepancies in the map data. To counteract this,
we used a unique method. For example when you trace route to 200.80.198.250 you get a private IP of 10.168.255.6 toward the end of the route. This might show up on many different traceroutes to different networks. The way to combat this is to take the three previous hop points and the private IP address and put them into a string. For example: "152.63.83.17765.195.234.14200.69.129.11810.168.255.6". Then we MD5 check sum the string and it comes out as: "1e1533eabf7fa08226c81224a589cbac". Then we add RFC1918 to the beginning and get: "RFC19181e1533eabf7fa08226c81224a589cbac". That becomes the identifier for the hop point in the route and is what shows up in the LGL data. The method is not perfect, but it seems to be working very well on all of our tests. It keeps the route points separated, and we can still tell exactly how each point is routed with the checksum. |
