Changes

Early in the morning of the first day of the first week of term, IT Services (as we later found out) replaced some networking equipment in the Vanbrugh area, and may have incorrectly set some static routes. The first we found out about this is at 9:30, when all of our monitoring pinged that URY had dropped off the face of the internet.

Early in the morning of the first day of the first week of term, IT Services (as we later found out) replaced some networking equipment in the Vanbrugh area, and may have incorrectly set some static routes. The first we found out about this is at 9:30, when all of our monitoring pinged that URY had dropped off the face of the internet.

Much scrambling and some reboots later, we narrowed down the state of the network to:

Much scrambling and some (ultimately futile) reboots later, we narrowed down the state of the network to:

* Anything with a 144.32.64.160/27 IP (so all of URY) could send packets ''out'' of URY, but no packets would make it ''in''.

* Anything with a 144.32.64.160/27 IP (so all of URY) could send packets ''out'' of URY, but no packets would make it ''in''.

:* With the exception of uryfw0 which has a separate IP (144.32.109.64).

:* With the exception of uryfw0 which has a separate IP (144.32.109.64).