Google Deploys IPv6 For Internal Network 260
itwbennett writes "Google is four years into a project to roll out IPv6 to its entire internal employee network. At the Usenix Large Installation System Administration (LISA) conference in Boston last week, Google network engineer Irena Nikolova shared some lessons others can learn from Google's experience. For example: It requires a lot of work with vendors to get them to fix buggy and still-unfinished code. 'We should not expect something to work just because it is declared supported,' the paper accompanying the presentation concluded."
IPv4.1 (Score:2, Funny)
Simple solution, bump it up a notch.
My octets go to 257. Solved.
Re:IPv6 (Score:5, Funny)
Oh man, what I would have given to be there for that conversation.
"How many addresses do you figure we need?"
"Couple billion I guess."
"But what if we need more?"
"Dude, okay, let's just say one per person. 4 and a half billion or so. Now everyone on the world can have one."
"But what if, you know, there ends up being a few more people than that in the future?"
"Jesus Christ man, it's not like 3 billion extra people are gonna pop up out of nowhere in the next 30 years!"
Re:IPv4.1 (Score:5, Funny)
That's not how IPv4.1 works. Check the facts [packetlife.net].
Re:Supported (Score:5, Funny)
If you mean that the managed switch dies when you connect an unmanaged switch with NO loop: then you have an extremely crappy managed switch. This use case has nothing to do with STP.
That's exactly what I mean; disable STP and it all starts to magically work.
This was a Dell switch, which probably explains rather a lot - rumour has it that particular model is a rebadged Allied Telesyn. Mind you, if Dell were to write to me informing me the sky was blue I'd stick my head out of the window.
Re:IPv6 (Score:4, Funny)
I knew there was a language issue. Had they only realise that in manager speak "it still have some issues" means "ship it" ...
Re:Business as usual? (Score:5, Funny)