Peering your Caches

• Why?

  • To build hierarchies that make topological sense
  • Increases effective storage capacity
  • leverage bandwidth between isps.

• Configuring it

   # nlanr cache peers
    cache_peer pa.us.ircache.net            sibling 3128  3130 round-robin
    cache_peer_domain pa.us.ircache.net     !com !edu !org !net !ca !gov !us !128.223
    cache_peer sd.us.ircache.net            sibling 3128  3130 round-robin
    cache_peer_domain sd.us.ircache.net     !com !edu !org !net !ca !gov !us !128.223
  
  # orst proxy server
    cache_peer rin.nws.orst.edu             sibling 3128  3130
    cache_peer_domain rin.nws.orst.edu      !edu !gov !us !128.223
  
  # proxy2
    cache_peer 128.223.162.33         sibling   3128  3130  
  
  # proxy3
    cache_peer 128.223.162.201        sibling   3128  3130
  
  
  hierarchy_stoplist cgi-bin ?
  acl QUERY urlpath_regex cgi-bin \?
  no_cache deny QUERY
  

• ACLS

    acl ourallowedhosts src 128.223.0.0/255.255.0.0
    acl mesd src 198.236.63.0/255.255.255.0
    acl owencache src 198.237.157.0/255.255.255.0
    acl owen srcdomain or.us
    acl lane srcdomain lane.edu
    acl orst src 128.193.0.0/255.255.0.0
    acl moaz src 205.167.77.0/255.255.255.0
    #Mike Schuch  
    acl lane-current src 163.41.60.128/255.255.255.128
    acl lane-future src 163.41.62.0/255.255.255.0
    acl all src 0.0.0.0/0.0.0.0
  
    http_access allow ourallowedhosts
    http_access allow mesd
    http_access allow owencache
    http_access allow owen
    http_access allow lane
    http_access allow orst
    http_access allow moaz
    http_access allow lane-current
    http_access allow lane-future
    http_access deny all
  
    icp_access allow ourallowedhosts
    icp_access allow mesd
    icp_access allow owencache
    icp_access allow owen
    icp_access allow lane
    icp_access allow orst
    icp_access allow moaz
    icp_access allow lane-current
    icp_access allow lane-future
    icp_access deny all
  

Joel Jaeggli joelja@darkwing.uoregon.edu - 06/11/2003