<!DOCTYPE html
SYSTEM "about:legacy-compat">
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2023"><meta name="DC.rights.owner" content="(C) Copyright 2023"><meta name="DC.type" content="concept"><meta name="description" content="IPv6 (Internet Protocol version 6) is the successor to the most common Internet Protocol today (IPv4)."><meta name="prodname" content="All Mediatrix Units"><meta name="version" content="DGW 49.12.28842941"><meta name="platform" content=""><meta name="DC.date.modified" content="2023-0308-2809"><meta name="DC.date.issued" content="2023-0308-2809"><meta name="DC.date.available" content="2023-0308-2809"><meta name="ChapterNumbering" content="no"><meta name="DC.format" content="HTML5"><meta name="DC.identifier" content="concept_f14_1fs_b1b"><link href="https://fonts.googleapis.com/css?family=Open+Sans" rel="stylesheet"><link rel="stylesheet" type="text/css" href="https://documentation.media5corp.com/download/attachments/45482024/commonltr.css"><link rel="stylesheet" type="text/css" href="https://documentation.media5corp.com/download/attachments/45482024/custom.css"><title>IPv6 Availability</title></head><body><header role="banner"><div class="topicmeta title">IPv6 Availability</div><div class="topicmeta date">2023-0308-28<09</div><div class="topicmeta product">All Mediatrix Units</div><div class="topicmeta version">DGW 49.12.2884<2941</div><div class="topicmeta pdf"><a href="https://documentation.media5corp.com/download/attachments/45482024/IPv6%20Availability.pdf" rel="nofollow">Download PDF Document</a></div><hr><span style="float: inline-end;"></span></header><nav role="toc"><ul><li><a href="#concept_f14_1fs_b1b">IPv6</a><ul><li><a href="#reference_jcq_tds_b1b">IPv6 Availability</a></li></ul></li><li><a href="#concept_wbj_gts_b1b">IPv6 link-local Addresses</a><ul><li><a href="#task_zgd_trs_b1b">Locating the Scope Identifier of fe80 IPv6 Addresses on Windows</a></li><li><a href="#unique_856238011167256257">Locating the Scope Identifier of fe80 IPv6 Addresses on Linux</a></li></ul></li><li><a href="#concept_v4k_q3h_1r">DGW Documentation</a></li><li><a href="#concept_fqm_rv4_k4">Copyright Notice</a></li></ul></nav><main role="main"><article role="article" aria-labelledby="ariaid-title1"><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="nested0" aria-labelledby="ariaid-title1" id="concept_f14_1fs_b1b">
<h1 class="title topictitle1" id="ariaid-title1">IPv6</h1>
<div class="body conbody"><p class="shortdesc">IPv6 (Internet Protocol version 6) is the successor to the most common Internet Protocol
today (IPv4).</p>
<p class="p">This is largely driven by the fact that IPv4 32-bit addresses are quickly being consumed by the
ever-expanding sites and products on the Internet. IPv6 128-bit address space should not have
this problem for the foreseeable future. </p>
<p class="p">IPv6 addresses, in addition to being longer, are distinguished from IPv4 addresses by the use
of colons ":", e.g. 2001:470:8929:4000:201:80ff:fe3c:642f. An IPv4 address is noted by 4 sets of
decimal numbers separated by periods ".", e.g. 192.168.10.1. </p>
<p class="p">Please note that IPv6 addresses should be written between [ ] to allow port numbers to be set. </p>
<p class="p">For instance, [fd0f:8b72:5::1]:5060.</p>
</div>
<hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested1" aria-labelledby="ariaid-title2" id="reference_jcq_tds_b1b">
<h2 class="title topictitle2" id="ariaid-title2">IPv6 Availability</h2>
<div class="body refbody">
<section class="section">DGW supports IPv6 except for:</section>
<section class="section">
<ul class="ul" id="reference_jcq_tds_b1b__ul_rrr_ry4_f1b">
<li class="li">CPE WAN Management Protocol (CWMP)/TR-069</li>
<li class="li">DHCP embedded sever</li>
<li class="li">IP Routing</li>
<li class="li">Local Firewall (LFW)</li>
<li class="li">Network Firewall (NFW)</li>
<li class="li">Network Address Translation (NAT)</li>
<li class="li">Online Certificate Status Protocol (OSCP)</li>
<li class="li">Remote Authentication Dial In User Services (RADIUS)</li>
<li class="li">Session Border Controller (SBC)</li>
<li class="li">Simple Network Management Protocol (SNMP)</li>
<li class="li">PPPoE</li>
</ul>
</section>
</div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested0" aria-labelledby="ariaid-title3" id="concept_wbj_gts_b1b">
<h1 class="title topictitle1" id="ariaid-title3">IPv6 link-local Addresses</h1>
<div class="body conbody"><p class="shortdesc">IPv6 link-local addresses start with fe80 and must include the scope
identifier</p>
<p class="p">Therefore, the format of a link-local address is: [IPv6 link-local%ScopeIdentifier].</p>
<div class="p">The scope identifier corresponds to: <ul class="ul" id="concept_wbj_gts_b1b__ul_ajy_rxs_b1b">
<li class="li">On Windows: the network link used to contact the IPv6 link-local address.</li>
<li class="li">On Linux: the link name or the interface number.</li>
</ul></div>
<p class="p">For example, if the unit must contact a server at the IPv6 link-local fe80::201:80ff:fe3c:642f
address, you must check on which network link the server is available. Some units have WAN or
LAN. If it is on the WAN link, the IP address would then be "[fe80::201:80ff:fe3c:642f%wan]".</p>
</div>
<hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title4" id="task_zgd_trs_b1b">
<h2 class="title topictitle2" id="ariaid-title4">Locating the Scope Identifier of fe80 IPv6 Addresses on Windows</h2>
<div class="body taskbody">
<section class="section context"><div class="tasklabel"><strong class="sectiontitle tasklabel">Context</strong></div>
<div class="note important note_important"><span class="note__title">IMPORTANT:</span> If the Mediatrix unit is configured to use IPv6 addresses and the
firmware is downgraded to a version that does not support IPv6, then all IPv6
networks are deleted.</div>
</section>
<section id="task_zgd_trs_b1b__steps_kwt_zrs_b1b"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_zgd_trs_b1b__steps_kwt_zrs_b1b"><li class="li step stepexpand">
<span class="ph cmd">Open the Windows Command Line interface.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Type <span class="keyword wintitle">ipconfig</span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Locate the IPv6 address. </span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> The IPv6 address starts with fe80.</div>
</div>
</li><li class="li step stepexpand">
<span class="ph cmd">Locate the interface number in the IPv6 address.</span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> the interface number is at the end of the address, after the %.</div>
</div>
</li></ol></section>
<section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div> In the following example, the interface number of the [fe80::201:80ff:fe3c:642f%4]
IPv6 address is 4.<br><img class="image" id="task_zgd_trs_b1b__image_xdb_1vs_b1b" src="https://documentation.media5corp.com/download/attachments/45482024/IPv6addressWindows.png" width="700"><br></section>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title5" id="unique_856238011167256257">
<h2 class="title topictitle2" id="ariaid-title5">Locating the Scope Identifier of fe80 IPv6 Addresses on Linux</h2>
<div class="body taskbody">
<section class="section context"><div class="tasklabel"><strong class="sectiontitle tasklabel">Context</strong></div>
<div class="note important note_important"><span class="note__title">IMPORTANT:</span> If the Mediatrix unit is configured to use IPv6 addresses and the
firmware is downgraded to a version that does not support IPv6, then all IPv6
networks are deleted.</div>
</section>
<section id="unique_856238011167256257__steps_kwt_zrs_b1b"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="unique_856238011167256257__steps_kwt_zrs_b1b"><li class="li step stepexpand">
<span class="ph cmd">Open the Linux Command Line interface.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Type <span class="keyword wintitle">ipconfig</span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Locate the IPv6 address. </span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> The IPv6 address starts with fe80.</div>
</div>
</li><li class="li step stepexpand">
<span class="ph cmd">Locate the interface number in the IPv6 address.</span>
</li></ol></section>
<section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div> In the following example, to contact the IPv6 link-local IPv6 address
"fe80::201:80ff:fe3c:642f", you would use: [fe80::201:80ff:fe3c:642f%2] or
[fe80::201:80ff:fe3c:642f%eth0].<br><img class="image" id="unique_856238011167256257__image_lwz_3vs_b1b" src="https://documentation.media5corp.com/download/attachments/45482024/IPv6addressLinux.png" width="700"><br></section>
</div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested0" aria-labelledby="ariaid-title6" id="concept_v4k_q3h_1r">
<h1 class="title topictitle1" id="ariaid-title6">DGW Documentation</h1>
<div class="body conbody"><p class="shortdesc">Mediatrix devices are supplied with an exhaustive set of documentation. </p>
<p class="p">Mediatrix user documentation is available on the <a class="xref" href="http://documentation.media5corp.com" target="_blank">Media5 Documentation
Portal</a>.</p>
<div class="p">Several types of documents were created to clearly present the information you are looking for.
Our documentation includes:<ul class="ul" id="concept_v4k_q3h_1r__ul_bqy_cjh_1r">
<li class="li"><strong class="ph b">Release notes</strong>: Generated at each GA release, this document includes the known and
solved issues of the software. It also outlines the changes and the new features the release
includes.</li>
<li class="li"><strong class="ph b">Configuration notes</strong>: These documents are created to facilitate the configuration of a
specific use case. They address a configuration aspect we consider that most users will need to
perform. However, in some cases, a configuration note is created after receiving a question
from a customer. They provide standard step-by-step procedures detailing the values of the
parameters to use. They provide a means of validation and present some conceptual information.
The configuration notes are specifically created to guide the user through an aspect of the
configuration. </li>
<li class="li"><strong class="ph b">Technical bulletins</strong>: These documents are created to facilitate the configuration of a
specific technical action, such as performing a firmware upgrade.</li>
<li class="li"><strong class="ph b">Hardware installation guide</strong>: They provide the detailed procedure on how to safely and
adequately install the unit. It provides information on card installation, cable connections,
and how to access for the first time the Management interface.</li>
<li class="li"><strong class="ph b">User guide</strong>: The user guide explains how to customise to your needs the configuration
of the unit. Although this document is task oriented, it provides conceptual information to
help the user understand the purpose and impact of each task. The User Guide will provide
information such as where and how TR-069 can be configured in the Management Interface, how to
set firewalls, or how to use the CLI to configure parameters that are not available in the
Management Interface.</li>
<li class="li"><strong class="ph b">Reference guide</strong>: This exhaustive document has been created for advanced users. It
includes a description of all the parameters used by all the services of the Mediatrix units.
You will find, for example, scripts to configure a specific parameter, notification messages
sent by a service, or an action description used to create Rulesets. This document includes
reference information such as a dictionary, and it does not include any step-by-step
procedures. </li>
</ul></div>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested0" aria-labelledby="ariaid-title7" id="concept_fqm_rv4_k4">
<h1 class="title topictitle1" id="ariaid-title7">Copyright Notice</h1>
<div class="body conbody"><p class="shortdesc">Copyright © 2023 Media5 Corporation.</p>
<p class="p">This document contains information that is proprietary to Media5 Corporation.</p>
<p class="p">Media5 Corporation reserves all rights to this document as well as to the Intellectual Property
of the document and the technology and know-how that it includes and represents.</p>
<p class="p">This publication cannot be reproduced, neither in whole nor in part, in any form whatsoever,
without written prior approval by Media5 Corporation.</p>
<p class="p">Media5 Corporation reserves the right to revise this publication and make changes at any time
and without the obligation to notify any person and/or entity of such revisions and/or
changes.</p>
</div>
</article></article></main></body></html> | 