Hah - ok, well I know it'll be treated as unreachable if that's propagated. But if it's simply a local route (we're not planning on distributing that info) then the packet will still get punted, no?
I agree, Null0 seems like the safest and sanest solution, but I just wanted to check that my assumption about ::2/128 and 127.0.0.1/32 were correct. -----Original Message----- From: Mack McBride [mailto:[email protected]] Sent: Friday, June 11, 2010 5:30 PM To: Christian MacNevin; [email protected] Subject: RE: null routing in ipv6 Your brain isn't running IPv6 yet. Pony up the six pack. ::2 will be treated as an unreachable. However, this is bad practice because you can't guaranty someone isn't going to insert a default. Point the d*$% thing at Null0. Mack McBride Network Architect Viawest, Inc. Router#show ipv6 route ::1 Routing entry for ::/127 Known via "connected", distance 0, metric 0, type receive Route count is 1/1, share count 0 Routing paths: receive via Null0 Last updated 00:02:11 ago Router#show ipv6 route ::2 % Route not found -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Christian MacNevin Sent: Friday, June 11, 2010 3:12 PM To: [email protected] Subject: [c-nsp] null routing in ipv6 Hello A distinguished and beautifully tanned colleague of mine came up with the wild notion of routing black hole traffic to the ipv6 equivalent Of 127.0.0.2 (::2/128). So far, it's been working. My question is whether this is in fact going to punt everything to the CPU and in fact worsen the situation under load. My brain says maybe it is and as of this email I've decided that there's a six pack riding on it. Accordingly, should we move that back to set next hop int Null0? Thanks! Christian _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
