Follow-up to the Windows Update post

Hi palz. K so I was in a similar situation to the last one that prompted me to write the Windows Update post. This time, it required running Windows Update on Windows Server 2003 base version (without SP1). Now keep in mind, being the br0n pwny that I am, I have a CD with SP1 slipstreamed in already. However, I have a new dedicated server customer that specifically requested Win2k3 *without* SP1. Needless to say, I will need Windows Updates so he doesn't get hacked. Since I'm still an aspiring pwny, I haven't yet implemented slipstreaming of windows updates into my installation CDs, and why should I? It's a pain in the ass.

So anyway, I had to do Windows Updates on this Win2k3 box. Now that I have a little more time to do some research on the IP allocations, I will provide an updated list of the IPs and masks that I had to route in order to update this Win2k3 box. The masks will be all-inclusive, meaning, they will include the entire allocation according to ARIN (wherever possible), not just one /24 out of a larger block, ala my previous post. I will include the blocks in address/network_bits format AND provide a netmask for you clowns who can't add and subtract.

64.4.0.0/18 255.255.192.0
207.46.0.0/18 255.255.0.0
*64.21.49.0/24 255.255.255.0 (note: this block belongs to NAC)
*4.79.74.0/24 255.255.255.0 (note: this block belongs to LVLT)

Also of interest is that I don't recall seeing any of the 64.4.0.0/18 or 64.21.49.0/24 addresses in my netstat while I updated the box. Anyway, i'm off to do more pwning. BBBBBBBBBBBBBBBye.

-the br0n pwny