Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>There are a lot of things to consider. Off the top of my head:</p> <ul> <li>Learn the difference between link-local (<code>fe80::/10</code>), global unicast, and multicast address ranges. Make sure you support interface scoping with link-local addresses (you will see addresses like <code>fe80::1%eth1</code>, which will indicate the link-local address on the eth1 interface).</li> <li>ARP equivalent (IPv6 neighbor discovery) is now part of ICMP. This is important because if the user wants to block ICMP packets and isn't careful, they could lose all their connectivity!</li> <li>Most (sane) protocols will not need major changes. FTP is one protocol that <em>will</em> potentially need changes, since it sometimes passes network addresses within the protocol itself (rather than letting the lower-level protocols take care of it)</li> <li>The most basic tunneling/transition mechanism you will need is called 6in4; it simply encapsulates IPv6 packets within IPv4 packets and allows the user to manually configure the endpoints of the tunnel. Automatic tunneling mechanisms like 6to4 and Teredo can also be useful in some situations. </li> <li>If you are selling a commercial product, I recommend you take a look at the <a href="http://w3.antd.nist.gov/usgv6/test-specifications.html" rel="nofollow">USGv6 test selection tables</a>. Also, read through the <a href="http://w3.antd.nist.gov/usgv6/profile.html" rel="nofollow">USGv6 profile</a> which has pointers to many of the RFCs you will need to understand in order to develop an IPv6-compliant product. Not supporting the USGv6 profile for a network protection device (NPD) could severely limit your market. Finally, get some training! IPv6 is vastly different from IPv4 in many ways. If your employer wants this project to succeed, training will be critical given that it appears that many project members are new to both IPv6 and network security. (do you have a mentor on the team to ask questions?)</li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload