I was studying via Google+ Hangout the other day with CJ and Rob, and one of the topics that came up was the idea of OSPFv2 advertising all loopbacks as 32-bit no matter what the configured mask is. I rarely use loopbacks outside of a lab and had no idea, so I set up a quick lab to see for myself. Sure enough! That’s exactly what I saw.
ACLs in IPv6 aren’t that different from what you’re used to dealing with in the IPv4 world. You create a list of denies and permits for use with some other structure like filtering, PBR, and all sorts of other stuff.
My ISP is not ready for IPv6. They’ve ignored my emails asking about their deployment strategy, so I gave up and looked at turning up an IPv6 tunnel with a broker.
Are you sensing a theme lately? Since we covered the basics of the main IGPs (I’m an enterprise guy, so no IS-IS comments, please.), I thought I’d try to describe the basics of advertising IPv6 routes over BGP. Yet again, we’re not going to do any route manipulation or change any of the 948284928 BGP attributes. We’re just trying to get routes exchanged.
A few hours ago, the last of the IPv4 addresses were allocated by IANA. Now’s the time to learn more about IPv6! Yesterday, I posted about EIGRP for IPv6, so I think I’ll continue the trend by introducing OSPFv3, which is the IPv6 implementation of OSPF
I’m not going to go all out like Jeremy over at Packetlife.net has, but I’m going to start to discuss a few IPv6 topics. In time (like in September when APNIC runs out of IPv4 addresses), I’m sure I’ll ramp up the IPv6 talk, but let’s start easy and get EIGRP for IPv6 up and running.
Study Questions Your boss says that ever host in the network needs to be converted over to IPv6 by the end of the day. Which of multipoint tunnels, point-to-point tunnels, or native IPv6 would be the most appropriate to use…
I guess we would eventually discuss routing IPv6. It was inevitable.
IPv6! This is new territory for me.