feat: expand Proxmox help view with comprehensive IPv4 vs IPv6 comparison, including addressing characteristics, functionalities, and dual-stack configuration guidance
This commit is contained in:
@@ -1538,10 +1538,200 @@ iface vmbr0 inet static
|
||||
The management platform includes an integrated firewall system that can apply rules at the VM level, bridge level, or cluster level.
|
||||
</p>
|
||||
<div class="bg-background-secondary/60 p-3 rounded text-xs text-base/80 space-y-2">
|
||||
<p>Toggling the firewall slider on a NIC tells the backend to recreate that interface definition with the firewall flag enabled. Any rules you define in the UI (direction, action, CIDRs, ports, comments) are stored centrally and rendered to iptables on the node, so you don’t have to craft rule syntax yourself.</p>
|
||||
<p>Toggling the firewall slider on a NIC tells the backend to recreate that interface definition with the firewall flag enabled. Any rules you define in the UI (direction, action, CIDRs, ports, comments) are stored centrally and rendered to iptables on the node, so you don't have to craft rule syntax yourself.</p>
|
||||
<p>The platform automatically maps rules to the correct chains—INPUT for traffic hitting the node, FORWARD for VM-to-VM flows, and OUTPUT for traffic originating from the VM—keeping your policy consistent across the cluster.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<h3 class="text-xl font-semibold mt-6 mb-4 flex items-center gap-2">
|
||||
<x-ri-global-line class="size-5 text-base/60" />
|
||||
IPv6 vs IPv4: Understanding the Differences
|
||||
</h3>
|
||||
<div class="bg-background border border-neutral rounded-lg p-5 mb-4">
|
||||
<p class="text-base/80 mb-4">
|
||||
IPv4 and IPv6 are separate and independent network protocols that operate at the same layer (Layer 3) but use completely different addressing schemes and have distinct characteristics. Understanding their differences is crucial for proper network configuration.
|
||||
</p>
|
||||
|
||||
<div class="space-y-6">
|
||||
<div>
|
||||
<h4 class="text-lg font-semibold mb-3">Fundamental Differences</h4>
|
||||
<table class="w-full border border-neutral rounded-md mb-4">
|
||||
<thead class="bg-background">
|
||||
<tr>
|
||||
<th class="text-left py-3 px-4 font-semibold border-b border-neutral">Characteristic</th>
|
||||
<th class="text-left py-3 px-4 font-semibold border-b border-neutral">IPv4</th>
|
||||
<th class="text-left py-3 px-4 font-semibold border-b border-neutral">IPv6</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody class="text-sm text-base/70">
|
||||
<tr class="border-b border-neutral/20">
|
||||
<td class="py-2 px-4 font-semibold">Address Length</td>
|
||||
<td class="py-2 px-4">32 bits (4 bytes)</td>
|
||||
<td class="py-2 px-4">128 bits (16 bytes)</td>
|
||||
</tr>
|
||||
<tr class="border-b border-neutral/20">
|
||||
<td class="py-2 px-4 font-semibold">Address Format</td>
|
||||
<td class="py-2 px-4"><code>192.168.1.1</code> (dotted decimal)</td>
|
||||
<td class="py-2 px-4"><code>2001:db8::1</code> (hexadecimal)</td>
|
||||
</tr>
|
||||
<tr class="border-b border-neutral/20">
|
||||
<td class="py-2 px-4 font-semibold">Address Space</td>
|
||||
<td class="py-2 px-4">~4.3 billion addresses</td>
|
||||
<td class="py-2 px-4">~340 undecillion addresses</td>
|
||||
</tr>
|
||||
<tr class="border-b border-neutral/20">
|
||||
<td class="py-2 px-4 font-semibold">NAT Requirement</td>
|
||||
<td class="py-2 px-4">Commonly required due to address exhaustion</td>
|
||||
<td class="py-2 px-4">Not required (sufficient addresses)</td>
|
||||
</tr>
|
||||
<tr class="border-b border-neutral/20">
|
||||
<td class="py-2 px-4 font-semibold">Header Size</td>
|
||||
<td class="py-2 px-4">20 bytes (minimum)</td>
|
||||
<td class="py-2 px-4">40 bytes (fixed)</td>
|
||||
</tr>
|
||||
<tr class="border-b border-neutral/20">
|
||||
<td class="py-2 px-4 font-semibold">Fragmentation</td>
|
||||
<td class="py-2 px-4">Performed by routers</td>
|
||||
<td class="py-2 px-4">Performed by source only</td>
|
||||
</tr>
|
||||
<tr class="border-b border-neutral/20">
|
||||
<td class="py-2 px-4 font-semibold">Security</td>
|
||||
<td class="py-2 px-4">Optional (IPsec)</td>
|
||||
<td class="py-2 px-4">Built-in (IPsec mandatory)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="py-2 px-4 font-semibold">Configuration</td>
|
||||
<td class="py-2 px-4">Manual or DHCP</td>
|
||||
<td class="py-2 px-4">SLAAC (Stateless) or DHCPv6</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
|
||||
<div>
|
||||
<h4 class="text-lg font-semibold mb-3">Separate and Independent Operation</h4>
|
||||
<div class="bg-background-secondary border border-neutral rounded-md p-4 mb-4">
|
||||
<p class="text-sm text-base/70 mb-3">
|
||||
<strong>IPv4 and IPv6 are completely separate protocols:</strong>
|
||||
</p>
|
||||
<ul class="list-disc list-inside text-sm text-base/70 space-y-2 ml-2">
|
||||
<li>They operate independently on the same network interface (dual-stack)</li>
|
||||
<li>Each protocol has its own routing table and forwarding logic</li>
|
||||
<li>IPv4 addresses cannot communicate directly with IPv6 addresses</li>
|
||||
<li>Both can be assigned to the same network interface simultaneously</li>
|
||||
<li>Applications must explicitly support IPv6 to use it (IPv4 is the default fallback)</li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div>
|
||||
<h4 class="text-lg font-semibold mb-3">Functionalities and Use Cases</h4>
|
||||
<div class="grid md:grid-cols-2 gap-4 mb-4">
|
||||
<div class="bg-background border border-neutral rounded-md p-4">
|
||||
<h5 class="font-semibold mb-2 text-base/90 flex items-center gap-2">
|
||||
<x-ri-wifi-line class="size-4 text-primary" />
|
||||
IPv4 Functionalities
|
||||
</h5>
|
||||
<ul class="list-disc list-inside text-sm text-base/70 space-y-1">
|
||||
<li>Universal compatibility (all systems support IPv4)</li>
|
||||
<li>Mature ecosystem with extensive tooling</li>
|
||||
<li>Required for legacy applications and services</li>
|
||||
<li>Essential for email (SMTP) and many mail servers</li>
|
||||
<li>Widely supported by CDNs and hosting providers</li>
|
||||
<li>Standard for most web hosting and APIs</li>
|
||||
<li>Required for many third-party integrations</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="bg-background border border-neutral rounded-md p-4">
|
||||
<h5 class="font-semibold mb-2 text-base/90 flex items-center gap-2">
|
||||
<x-ri-global-line class="size-4 text-primary" />
|
||||
IPv6 Functionalities
|
||||
</h5>
|
||||
<ul class="list-disc list-inside text-sm text-base/70 space-y-1">
|
||||
<li>Massive address space (no NAT needed)</li>
|
||||
<li>Improved routing efficiency and performance</li>
|
||||
<li>Built-in security features (IPsec)</li>
|
||||
<li>Better support for mobile and IoT devices</li>
|
||||
<li>Simplified network configuration (SLAAC)</li>
|
||||
<li>Future-proof for growing internet needs</li>
|
||||
<li>Reduced latency in some scenarios</li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div>
|
||||
<h4 class="text-lg font-semibold mb-3">IPv4-Only Services and Compatibility</h4>
|
||||
<div class="bg-warning/10 border border-warning/30 rounded-lg p-4 mb-4">
|
||||
<div class="flex items-start gap-3">
|
||||
<x-ri-information-line class="size-5 text-warning flex-shrink-0 mt-0.5" />
|
||||
<div>
|
||||
<p class="text-sm font-semibold mb-2 text-warning">Why Some Services Remain IPv4-Only</p>
|
||||
<p class="text-sm text-base/70 mb-3">
|
||||
Many critical internet services, particularly email and legacy systems, are typically deployed only on IPv4 for compatibility reasons:
|
||||
</p>
|
||||
<ul class="list-disc list-inside text-sm text-base/70 space-y-1 ml-2">
|
||||
<li><strong>Email (SMTP/POP3/IMAP):</strong> Many mail servers and email providers only accept connections over IPv4 due to legacy infrastructure, spam filtering systems, and compatibility with older mail clients</li>
|
||||
<li><strong>Legacy Applications:</strong> Older software and enterprise applications may not support IPv6 at all</li>
|
||||
<li><strong>Third-Party APIs:</strong> Many external services and APIs only provide IPv4 endpoints</li>
|
||||
<li><strong>CDN and Hosting:</strong> Some content delivery networks and hosting providers have limited IPv6 support</li>
|
||||
<li><strong>DNS and Infrastructure:</strong> Some DNS resolvers and network infrastructure components are IPv4-only</li>
|
||||
<li><strong>Security Tools:</strong> Firewalls, intrusion detection systems, and security appliances may have better IPv4 support</li>
|
||||
</ul>
|
||||
<p class="text-sm text-base/70 mt-3">
|
||||
<strong>Best Practice:</strong> Deploy services on both IPv4 and IPv6 (dual-stack) when possible, but always ensure IPv4 connectivity for maximum compatibility, especially for email and critical business applications.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div>
|
||||
<h4 class="text-lg font-semibold mb-3">IPv6 Adoption Worldwide</h4>
|
||||
<p class="text-sm text-base/70 mb-3">
|
||||
The following chart from <a href="https://stats.labs.apnic.net/ipv6/" target="_blank" rel="noopener noreferrer" class="text-primary hover:underline">APNIC Labs</a> shows the current IPv6 adoption rate across different countries. IPv6 adoption varies significantly by region, with some countries having over 50% adoption while others remain primarily on IPv4.
|
||||
</p>
|
||||
<div class="bg-background border border-neutral rounded-md p-4 mb-4">
|
||||
<iframe
|
||||
src="https://stats.labs.apnic.net/ipv6/"
|
||||
title="IPv6 Adoption Rate by Country"
|
||||
class="w-full border-0 rounded"
|
||||
style="height: 600px; min-height: 600px;"
|
||||
loading="lazy"
|
||||
allow="fullscreen"
|
||||
></iframe>
|
||||
<p class="text-xs text-base/60 mt-2 text-center">
|
||||
Source: <a href="https://stats.labs.apnic.net/ipv6/" target="_blank" rel="noopener noreferrer" class="text-primary hover:underline">APNIC IPv6 Statistics</a> - Asia-Pacific Network Information Centre
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div>
|
||||
<h4 class="text-lg font-semibold mb-3">Dual-Stack Configuration</h4>
|
||||
<div class="bg-background border border-neutral rounded-md p-4 mb-4">
|
||||
<p class="text-sm text-base/70 mb-3">
|
||||
<strong>Dual-stack</strong> refers to running both IPv4 and IPv6 simultaneously on the same network interface. This is the recommended approach for maximum compatibility:
|
||||
</p>
|
||||
<ul class="list-disc list-inside text-sm text-base/70 space-y-1 ml-2 mb-3">
|
||||
<li>IPv4 ensures compatibility with all existing services and applications</li>
|
||||
<li>IPv6 provides future-proofing and access to IPv6-only resources</li>
|
||||
<li>Applications automatically choose the best protocol (IPv6 preferred, IPv4 fallback)</li>
|
||||
<li>Both protocols can be configured independently with different gateways and DNS servers</li>
|
||||
</ul>
|
||||
<pre class="bg-background-secondary p-3 rounded text-xs overflow-x-auto"><code># Example dual-stack configuration (Linux)
|
||||
# IPv4 configuration
|
||||
ifconfig eth0 203.0.113.10 netmask 255.255.255.0
|
||||
route add default gw 203.0.113.1
|
||||
|
||||
# IPv6 configuration (SLAAC or static)
|
||||
ip -6 addr add 2001:db8::100/64 dev eth0
|
||||
ip -6 route add default via 2001:db8::1
|
||||
|
||||
# Both protocols operate independently on the same interface</code></pre>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<!-- RFC Standards Section -->
|
||||
|
||||
Reference in New Issue
Block a user