Technical data

ManualsBrandsSamsung ManualsFlat Panel TVPC680-ZA

361

362

363

364

365

366

367

368

369

370

B. Appendixes to optional packages

The last two settings are not absolutely necessary for a working IPv6 subnet but are very

helpful. They serve to spread additional information on the IPv6 subnet, i.e. IPv6 address of

the DNS server and the domain used. The DNS server even may be published in two ways.

Because diﬀerent systems have diﬀerent preferences it is of advantage to activate both methods

(RDNSS via router advertisements and DHCPv6).

Test

The whole IPv6-conﬁguration of this example (DNS_SUPPORT_IPV6='yes' is assumed!) looks

like this:

IPV6_NET_N='1'

IPV6_NET_1='0:0:0:456::1/64' # IPv6-address of the routers (without

# Subnet-prefix) + subnet mask

IPV6_NET_1_DEV='eth0' # network interface for this IPv6-subnet

IPV6_NET_1_ADVERTISE='yes' # /64-subnetz-prefix and default-route per RA

IPV6_NET_1_ADVERTISE_DNS='yes' # DNS-server per RA

IPV6_NET_1_DHCP='yes' # Domain-name and DNS-server per DHCPv6

IPV6_TUNNEL_N='1'

IPV6_TUNNEL_1_PREFIX='2001:db8:123::/48' # /48-subnet mask

IPV6_TUNNEL_1_LOCALV4='dynamic' # or fixed local IPv4-address

IPV6_TUNNEL_1_REMOTEV4='212.224.0.188'

IPV6_TUNNEL_1_LOCALV6='2001:db8:900:551::2/64'

IPV6_TUNNEL_1_REMOTEV6='2001:db8:900:551::1'

IPV6_TUNNEL_1_TYPE='sixxs'

IPV6_TUNNEL_1_USERID='USER1-SIXXS'

IPV6_TUNNEL_1_PASSWORD='sixxs'

IPV6_TUNNEL_1_TUNNELID='T1234'

With a ﬂi4l like this a normally conﬁgured Windows 7 host should automatically conﬁgure

its IPv6 address, default route, DNS server and domain and thus make the computer IPv6

capable. This can be veriﬁed e.g. with a simple PING from the Windows host to the IPv6

internet. In the following example we try to reach the ﬂi4l.de webserver from the Windows

PC (we directly use the IPv6 address here to avoid assumption of correct DNS functionality):

C:\>ping 2001:bf0:c000:a::2:132

Ping executed for 2001:bf0:c000:a::2:132 with 32 bytes data:

Answer from 2001:bf0:c000:a::2:132: time=104ms

Answer from 2001:bf0:c000:a::2:132: time=102ms

Answer from 2001:bf0:c000:a::2:132: time=106ms

Ping-Statistics for 2001:bf0:c000:a::2:132:

Packets: Sent = 4, Received = 4, lost = 0 (0% lost),

time in millisecs.:

Minimum = 102ms, Maximum = 106ms, Average = 104ms

Yo can try to use the tool “traceroute” (in Windows: “tracert”) in order to examine whether

a packet is routed correctly. An example from the local network of the author is found below.

365