1 / 7

Check Point’s World IPv6 Day Experience

Check Point’s World IPv6 Day Experience. Bob Hinden. Starting Point. No external IPv6 presence prior to World IPv6 Day Started receiving questions from customers asking if we were going to participate IT Team had little or no experience with IPv6 We had an ARIN IPv6 allocation. Planning.

justis
Télécharger la présentation

Check Point’s World IPv6 Day Experience

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Check Point’s World IPv6 Day Experience Bob Hinden

  2. Starting Point • No external IPv6 presence prior to World IPv6 Day • Started receiving questions from customers asking if we were going to participate • IT Team had little or no experience with IPv6 • We had an ARIN IPv6 allocation

  3. Planning • Goal to make www.checkpoint.com reachable via IPv6 • Worked out rough plan with IT Team • Mixture of education and planning • Keep it simple • Set up meeting with local ISC IT Team so our IT folks could talk to IT folks who had done this before • Many thanks to ISC and Jim Martin

  4. What we did • Advertized our IPv6 prefix to our ISP (AboveNet) with BGP • Ran dual stack • Used our own Firewalls between the routers and load balancers • We used our existing load balancers to front for the web servers •  Meant we didn't have to touch the actual web servers

  5. What we learned • It was not as hard as the IT folks initially expected • Our ISP and existing deployed equipment supported IPv6 • A few things didn't work in the software releases we were using that we were able to work around • Adding dual stack IPv6 didn't degrade IPv4 service • Load Balancer approached worked well

  6. Conclusions • We left it up! • Concerns raised about 6to4 brokenness doesn’t seem to be a big concern • No need to keep a white list • Other organizations may be similar

  7. QUESTIONS?

More Related