This document provides information about IP address conversion between IPv4 and IPv6, as well as common IP address ranges and formats. It also discusses some web application concerns and considerations for supporting both IPv4 and IPv6, such as additional validation of IPv4-embedded IPv6 addresses, larger space required for storing IPv6 addresses in databases, and ensuring log analyzers and tools support the IPv6 format. Automatic and static configuration techniques for IPv6, including link-local addresses, public address blocks, tunneling protocols like Teredo and 6to4, and their address formats are outlined.
3. Link-local?
fe80::/10
Use to ask:
Anyone else here on this link?
Anyone here with a special address
(e.g. looking for a router)?
Announce for rules (router advertise).
11. Web application concerns
GeoIP requires additional IPv6 database
Log analyzer (webalizer, awstats) and
v4embed address
12. Web application concerns
Direct connect to IPv6 address:
use [ ] brackets like “[2001:db8::1]”
Example:
13. Web application concerns
Communicating to other site by curl,
file_get_contents, …
IPv4-only servers or some with incorrect
ipv6 setting might have problem when
access to dual-stack sites ex: Facebook,
Google
○ Server try to connect to ipv6 first, then ipv4.
○ Some more latency for retry with ipv4.
14.
15. Automatic configuration
Just enable IPv6 !
Router will advertise itself and prefix /64
to use in that network.
Client will automatically assign address
with EUI-64 or Pseudo-random address.
18. Teredo
Automated tunnel under windows vista/7
Use UDPv4 to pass thru NAT under IPv4
No static address can be use as a server!
Connects only to direct IP's