Recently, I posted about some lab verification I did during a customer setup where I had to strip private BGP AS numbers (64512-65535) before sending BGP-learned prefixes upstream to an ISP.
While I used the purpose-built “remove-private-as” neighbor command, several readers commented to me via the blog and via Twitter with some ideas for alternate solutions. They even got me thinking about an idea of my own.
I have an interesting project going on with two of my customers. One of them is buying a web-hosting business from the other, and we have to migrate all of the resources (including IP space) from one organization to the other in the same colo. Of course there is a lot involved with this, but one of the things we had to consider was the routing. For the short term (the next few months), the company buying the hosting business (let’s call them BUYER, Inc), will not have its own Internet connection from the colo, but will instead transit through the selling company (we’ll call them SELLER Corp.).
Virtualization, Storage, and other techy stuff
I ask those questions you're too clever to.
Pluribus Networks Founder's Blog on OS, Networking, Virtualization, Cloud Computing, Solaris Architecture, etc
Just another WordPress.com weblog
Data networking, stray thoughts, nerdy fun...
Tales of the network reformation
Jottings on the intersection of tech and humanness
Ramblings about my thoughts, experiences, and ideas.
Attaining my CCIE with the help of Warhammer 40k
Making Packets Do Silly Things
Ramblings of JD (@subnetwork)
Musings from yet another IT nerd
Resource sharing, time sharing, (20)11 and beyond. A retired sysadmin's blog.
Herding Packets 