Uputstvo za povezivanje na IPv6 mrežu

Uputstvo za povezivanje na IPv6 mrežu Počevši od 6. juna 2012. godine, veliki javni servisi će biti dostupni širom sveta kako putem IPv4 tako i putem IPv6 adrese. Bitno je na vreme se priključiti novom sistemu koji će tokom narednih godina potisnuti IPv4 adresni sistem. Da bi krajnji korisnik imao javnu IPv6 adresu, istu mu mora izdati njegov Internet servis provajder (ISP). Pomoću javne IPv6 adrese je moguće pristupiti web sadržajima na Internetu koji se nalaze na IPv6 mreži. Naši ISP-evi trenutno ne izdaju IPv6 adrese, tako da je trenutno moguće izaći na Internet samo putem IPv4 protokola. Mešutim, u slučaju da želite da testirate IPv6 protokol, kao i da pristupate IPv6 sajtovima (kao što je i sajt Visoke ICT škole), možete dobiti IPv6 adresu putem servisa koji je poznat kao 6to4 tunel. Servis omogućava prenos IPv6 paketa preko IPv4 mreže (IPv4 je obično Internet). Besplatan servis se nalazi na adresi http://tunnelbroker.net/ Potrebno je registrovati se na navedenom sajtu i kreirati 6to4 tunel po sledećem uputstvu: - Nakon registrovanja, kliknite na link "Create Regular Tunnel" - U polje IPv4 Endpoint (Your side) upišite vašu javnu IPv4 adresu. Javna IPv4 adresa se nalazi ispisana odmah pored oznake You are viewing from: - Izaberite server preko kojeg ćete izlaziti na IPv6 Internet. Sajt će obično preporučiti koji server da izaberete - Kliknite na Create Tunnel dugme - Nakon uspešno kreiranog tunela kliknite na novokreirani tunel, gde zatim možete videti IPv4 i IPv6 adresiranja vezana za vaš tunel - Klikom na Example Configuration karticu, sajt će prikazati izbor operativnih sistema za koje će vam ponuditi konfiguraciju

- Da bi se Windows XP (ili Windows 7) konfigurisao, potrebno je pokrenuti Command Prompt i ukucati dobijenu konfiguraciju - Nakon konfigurisanja, probajte da posetite sajt http://test-ipv6.com/ kako bi proverili IPv6 konekciju. Napomena: 1. Vaša javna IPv4 adresa mora biti dostupna putem ICMP protokola (omogućen ping ka istoj). 2. Ako koristite NAT (Network Address Translation), pobrinite se da ruter dozvoljava i prosleñuje IP protokol 41 Video uputstva možete pogledati na adresi: http://ipv6.he.net/presentations.php

IPv6 i NAT U slučaju da NAT servis na ruteru ne prosleñuje pakete, moguće je koristiti IPv6 tunel pod nazivom Teredo. U pitanju je Microsoft servis koji je instaliran na Windows 7 računarima (i pokrenut), dok je za Windows XP računare potrebno instalirati ga naknadno. Uputstvo za konfigurisanje je preuzeto sa adrese http://support.microsoft.com/kb/817778 IPv6 Teredo NAT traversal technology IPv6 is the next generation Internet Protocol that permits communication across a diverse set of networks. IPv6 Teredo is a transition technology that permits automatic IPv6 tunneling between hosts that are located across one or more IPv4 NAT devices. IPv6 traffic from Teredo hosts can flow across NATs because an IPv4 User Datagram Protocol (UDP) message encapsulates the traffic. If the NAT supports UDP port translation, the NAT supports Teredo. The one exception is a "Symmetric" NAT. Use of a Symmetric NAT is not supported. Currently a Symmetric NAT is seldom used. The Microsoft implementation of IPv6 Teredo is based on Internet Engineer Task Force (IETF) Internet Draft version 8, "Teredo: Tunneling IPv6 over UDP through NATs". Teredo permits other hosts on the Internet to communicate directly with your computer, and, permits direct communication between peer clients on the Internet. The following IPv6 Teredo NAT Traversal Technology components are included in the Advanced Networking Pack for Windows XP: Teredo client A Teredo client is a host that can obtain a Teredo address assignment, manage NAT mappings, and tunnel IPv6 traffic across the IPv4 Internet. Teredo clients forward NAT mapping initialization packets between Teredo clients and nodes on the IPv6 Internet. Teredo Host-Specific Relay A Teredo host-specific relay is a host that forwards packets between Teredo clients and IPv6 Internet nodes. Note Currently, only Teredo clients are supported in the Advanced Networking Pack for Windows XP. The Teredo Host-Specific Relay is configured automatically when it is required.

IPv6 Internet nodes must run the Advanced Networking Pack for Windows XP to provide a hostspecific relay to reach the Teredo client, or use a public Teredo relay. If a public Teredo relay is not available, Teredo clients that connect to a non-advanced Networking Pack for Windows XPcompatible IPv6 host may have to use IPv4. Configure the IPv6 Teredo client When you install the Advanced Networking Pack for Windows XP, your computer is automatically configured to enable the IPv6 Teredo client. Typically, you do not have to modify this configuration. However, if you must change these settings, use the netsh interface ipv6 command-line utility. To do this, follow these steps: 1. Click Start, and then click Run. 2. In the Open box, type cmd, and then press ENTER. 3. At the command prompt, type the following lines, and then press ENTER after each line: netsh interface ipv6 To configure the IPv6 Teredo client, use the set teredo command at the netsh interface ipv6 command prompt. The set teredo command uses the following syntax: set teredo [[type]=disabled client enterpriseclient default] [[ServerName=]HostName IPv4 Address default] [[RefreshInterval=]value default][[clientport=] set value default The parameters that you can use with the set teredo command are listed as follows: type: Specifies one of the following options: o disabled: Disable the Teredo service. o client: Enable the Teredo client. o enterpriseclient: Permit the Teredo client to work in a managed network ServerName: Specifies the name or IPv4 address of the Teredo server. RefreshInterval: Specifies the Teredo client refresh interval (in seconds). ClientPort: Permits users to specify a UDP port. If you do not use this option, the computer specifies the UDP. For more information about when to use the enterpriseclient and ClientPort options, see the "Additional information about how to configure NAT devices" section. For more information about netsh, see Windows XP Help and Support. To do this, click Start, click Help and Support, type using netsh in the Search box, and then press ENTER to view the topics.

NAT and IPv6 Teredo interoperability Teredo is an IPv6 technology that traverses NATs to provide end-to-end connectivity between IPv6 nodes. However, because of the wide range of NAT devices that are available from different vendors, Teredo may or may not function correctly with a particular NAT device. The following NAT devices have been thoroughly tested and are known to work with Teredo: LinkSys BEFW11S4 v.1 Linksys BEFSR41 Linksys BEFSR1 D-Link DI-713 with Firmware version 2.53b9 NETGEAR RP614 NETGEAR RP114 NETGEAR MR314 NETGEAR FVS318 Microsoft MN-100 Wired Base Station Siemens SpeedStream 2602 NAT Router SMC 7004VBR SMC 7004AWBR Belkin F5D6230-3 3Com 3C855 Windows XP Internet Connection Sharing You can update the following devices to work with Teredo: D-Link DI-604 D-Link DI-614 You can configure the following device to work with Teredo: Microsoft Broadband Wireless Base Station - MN-500 If your NAT device does not appear in the list, it does not mean that Teredo does not work with your NAT device. To verify whether Teredo is working correctly, you can use the netsh interface ipv6 command-line utility. To do this, follow these steps: 1. Click Start, and then click Run. 2. In the Open box, type cmd, and then press ENTER. 3. At the command prompt, type the following, and then press ENTER: netsh interface ipv6 show teredo The output includes a list that displays the current status of Teredo. If your client cannot use Teredo, the State is listed as Offline and Error contains more information that

explains why the client cannot use Teredo. You may be able to configure your device to use Teredo. For more information about how to configure NAT devices, see the "Additional information about how to configure NAT devices" section. The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products. Additional information about how to configure NAT devices UPnP support You may have a device that supports Universal Plug and Play (UPnP). UPnP is a configuration protocol that many devices support. The Teredo client tries to automatically configure NAT devices that support UPnP but otherwise do not allow Teredo traffic. This process occurs automatically. You do not have to configure any additional settings. However, each NAT device is different and may support UPnP but may also require the user to enable it. To determine whether your device supports UPnP, see the documentation that is included with your NAT device. ClientPort You may also be able to manually configure a specific UDP port for the Teredo client to use. Some NAT devices require network programs to use the same port for each connection. If your NAT appears to be blocking Teredo, you can use the ClientPort option described earlier in the "Configure the IPv6 Teredo client" section to set a specific port. The port can be any number between 1024 and 65356. EnterpriseClient The Teredo client is automatically disabled if the computer is a member of a corporate domain or if a firewall is detected. If you want to use Teredo from a corporate network, contact your network administrator before you use the EnterpriseClient option. This setting overrides the typical behavior and tries to enable Teredo on the client computer even when the client is a member of a domain.

Enable IPv6 ICF When you install the Advanced Networking Pack for Windows XP, IPv6 and IPv6 Internet Connection Firewall (IPv6 ICF) are installed but are not yet enabled. When IPv6 is enabled, IPv6 ICF is automatically enabled for all network connections. IPv6 ICF is separate from the IPv4 Internet Connection Firewall that is included with Windows XP, and therefore, you cannot view IPv6 ICF configuration information and statistics in the Network Connections folder. You can only view information about the IPv4 ICF in the Network Connections folder. IPv6 ICF provides the following capabilities: Stateful filtering for outbound traffic Unsolicited inbound traffic is automatically and silently dropped Port configuration When you install the Advanced Networking Pack for Windows XP, IPv6 ICF blocks all inbound ports. When you enable the optional Windows Peer-to-Peer Networking Component, ports 3540 (UDP) and 3587 (TCP) are opened for inbound traffic. Additionally, you can manually configure ports to accept unsolicited traffic from the network. For example, if you host an IPv6-enabled Web server, you can configure IPv6 ICF to permit unsolicited IPv6 traffic on TCP port 80. ICMP configuration You can configure Internet Control Message Protocol (ICMP) options. Logging information You can configure the logging of dropped packets, successful connections, or both. You can use the logs to help you troubleshoot security and performance issues. For more information about how to configure IPv6 ICF, visit the following Microsoft Web site: http://technet.microsoft.com/en-us/library/bb726938.aspx Manually enable IPv6 ICF IPv6 ICF is automatically enabled when IPv6 is enabled on the computer. No additional action is required. However, if you disable IPv6 ICF, you can manually enable it. To enable IPv6 ICF, follow these steps: 1. Click Start, and then click Control Panel. 2. Click Add or Remove Programs. 3. Click Add/Remove Windows Components. The Windows Components wizard starts. 4. Click Networking Services (but do not click to clear the check box), and then click Details.

5. Click to select the IPv6 Internet Connection Firewall check box, and then click OK. 6. Click Next. 7. Follow the instructions on the screen to install the component on the computer. Disable IPv6 ICF To disable IPv6 ICF, follow these steps: 1. Click Start, and then click Control Panel. 2. Click Add or Remove Programs. 3. Click Add/Remove Windows Components. The Windows Components wizard starts. 4. Click Networking Services (but do not click to clear the check box), and then click Details. 5. Click to clear the IPv6 Internet Connection Firewall check box, and then click OK. 6. Click Next. 7. Follow the instructions on the screen to remove the component from the computer. Known issues IPv6 connectivity issues when you use incorrect firewall settings. You may have connectivity issues if firewall settings for ICF for IPv4 or ICF for IPv6 are not configured correctly. To resolve this behavior, use the following command at the command prompt to update the firewall settings: netsh interface ipv6 set teredo client Windows XP peer-to-peer ports are not open when you install a new network adapter. If Windows XP Peer-to-Peer Update Beta is installed on the computer, and you do not remove it before you install the Advanced Networking Pack for Windows XP, the appropriate ports for the Windows XP peer-to-peer networking infrastructure are not opened when you install a new network adapter. This behavior occurs because ports are not opened globally in Windows XP Peer-to-Peer Update Beta. To resolve this behavior, disable, and then and re-enable the Windows XP Peer-to-Peer Networking Component. The guest account cannot use a Windows XP peer-to-peer networking program. You must log on with a user account other than the Guest account to use the Windows XP peer-to-peer networking infrastructure. A program, such as Microsoft Internet Explorer, may not be able to resolve domain names from some Domain Name System (DNS) servers after you enable IPv6. Because of this, you may not be able to access some Web sites. This problem may occur if the DNS server is queried for a non-"a" record, and the server replies with an authoritative response that returns NXDOMAIN or NAME_ERROR (Response Code, or RCODE, 3)

although an "A" (or Internet Protocol version 4, or IPv4, host) record for the queried name exists on that DNS server. NXDOMAIN or NAME_ERROR in the response indicates that there are "no records of any type for that name." Microsoft has found that some DNS server software does not support "AAAA" (Internet Protocol version 6 or IPv6) records and incorrectly responds with NXDOMAIN although an "A" record exists for the site. For additional information about this issue, click the following article number to view the article in the Microsoft Knowledge Base: 815768 Application cannot resolve some domain names IPv6 traffic is not filtered by the IPv4 ICF in Windows XP. To filter IPv6 traffic, you must use the IPv6 ICF included with the Advanced Networking Pack.