From f5f273071af913bc5455997828d9917e892e190e Mon Sep 17 00:00:00 2001 From: "Joseph.Rawlings" Date: Mon, 1 Dec 2025 11:27:11 -0500 Subject: [PATCH] feat: expand Proxmox help view with comprehensive IPv4 vs IPv6 comparison, including addressing characteristics, functionalities, and dual-stack configuration guidance --- .../Servers/Proxmox/views/help.blade.php | 192 +++++++++++++++++- 1 file changed, 191 insertions(+), 1 deletion(-) diff --git a/extensions/Servers/Proxmox/views/help.blade.php b/extensions/Servers/Proxmox/views/help.blade.php index 95634a070..85c182edd 100644 --- a/extensions/Servers/Proxmox/views/help.blade.php +++ b/extensions/Servers/Proxmox/views/help.blade.php @@ -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.

-

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.

+

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.

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.

+ +

+ + IPv6 vs IPv4: Understanding the Differences +

+
+

+ 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. +

+ +
+
+

Fundamental Differences

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CharacteristicIPv4IPv6
Address Length32 bits (4 bytes)128 bits (16 bytes)
Address Format192.168.1.1 (dotted decimal)2001:db8::1 (hexadecimal)
Address Space~4.3 billion addresses~340 undecillion addresses
NAT RequirementCommonly required due to address exhaustionNot required (sufficient addresses)
Header Size20 bytes (minimum)40 bytes (fixed)
FragmentationPerformed by routersPerformed by source only
SecurityOptional (IPsec)Built-in (IPsec mandatory)
ConfigurationManual or DHCPSLAAC (Stateless) or DHCPv6
+
+ +
+

Separate and Independent Operation

+
+

+ IPv4 and IPv6 are completely separate protocols: +

+
    +
  • They operate independently on the same network interface (dual-stack)
    • +
  • Each protocol has its own routing table and forwarding logic
    • +
  • IPv4 addresses cannot communicate directly with IPv6 addresses
    • +
  • Both can be assigned to the same network interface simultaneously
    • +
  • Applications must explicitly support IPv6 to use it (IPv4 is the default fallback)
    • +
+
+
+ +
+

Functionalities and Use Cases

+
+
+
+ + IPv4 Functionalities +
+
    +
  • Universal compatibility (all systems support IPv4)
    • +
  • Mature ecosystem with extensive tooling
    • +
  • Required for legacy applications and services
    • +
  • Essential for email (SMTP) and many mail servers
    • +
  • Widely supported by CDNs and hosting providers
    • +
  • Standard for most web hosting and APIs
    • +
  • Required for many third-party integrations
    • +
+
+
+
+ + IPv6 Functionalities +
+
    +
  • Massive address space (no NAT needed)
    • +
  • Improved routing efficiency and performance
    • +
  • Built-in security features (IPsec)
    • +
  • Better support for mobile and IoT devices
    • +
  • Simplified network configuration (SLAAC)
    • +
  • Future-proof for growing internet needs
    • +
  • Reduced latency in some scenarios
    • +
+
+
+
+ +
+

IPv4-Only Services and Compatibility

+
+
+ +
+

Why Some Services Remain IPv4-Only

+

+ Many critical internet services, particularly email and legacy systems, are typically deployed only on IPv4 for compatibility reasons: +

+
    +
  • Email (SMTP/POP3/IMAP): Many mail servers and email providers only accept connections over IPv4 due to legacy infrastructure, spam filtering systems, and compatibility with older mail clients
    • +
  • Legacy Applications: Older software and enterprise applications may not support IPv6 at all
    • +
  • Third-Party APIs: Many external services and APIs only provide IPv4 endpoints
    • +
  • CDN and Hosting: Some content delivery networks and hosting providers have limited IPv6 support
    • +
  • DNS and Infrastructure: Some DNS resolvers and network infrastructure components are IPv4-only
    • +
  • Security Tools: Firewalls, intrusion detection systems, and security appliances may have better IPv4 support
    • +
+

+ Best Practice: 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. +

+
+
+
+
+ +
+

IPv6 Adoption Worldwide

+

+ The following chart from APNIC Labs 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. +

+
+ +

+ Source: APNIC IPv6 Statistics - Asia-Pacific Network Information Centre +

+
+
+ +
+

Dual-Stack Configuration

+
+

+ Dual-stack refers to running both IPv4 and IPv6 simultaneously on the same network interface. This is the recommended approach for maximum compatibility: +

+
    +
  • IPv4 ensures compatibility with all existing services and applications
    • +
  • IPv6 provides future-proofing and access to IPv6-only resources
    • +
  • Applications automatically choose the best protocol (IPv6 preferred, IPv4 fallback)
    • +
  • Both protocols can be configured independently with different gateways and DNS servers
    • +
+ 
# 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
+
+
+
+