HOSTING

Feb 13 2020

CoDeeN – A CDN on PlanetLab, cdn hosting.

#Cdn #hosting



Cdn hosting

Cdn hosting

C o D ee N is an academic testbed Content Distribution Network (CDN) built on top of PlanetLab by the Network Systems Group at Princeton University. This testbed CDN consists of a network of high-performance proxy servers. Currently, proxy servers have been deployed on many PlanetLab nodes. These proxy servers behave both as request redirectors and server surrogates. They cooperate with each other and collectively provide a fast and robust web content delivery service to C o D ee N users. A number of projects are related to C o D ee N , including the following:

  • Co Deploy , an efficient synchronization tool for PlanetLab slices.

  • Co DNS , a fast and reliable name lookup service.

  • Co Mon , a Web-based general node/slice monitor that monitors most PlanetLab nodes.

  • Co Visualize , a visualization tool graphically displaying PlanetLab activity.

    How to Use

    C o D ee N follows an opt-in model: to take advantage of C o D ee N ‘s service, you need to make a small change to your browser’s proxy configuration. Here are the steps for two common browsers.

    [Disclaimer:] C o D ee N is still under development, and while we are striving to provide continual service, it may not always be as smooth as we would like. If you are interested in using C o D ee N , please bear with us when problems arise, and feel free to provide us with feedback on your experiences.

    Before taking the following steps, you need to first pick a proxy server near you from this list and denote it as your-nearby-proxy . For example, Princeton users may choose planetlab-1.cs.princeton.edu. Note: some PlanetLab sites are currently filtering port 3128, so if that port does not work, you should pick a different node or try ports 3127 or 3124.

    • In the IE window, click menu item “Tools” “Internet options. “
    • In the “Internet Options” dialog box, click “Connections” tab
    • In this “Connections” tab,
      • If you have a Local Area Network (LAN) connection, click “LAN Settings. ” button at the right bottom.
      • If you have Dial-up or Virtual Private Network (VPN) connections, choose the connection you are using from the selection list at the top titled as “Dial-up and Virtual Private Network settings” and then click “Settings. ” button on the right.
    • In either “Local Area Network (LAN) Settings” or “Dial-up and Virtual Private Network settings” pop-up box, find the “Proxy server” section, select “Use a proxy server. ” and click on the Advanced button. In the field for an HTTP proxy, provide the name of your-nearby-proxy and set “Port” to 3128 . Click OK.
    • Click “Advanced” button to specify using HTTP proxy only.
    • Click OK in the “Internet Options” box.
    • You are ready to use C o D ee N now.
    • In the Navigator window, click menu item “Edit” “Preferences. “
    • In the pop-up “Preference” dialog box, on the left column, click “Advanced”, then click “Proxies”.
    • On the right column, select “Manual proxy configuration” and click “View. “
    • In the pop-up “Manual Proxy Configuration” dialogue box, on the first row labeled as “HTTP”, set “Address of proxy server to use” to be your-nearby-proxy and “Port” to be 3128 . Click OK.
    • Click OK in the “Preference” box.
    • You are ready to use C o D ee N now.

    You can get a list of current C o D ee N proxy servers and their status through this link:

    Publications,

    CoDeeN intro presented at the August 2003 MIT IRIS/PlanetLab meeting. Also in powerpoint format.

    CoDNS presented at the October 2003 RPI PlanetLab meeting. Also in powerpoint format.

    CoDeploy presented at the March 2004 HP Palo Alto PlanetLab meeting. Also in powerpoint format.

    CoDeeN runs on the PlanetLab global network testbed. PlanetLab has been supported in part by the National Science Foundation* (under grants 0101247, 0454278, 0335214) and by DARPA (under contract N66001-05-1-8902). Support is also provided by companies that join the PlanetLab Consortium.

    *Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation.

    People

    Privacy

    All accesses via C o D ee N are logged, mostly to aid in identifying abuse and other forms of damage control. We sometimes monitor these logs, report abuse, and release entries to aid in investigations. In case of suspicious traffic, we may access URLs from the logs to determine what kind of content is passing through our network. We are also using these logs in our own research, so they may be examined as needed for non-abuse reasons. For normal users, we do not expect that we will intentionally release any personally-identifying information. To prevent abuse, some sites have requested we pass along the client IP addresses, and these are included with every request forwarded to those sites.

    Security

    We receive many queries about whether C o D ee N is an open proxy, and whether it is safe for the hosting institutions. C o D ee N uses semi-restricted proxies, with a number of protections against the abuse normally encountered by open proxies. Some of these are described below:

    • Sites that contained licensed content, such as electronic journals and databases, are not accessible by the general public. In this manner, an organization does not have to worry about protecting its subscriptions from unauthorized access.

  • Requests are not forwarded from a client outside the organization to a server within the organization via a local proxy. In this way, pages with IP-address restrictions cannot be viewed by outsiders.

  • We test a number of known virus and attack signatures, and automatically ban clients attempting to use these attacks.

  • We log all accesses, and cooperate with investigations of abuse. All clients using CoDeeN are greeted with a splash screen providing information on our privacy policies.

  • We restrict the HTTP methods we allow, as well as the ports that can be accessed. As a result, clients cannot post content, upload files, or access non-HTTP services, such as SMTP-based e-mail.

  • We detect robotically-generated traffic and place more restrictions on it in terms of request behavior. Robots are banned quite aggressively, as soon as we detect any suspicious-looking traffic.

  • Despite these steps, some Web sites still list C o D ee N among their “anonymous” or “elite” proxies. The reason for this is because most of these sites make money selling access to their lists or to their proxy-hopping software. By advertising larger lists, their service looks more impressive than it really is. Many of the more honest sites have begun to either separate out C o D ee N proxies or offer tools to avoid using them.



  • Written by admin


    Leave a Reply