Changes between Version 19 and Version 20 of ussf_book_chapter


Ignore:
Timestamp:
Sep 22, 2008, 10:50:52 AM (12 years ago)
Author:
Jamie McClelland
Comment:

Adding replacment text for the description of how we rerouted traffic

Legend:

Unmodified
Added
Removed
Modified
  • ussf_book_chapter

    v19 v20  
    143143Daniel came up with the solution and worked, under intense pressure, for the next 15 minutes to make it happen.
    144144
    145 When they were finished all traffic to the Social Forum website stopped being sent directly to New York. Instead, it was rerouted to our Delaware server as if that server was hosting the site. That server which wasn't hosting anything related to the Forum, transparently forwarded all requests from Delaware to New York where the site actually lived.
     145When they were finished all traffic to the Social Forum website stopped being sent directly to New York. Instead, it was rerouted to our Delaware server as if that server was hosting the site. That server which wasn't hosting anything related to the Forum, transparently forwarded all requests from Delaware to New York where the site actually lived. Although the Internet was designed to route around problems such as the one we were facing, we did not have access to the Bell South routers that needed to be re-configured to go around the faulty connection. We needed an alternative, non-standard way to re-route traffic, one that we could implement ourselves, without relying on Bell South.
    146146
    147 So, during the first hour and a half of the Social Forum, registration staff in Atlanta were going to the wrong server looking for the website and being bounced from that remote location to NYC to get the site. We circumvented Bell South's troublesome router.
     147So, during the first hour and a half of the Social Forum, registration staff in Atlanta were going to the wrong server looking for the website and being rerouted from that remote location to NYC to get the site. We circumvented Bell South's troublesome router.
    148148
    149149I dwell on this because this was, for me, a moment of great pride in the ITC team. We were there to make sure that event could use the Internet and, when confronted with the power of a corporate system effectively blocking that, our people figured out a way around it.