05-15-2013, 10:08 AM | #1 | ||
Death Herald
Join Date: Nov 2000
Location: Le stelle la notte sono grandi e luminose nel cuore profondo del Texas
|
So, there's this thing called IPv6
I consider myself a very solid networking guy. I've gotten most Cisco certs short of the CCIE, which I passed the written test for but never got to take the practical exam. I understand IPv4 very well. But for the life of me I'm having a hard time getting my head around IPv6. I don't think it should be this difficult, but I'm obviously missing something.
Anyone here gotten a good understanding of IPv6? If so, what did you use to learn about it? I've gotten a couple of books, but after reading through them I didn't really have much more understanding than before I picked them up.
__________________
Thinkin' of a master plan 'Cuz ain't nuthin' but sweat inside my hand So I dig into my pocket, all my money is spent So I dig deeper but still comin' up with lint |
||
05-15-2013, 10:20 AM | #2 |
College Prospect
Join Date: Jan 2005
Location: Inland Empire, PRC
|
Here's the hardest thing to get your head around from my POV:
Wasting tons of address space is OK! in IPv6. A /64 for a small office LAN? Yes, that's fine. A /64 for a point-to-point link? Sure! No problem! We will be doing /127, maybe /126 for a point-to-point. The difficult one will be the /64 for a network infrastructure LAN (routers, switches) The way I see it for my network is that I'll be assigning a /61 as the smallest allocation to an office to cover Data, Voice, Wireless, and infrastructure. This will allow me to get from at fewest 6 routes to 1 in my global routing table. Larger facilities will get larger allocations but it will still be 1 route/site. Of course, the more difficult part for me will be the global/regional strategy of address allocation. Do we assign the entire corporation from our ARIN assigned space or get space from APNIC and RIPE as we have internet POPs there? all the best, --t |
05-15-2013, 01:11 PM | #3 | |
Pro Starter
Join Date: Nov 2002
Location: Winnipeg, MB
|
Quote:
What. The. Fuck.
__________________
"Breakfast? Breakfast schmekfast, look at the score for God's sake. It's only the second period and I'm winning 12-2. Breakfasts come and go, Rene, but Hartford, the Whale, they only beat Vancouver maybe once or twice in a lifetime." |
|
05-15-2013, 02:34 PM | #4 |
College Benchwarmer
Join Date: Oct 2000
Location: calgary, AB
|
|
05-16-2013, 11:11 PM | #5 |
College Benchwarmer
Join Date: Apr 2008
Location: Sterling Heights, Mi
|
|
05-17-2013, 06:27 AM | #6 | |
hates iowa
Join Date: Oct 2010
|
Quote:
|
|
05-19-2013, 04:36 PM | #7 |
Pro Rookie
Join Date: Nov 2000
Location: USA
|
Right now I am able to get a /64 from my ISP (Comcast). Every IPv6 capable device on my network gets its own public IPv6 address. IPv4 is still behind a NAT router. From a use perspective, I find that my IPv6 connections tend to be slightly faster than IPv4 to the same server/service.
From a security and management perspective, I'm in the same boat. I don't really know much in that area either. Most security/management devices/appliances/etc seem to be geared around IPv4 and if IPv6 is even allowed, it is merely passed through. |
05-19-2013, 05:12 PM | #8 |
Coordinator
Join Date: Oct 2000
|
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
|
|