Softwire Protocols in Computer Networking

Definition and Fundamental Concepts

A softwire in computer networking describes a mechanism that provides a virtualized, transparent connection—functionally equivalent to a dedicated physical wire—by encapsulating one network-layer protocol inside another. Unlike conventional tunneling methods at higher layers, softwire protocols operate at or below the IP layer, preserving the addressing, header structure, and operational semantics of the payload protocol as it transits an incompatible or intermediary network. This transparent encapsulation allows the endpoints to communicate as though they were directly connected, even when separated by heterogeneous infrastructure, such as an IPv6-only provider backbone traversed by IPv4 packets.

The term „softwire“ was first established by the IETF’s Softwires Working Group to distinguish these mechanisms from generic tunnels and overlays, emphasizing standardization, scalability, and transparency as key design criteria.

Origins and Motivation

The introduction of softwire protocols was a direct response to the exhaustion of globally routable IPv4 address space and the slow, complex rollout of IPv6 connectivity. Many network operators faced the challenge of continuing to offer IPv4-based services in environments rapidly transitioning to or already dominated by IPv6. Dual-stack strategies—where both protocol versions operate in parallel—introduced significant operational overhead and failed to address address scarcity. Conventional IP tunneling techniques (e.g., GRE, IP-in-IP) provided some solutions but did not scale to the needs of major ISPs, particularly in terms of management, automation, and state tracking.

In response, the IETF Softwires Working Group was chartered to define standard mechanisms capable of supporting carrier-grade deployments, network migration, and interoperability at scale. The group’s foundational document, RFC 4925, formulated the problem space and articulated the requirements for modern softwire protocols:

RFC 4925 – Softwire Problem Statement: https://datatracker.ietf.org/doc/html/rfc4925

Softwire Protocol Architecture

Softwire protocols are characterized by their encapsulation of complete packets from a “payload” protocol family (such as IPv4) inside packets of a “carrier” protocol family (such as IPv6). The encapsulation process occurs at the ingress node (the softwire initiator), where the payload packet is wrapped in a new header corresponding to the carrier protocol. This encapsulated packet then traverses the transit network, which only needs to route the outer protocol, not being aware of the encapsulated inner protocol. At the egress node (the softwire terminator), the outer header is stripped, and the original payload packet is forwarded to its destination. This procedure is entirely transparent to upper-layer protocols and endpoint devices, which remain unaware of the encapsulation and decapsulation.

Key Architectural Models

Softwire deployments typically follow one of two architectural paradigms:

1. Hub-and-Spoke:
Traffic is funneled through a central gateway or aggregator, known as the hub. This centralization simplifies management, policy enforcement, and address translation. However, it can create bottlenecks and single points of failure.

2. Mesh:
End devices or distributed gateways establish direct softwire tunnels between each other as required, creating a mesh of virtual links. This model eliminates central bottlenecks and supports direct peer-to-peer communication but increases signaling and configuration complexity.

Both models are standardized and have well-documented operational characteristics. See:

RFC 5565 – Softwire Mesh Framework: https://datatracker.ietf.org/doc/html/rfc5565

Softwire Protocol Families and Standards

The IETF has published several open standards defining softwire protocols and their operational frameworks. The most prominent families and their technical characteristics are detailed below.

Dual-Stack Lite (DS-Lite)

DS-Lite was one of the earliest and most influential softwire standards, designed to enable IPv4 connectivity over IPv6-only networks. Customer-premises equipment (CPE) encapsulates IPv4 packets within IPv6, sending them to an Address Family Transition Router (AFTR) in the provider’s core. The AFTR decapsulates and NAT-translates the IPv4 packets for onward routing. DS-Lite centralizes NAT at the provider side (carrier-grade NAT), reducing the IPv4 address requirement per customer.

RFC 6333 – Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion: https://datatracker.ietf.org/doc/html/rfc6333

Lightweight 4over6 (lw4o6)

Lightweight 4over6 is an evolution of DS-Lite, minimizing statefulness and overhead. Each user receives a shared IPv4 address and a unique port set, which allows the provider network to perform stateless IPv4-in-IPv6 encapsulation. The CPE only needs to manage its own port range; state is not maintained for every flow at the AFTR.

RFC 7596 – Lightweight 4over6: An Extension to the Dual-Stack Lite Architecture: https://datatracker.ietf.org/doc/html/rfc7596

MAP-E and MAP-T

Mapping of Address and Port with Encapsulation (MAP-E) is a stateless mechanism that maps IPv4 addresses and ports to IPv6 prefixes algorithmically. IPv4 packets are encapsulated in IPv6 for transport. MAP-T uses a similar mapping strategy but translates IPv4 packets into IPv6 at the network layer, rather than encapsulating them. Both mechanisms scale to large networks by avoiding per-customer state in provider devices and can support both hub-and-spoke and mesh topologies.

RFC 7597 – Mapping of Address and Port with Encapsulation (MAP-E): https://datatracker.ietf.org/doc/html/rfc7597
RFC 7599 – Mapping of Address and Port using Translation (MAP-T): https://datatracker.ietf.org/doc/html/rfc7599

IPv6 Rapid Deployment (6rd)

The 6rd protocol allows for stateless IPv6 deployment over existing IPv4 infrastructure. It operates by encapsulating IPv6 packets in IPv4, with stateless address mapping, facilitating fast rollout in networks lacking native IPv6 support.

RFC 5969 – IPv6 Rapid Deployment on IPv4 Infrastructures (6rd): https://datatracker.ietf.org/doc/html/rfc5969

Technical Operation and Functional Details

Encapsulation and Decapsulation

The technical core of every softwire protocol is the process of encapsulation and decapsulation. At the ingress point—commonly the customer-premises equipment (CPE) or a gateway router—an entire packet (for example, an IPv4 datagram) is encapsulated within a new outer header, typically that of IPv6. The resulting packet is then transmitted over the provider’s native network infrastructure, which operates solely on the outer protocol. At the egress point, a provider-operated gateway or router removes the outer header and forwards the restored original packet towards its destination.

This encapsulation method ensures that the payload protocol (for example, IPv4) remains completely unchanged and operationally invisible to the transit network. Intermediate routers, switches, and firewalls process the packets exclusively according to the carrier protocol (for example, IPv6), and are not required to support or be aware of the encapsulated protocol.

Stateless versus Stateful Operation

Softwire protocols are implemented as either stateless or stateful solutions, each with specific implications for scalability, manageability, and operational complexity.

Stateless softwire mechanisms—as found in MAP-E, MAP-T, and 6rd—use deterministic and algorithmic address and port mappings between IPv4 and IPv6 domains. These mappings allow providers to avoid maintaining any per-customer or per-session state within the network. This makes stateless protocols exceptionally scalable and predictable, as all information required for mapping and demapping is embedded in the packet headers themselves and is derived from fixed rules agreed upon during network configuration.

Stateful solutions, such as DS-Lite and, to a lesser degree, lw4o6, require the network operator to maintain a mapping or state table at the provider edge. In DS-Lite, for example, each active flow from a customer’s CPE through the provider’s AFTR must be tracked, as the same IPv4 address may be used by multiple customers. This introduces more complexity but can provide finer-grained control and simplified port allocation management.

Address and Port Mapping

A distinguishing characteristic of modern softwire protocols is the use of precise address and port mapping to maximize the efficient use of scarce IPv4 resources. For instance, in stateless models like MAP-E and lw4o6, each user is assigned a range of ports on a shared IPv4 address, and a corresponding IPv6 prefix or address that encodes this allocation. The mapping allows for correct demultiplexing of packets at both tunnel endpoints, facilitating address sharing and enabling massive scale.

Detailed mapping and algorithmic rules are thoroughly specified in:

RFC 7597 – Mapping of Address and Port with Encapsulation (MAP-E): https://datatracker.ietf.org/doc/html/rfc7597
RFC 7596 – Lightweight 4over6: https://datatracker.ietf.org/doc/html/rfc7596

Path MTU and Fragmentation

Encapsulation increases the size of the transmitted packet, which can result in packets that exceed the maximum transmission unit (MTU) of network segments along the path. When the combined size of the original payload and the encapsulating header exceeds the available MTU, packets may be fragmented or dropped. This can impair performance or break applications if not managed correctly.

Best practice dictates rigorous adherence to Path MTU Discovery (PMTUD) protocols and correct handling of “ICMP Packet Too Big” messages to inform senders of the need to reduce packet size. The relevant operational and security recommendations are outlined in:

RFC 4459 – Recommendations for Addressing Problems with ICMP Packet Too Big Messages: https://datatracker.ietf.org/doc/html/rfc4459


Real-World Applications and Deployment

Softwire protocols have moved from conceptual standards to widespread real-world deployment in a diverse range of scenarios.

Internet Service Providers (ISPs)

Global ISPs have adopted softwire solutions, particularly DS-Lite and lw4o6, to deliver IPv4 Internet access to end-users over IPv6-only access networks. This strategy enables providers to modernize their core infrastructure, reduce operational complexity, and centralize Network Address Translation (NAT) functionality, thereby conserving public IPv4 addresses and extending the life of legacy IPv4-based services.

For instance, DS-Lite is widely used in fiber-to-the-home and broadband deployments in Asia, Europe, and North America, as documented in various operator case studies and technical whitepapers.

Enterprise and Data Center Networks

Large enterprises and data centers utilize softwire protocols to facilitate staged IPv6 adoption, allowing internal systems to migrate to IPv6 while retaining compatibility with external IPv4 services. Softwire-based tunnels are also used for secure inter-site links, testing environments, and temporary migration scenarios.

Carrier-Grade NAT (CGNAT) and Resource Optimization

Centralized NAT at the provider edge (CGNAT) is a critical feature of softwire deployments, as it allows many customers to share a limited pool of public IPv4 addresses without sacrificing connectivity or session reliability. Address and port mapping strategies implemented by softwire protocols support this sharing efficiently.

Security Considerations in Softwire Deployments

Security remains a pivotal aspect in the design, deployment, and ongoing operation of softwire protocols. The encapsulation of one network protocol within another introduces several unique risks and challenges that must be systematically addressed at each architectural layer. Since softwire tunnels operate at the network layer, encapsulated packets are invisible to the underlying transit infrastructure, which can inhibit traditional network inspection, filtering, and enforcement mechanisms. This characteristic presents both advantages and disadvantages. On the one hand, encapsulation can protect tunneled traffic from certain forms of interception or manipulation by intermediate devices that are only aware of the outer protocol. On the other hand, the same invisibility can be exploited by attackers to bypass firewalls, intrusion detection systems, or policy engines that do not inspect the encapsulated payload.

A significant concern involves unauthorized access to the tunnel endpoints. If an attacker gains access to a softwire’s ingress or egress node, it becomes possible to inject or intercept traffic that will be decapsulated and routed with the privileges of the original protocol. This scenario may facilitate man-in-the-middle attacks, session hijacking, or data exfiltration. Therefore, robust authentication and authorization mechanisms must be enforced at tunnel endpoints. Industry practice recommends the deployment of access control lists, network segmentation, and, where supported, cryptographic authentication of tunnel participants.

Another aspect is susceptibility to denial-of-service (DoS) attacks, which can be amplified by the softwire infrastructure. For instance, an attacker may flood the softwire tunnel with oversized or malformed packets, consuming processing resources at the encapsulation and decapsulation points. In stateless softwire designs, an adversary may exploit address and port mappings to generate large volumes of traffic targeting shared resources, potentially overwhelming shared IPv4 address pools. Defensive strategies include rigorous traffic monitoring, rate limiting, anomaly detection, and isolation of critical infrastructure components.

Softwire encapsulation also has implications for path MTU discovery and fragmentation-based attacks. Because the encapsulated packet is larger than the original, misconfigurations or inadequate handling of ICMP “Packet Too Big” messages can result in persistent blackholing of traffic or facilitate deliberate fragmentation attacks. It is essential that all network devices involved in the softwire path are configured to correctly handle and propagate MTU-related control messages, as prescribed in RFC 4459 (https://datatracker.ietf.org/doc/html/rfc4459).

Operators must also consider the interplay between softwire protocols and other forms of network address translation or stateful inspection. For example, the use of carrier-grade NAT in DS-Lite deployments requires careful synchronization of state between the softwire endpoint and the NAT function, to prevent address exhaustion, port conflicts, or session drops. Stateless protocols such as MAP-E and MAP-T avoid these pitfalls by construction, but they shift responsibility for correct mapping to the network design phase, requiring deterministic configuration and thorough documentation.

In summary, security in softwire deployments is multi-faceted. It must address endpoint authentication, traffic integrity, resource protection, and compatibility with existing monitoring and enforcement frameworks. Comprehensive testing, documentation, and ongoing vigilance are required to ensure that the operational benefits of softwire technologies are not undermined by preventable vulnerabilities.

Implementation and Interoperability

The adoption of softwire protocols is supported by a mature ecosystem of open-source and commercial networking platforms. Most modern router operating systems—such as Cisco IOS, Juniper Junos, and Nokia SR OS—offer native support for standardized softwire mechanisms, including DS-Lite, MAP-E, MAP-T, lw4o6, and 6rd. These implementations are regularly updated to reflect the latest IETF standards and to ensure compatibility across multi-vendor environments.

In the open-source domain, platforms like FRRouting (FRR), BIRD, and the Linux kernel itself provide robust support for the relevant tunneling and encapsulation primitives. The Linux kernel, for example, implements IP-in-IP tunneling (for both IPv4 and IPv6), Generic Routing Encapsulation (GRE), and basic support for encapsulated address and port mapping as required by softwire standards. Additional user-space tools and configuration frameworks, such as OpenWRT for customer-premises equipment, further extend the accessibility and flexibility of softwire deployments.

Interoperability is a cornerstone of softwire technology. Because the IETF has specified all major softwire protocols as open standards, multi-vendor and heterogeneous network environments can leverage softwire mechanisms without fear of lock-in or proprietary incompatibilities. The relevant RFCs are meticulously detailed, specifying not only packet formats and protocol behavior but also operational practices, error handling, and interoperability scenarios. This rigorous specification process has facilitated wide-scale adoption and real-world interoperability, as evidenced by successful deployments in tier-one ISPs and large enterprise networks worldwide.

Despite this maturity, practical deployment often reveals edge cases and subtleties not fully addressed in the base specifications. For example, providers must ensure that IPv6 addresses or prefixes used in stateless mapping schemes do not conflict with existing allocations, and that all participating devices interpret mapping rules identically. During migration periods, hybrid environments may require support for both stateless and stateful tunneling, as well as fallback mechanisms for legacy clients.

Testing and certification programs, such as those run by the Broadband Forum and other industry groups, provide additional validation for softwire implementations. These programs establish test suites, reference topologies, and validation tools to ensure that equipment from different vendors can operate together seamlessly under production conditions. Such efforts are essential for maintaining the reliability and predictability of softwire-based infrastructure as the Internet’s protocol mix continues to evolve.

Deployment Experiences and Operational Challenges

Field experience with softwire protocols has revealed both strengths and challenges. On the positive side, ISPs report that softwire technologies enable the efficient rollout of IPv6 without disrupting existing IPv4-based customer services. Centralized NAT, made possible by DS-Lite and lw4o6, simplifies address management and facilitates regulatory compliance, especially in jurisdictions that require tracking of user sessions or preservation of connection metadata. Stateless protocols, like MAP-E and MAP-T, are praised for their scalability and deterministic behavior, which greatly simplifies planning for large subscriber bases.

However, operational challenges do occur. Incorrectly configured mapping rules or inconsistent state synchronization between softwire endpoints can result in routing loops, address leakage, or unintentional denial of service. Some applications that rely on incoming connections (such as peer-to-peer or VoIP) may experience difficulties when sharing IPv4 addresses and ports, especially in stateless mapping regimes where port ranges are strictly partitioned. To mitigate these issues, many providers supplement their softwire deployments with application-layer gateways, explicit configuration guidance for customers, and detailed network monitoring.

Performance tuning is another area of focus. Encapsulation adds processing overhead at both tunnel endpoints, and inadequate hardware resources may become a bottleneck in high-throughput scenarios. Advanced platforms employ hardware acceleration for encapsulation and decapsulation, minimizing latency and maximizing throughput. Where possible, providers deploy softwire endpoints in a geographically distributed manner, reducing transit distances and improving performance for end-users.

Finally, operator feedback consistently underscores the importance of careful planning, rigorous testing, and continuous operational monitoring. The success of softwire deployments is closely tied to the quality of documentation, staff training, and the ability to rapidly diagnose and resolve interoperability or performance issues as they arise.

Key Softwire Protocol Families

Dual-Stack Lite (DS-Lite)

Dual-Stack Lite represents a seminal advancement in the design of IPv4-over-IPv6 softwire protocols. DS-Lite enables service providers to deploy IPv6-only infrastructure in their core and access networks while continuing to deliver IPv4 connectivity to end customers. In this approach, each customer-premises equipment (CPE) device operates exclusively with an IPv6 WAN interface. When a customer device generates IPv4 traffic, the CPE encapsulates each IPv4 packet within an IPv6 packet. These encapsulated packets are then forwarded to a centralized Address Family Transition Router (AFTR), typically operated within the provider’s core data center.

The AFTR performs two critical roles: it decapsulates the IPv4 packet, restoring it to its native form, and it implements a large-scale Network Address Translation (NAT44) function for all customers using IPv4. This design centralizes the NAT state, simplifies IPv4 address management, and allows providers to conserve public IPv4 addresses, as many subscribers can be served from a limited address pool. However, it also introduces a dependency on the AFTR as a critical network component. Scalability, redundancy, and failure recovery must be carefully engineered to avoid bottlenecks or single points of failure. DS-Lite is particularly suited to environments where public IPv4 addresses are exhausted and IPv6 deployment is advanced. Its real-world adoption is widespread, as documented in RFC 6333.

Lightweight 4over6 (lw4o6)

Lightweight 4over6 builds upon the concepts established by DS-Lite, specifically addressing state management and NAT overhead. In lw4o6, each subscriber receives a shared public IPv4 address in combination with a unique port set, which is encoded in the configuration of both CPE and provider-side Border Relay (BR) routers. Unlike DS-Lite, the provider infrastructure no longer requires per-flow NAT state for each subscriber; instead, the state is distributed and limited to port set assignments. The encapsulation and decapsulation processes remain similar, but scalability is improved and per-subscriber isolation is strengthened. Lightweight 4over6 is particularly well-suited to ISPs with very large customer bases, as the reduction of per-customer state dramatically lowers operational overhead. Comprehensive technical guidance and deployment scenarios are described in RFC 7596.

Mapping of Address and Port with Encapsulation (MAP-E)

MAP-E introduces a fundamentally stateless approach to IPv4-over-IPv6 softwire communication. It achieves this through algorithmic mapping rules that deterministically assign each subscriber a specific IPv4 address and port range, paired with an IPv6 prefix. Every participating device implements the same mapping logic, eliminating the need for any shared session or address state in the provider infrastructure. When a CPE device needs to transmit IPv4 traffic, it encapsulates it within IPv6 and sends it across the provider network; the decapsulating device at the far end applies the same mapping to correctly deliver or route the original packet. MAP-E thus enables massive scalability, resilience to endpoint failures, and simple recovery from configuration loss. However, port range limitations may impact some advanced use cases, such as hosting multiple incoming connections or certain real-time applications. Detailed protocol specification is available in RFC 7597.

Mapping of Address and Port using Translation (MAP-T)

MAP-T employs a similar mapping principle as MAP-E but utilizes translation rather than encapsulation. When a CPE device transmits IPv4 traffic, the packet is algorithmically mapped and translated into IPv6, traverses the provider network natively, and is then reverse-mapped and translated back to IPv4 at the receiving edge. This stateless, deterministic translation avoids the overhead and complexity of encapsulation while maintaining the same address and port mapping benefits. MAP-T is optimal for operators seeking to maximize performance and simplicity, particularly in environments with modern IPv6-capable equipment and applications. The protocol and its deployment models are detailed in RFC 7599.

IPv6 Rapid Deployment (6rd)

The 6rd mechanism was designed to expedite IPv6 deployment by leveraging existing IPv4 infrastructure. Instead of relying on softwire encapsulation for IPv4-over-IPv6, 6rd operates in the reverse direction, encapsulating IPv6 packets within IPv4. This allows ISPs to rapidly extend IPv6 connectivity to customers before full dual-stack or native IPv6 is available throughout their infrastructure. 6rd operates in a stateless manner and is typically implemented as a transition or interim solution. Its architecture, use cases, and configuration requirements are described in RFC 5969.


Practical Fields of Application

Softwire protocols are implemented in a wide range of networking scenarios, far beyond basic IPv4/IPv6 coexistence. In the telecommunications sector, softwire technologies enable large-scale ISPs to migrate core and access networks to IPv6 without disrupting legacy services. In the enterprise, they support staged migrations, hybrid cloud integration, and legacy application preservation. In data center and cloud environments, softwire tunnels can bridge segmented virtual networks, provide secure interconnects, or enable multi-protocol connectivity for containers and virtual machines.

Additionally, softwire solutions are instrumental in regulatory compliance and lawful interception. By centralizing NAT and providing deterministic mappings, they enable providers to track and log user sessions as required by legal frameworks in many jurisdictions. This is particularly important where address sharing complicates attribution of network activity to individual subscribers.

Performance optimization is another key domain. By offloading NAT and encapsulation to high-performance hardware or distributed edge devices, providers can reduce latency, increase throughput, and improve overall service quality for end-users. These optimizations are essential in highly competitive markets and for emerging low-latency applications, such as gaming or real-time communications.


Outlook and Future Development

The continued evolution of Internet protocol infrastructure will further increase the importance of softwire concepts. As IPv6 adoption accelerates globally, legacy IPv4-based services will persist for many years, especially in regions with significant installed bases of consumer and industrial equipment. Softwire mechanisms provide the technical foundation for this period of coexistence, allowing seamless interworking and gradual migration.

Ongoing research and standardization efforts address new challenges, such as integrating softwire logic with programmable data planes (e.g., P4, SDN), enhancing automation for tunnel setup and management, and improving security against increasingly sophisticated attacks. Emerging paradigms like segment routing, multi-access edge computing, and virtualized network functions may also leverage softwire techniques for flexible, on-demand protocol translation and encapsulation.

It is expected that future networking equipment will support even more granular and dynamic softwire instantiations, perhaps orchestrated by intent-driven controllers or AI-assisted management systems. These advances will further reduce the operational burden of protocol migration, optimize resource utilization, and enhance the overall robustness and adaptability of global Internet infrastructure.


References

Wie hilfreich war dieser Beitrag?

Klicke auf die Sterne um zu bewerten!

Es tut uns leid, dass der Beitrag für dich nicht hilfreich war!

Lasse uns diesen Beitrag verbessern!

Wie können wir diesen Beitrag verbessern?

Meroth IT-Service ist Ihr lokaler IT-Dienstleister in Frankfurt am Main für kleine Unternehmen, Selbstständige und Privatkunden


Kostenfreie Ersteinschätzung Ihres Anliegens?

❱ Nehmen Sie gerne Kontakt auf ❰

Werbung

SYNOLOGY Rackstattion RS422+ mit 4 Bays
SYNOLOGY Rackstattion RS422+ mit 4 Bays*
€ 629,00
Auf Lager
Preise inkl. MwSt., zzgl. Versandkosten
€ 659,90
Preise inkl. MwSt., zzgl. Versandkosten
€ 699,99
Preise inkl. MwSt., zzgl. Versandkosten
Canon MAXIFY GX7150 kompakter Büro-Drucker – Farbdrucker & Scanner All-in-One WLAN | MegaTank Tintenstrahldrucker mit Kopierer & Scanner | Wi-Fi, Ethernet & USB-Anschluss
Canon MAXIFY GX7150 kompakter Büro-Drucker – Farbdrucker & Scanner All-in-One WLAN | MegaTank Tintenstrahldrucker mit Kopierer & Scanner | Wi-Fi, Ethernet & USB-Anschluss*
€ 622,22
Auf Lager
Preise inkl. MwSt., zzgl. Versandkosten
TP-Link TL-WPA7817 KIT Powerline Adapter WLAN, AV1000, WiFi 6 AX1500 Dualband, Gigabit Ethernet, Plug & Play, Kompatibel mit Allen HomePlug AV/AV2 Powerline Adaptern
TP-Link TL-WPA7817 KIT Powerline Adapter WLAN, AV1000, WiFi 6 AX1500 Dualband, Gigabit Ethernet, Plug & Play, Kompatibel mit Allen HomePlug AV/AV2 Powerline Adaptern*
€ 76,92
Auf Lager
Preise inkl. MwSt., zzgl. Versandkosten
Synology DS224+ 2-Bay Diskstation NAS (Intel Celeron J4125 4-Core 2.0 GHz 2GB DDR4 RAM 2xRJ-45 1GbE LAN-Port) 16 TB Bundle mit 2 x 8 TB Seagate IronWolf NAS HDDs (ST8000VN004)
Synology DS224+ 2-Bay Diskstation NAS (Intel Celeron J4125 4-Core 2.0 GHz 2GB DDR4 RAM 2xRJ-45 1GbE LAN-Port) 16 TB Bundle mit 2 x 8 TB Seagate IronWolf NAS HDDs (ST8000VN004)*
€ 795,00
Auf Lager
Preise inkl. MwSt., zzgl. Versandkosten
Canon PIXMA TS8750 Multifunktionsdrucker 3in1 (Tintenstrahl,Drucken, Kopieren, Scannen, A4, 10,8 cm Touch LCD, WLAN, Duplexdruck, 2 Papierzuführungen, 2 x 100 Blatt, 6 Separate Tinten) schwarz
Canon PIXMA TS8750 Multifunktionsdrucker 3in1 (Tintenstrahl,Drucken, Kopieren, Scannen, A4, 10,8 cm Touch LCD, WLAN, Duplexdruck, 2 Papierzuführungen, 2 x 100 Blatt, 6 Separate Tinten) schwarz*
UVP**: € 289,00
€ 177,94
Auf Lager
Preise inkl. MwSt., zzgl. Versandkosten
€ 219,99
Preise inkl. MwSt., zzgl. Versandkosten
TP-Link WLAN Powerline Adapter TL-WPA4220 WLAN 300Mbit/s, AV600 Powerline, Zusatzeinheit, Es kann nicht alleine verwendet werden
TP-Link WLAN Powerline Adapter TL-WPA4220 WLAN 300Mbit/s, AV600 Powerline, Zusatzeinheit, Es kann nicht alleine verwendet werden*
UVP**: € 44,90
€ 41,53
Auf Lager
Preise inkl. MwSt., zzgl. Versandkosten
Synology DS224+ 2-Bay Diskstation NAS (Intel Celeron J4125 4-Core 2.0 GHz 2GB DDR4 RAM 2xRJ-45 1GbE LAN-Port) 8 TB Bundle mit 2X HAT3300-4T
Synology DS224+ 2-Bay Diskstation NAS (Intel Celeron J4125 4-Core 2.0 GHz 2GB DDR4 RAM 2xRJ-45 1GbE LAN-Port) 8 TB Bundle mit 2X HAT3300-4T*
€ 515,00
Preise inkl. MwSt., zzgl. Versandkosten
€ 614,95
Preise inkl. MwSt., zzgl. Versandkosten
UGREEN Revodok USB C Hub PD100W, 4K HDMI, 3*USB A Datenports USB C Adapter Multiportadapter kompatibel mit iPhone 16, Galaxy S24, Surface, MacBook Pro/Air, iPad Pro/Air, Steam Deck usw.
UGREEN Revodok USB C Hub PD100W, 4K HDMI, 3*USB A Datenports USB C Adapter Multiportadapter kompatibel mit iPhone 16, Galaxy S24, Surface, MacBook Pro/Air, iPad Pro/Air, Steam Deck usw.*
UVP**: € 16,99
€ 12,99
Auf Lager
Preise inkl. MwSt., zzgl. Versandkosten
Fritz!Box 7590 AX Exclusive Edition Bundle mit Crucial X9 1TB Externe SSD Festplatte (Wi-Fi 6 DSL-Router 2.400 MBit/s (5GHz) & 1.200 MBit/s (2,4 GHz), WLAN Mesh,DECT-Basis)
Fritz!Box 7590 AX Exclusive Edition Bundle mit Crucial X9 1TB Externe SSD Festplatte (Wi-Fi 6 DSL-Router 2.400 MBit/s (5GHz) & 1.200 MBit/s (2,4 GHz), WLAN Mesh,DECT-Basis)*
€ 327,64
Auf Lager
Preise inkl. MwSt., zzgl. Versandkosten
Canon PIXMA PRO-200 Farbtintenstrahldrucker Fotodrucker DIN A3+ (Hochglanzdruck, WLAN, USB 2.0, WiFi, LAN, Print App, 7,5 cm LCD Farbdisplay, 4.800 x 2.400 DPI, 8 Separate Druckertinten), grau
Canon PIXMA PRO-200 Farbtintenstrahldrucker Fotodrucker DIN A3+ (Hochglanzdruck, WLAN, USB 2.0, WiFi, LAN, Print App, 7,5 cm LCD Farbdisplay, 4.800 x 2.400 DPI, 8 Separate Druckertinten), grau*
€ 627,00
Gewöhnlich versandfertig in 9 bis 10 Tagen
Preise inkl. MwSt., zzgl. Versandkosten
Brother HL-L5210DN Laserdrucker schwarz weiß (A4, 48 Seiten/Min., 1.200x1.200 DPI, LAN, Duplex, 250 Blatt Papierkassette) weiß/grau
Brother HL-L5210DN Laserdrucker schwarz weiß (A4, 48 Seiten/Min., 1.200x1.200 DPI, LAN, Duplex, 250 Blatt Papierkassette) weiß/grau*
UVP**: € 219,00
€ 199,90
Auf Lager
Preise inkl. MwSt., zzgl. Versandkosten
€ 232,99
Preise inkl. MwSt., zzgl. Versandkosten
€ 529,00
Preise inkl. MwSt., zzgl. Versandkosten
UGREEN USB C Hub 10 Gbps, Adapter mit 4*USB C 3.2 Ports, Hochgeschwindigkeits USB C Multiport Splitter für iPhone 16 Serie, Galaxy S24, MacBook Pro, iMac, iPad Pro, Chromebook und mehr
UGREEN USB C Hub 10 Gbps, Adapter mit 4*USB C 3.2 Ports, Hochgeschwindigkeits USB C Multiport Splitter für iPhone 16 Serie, Galaxy S24, MacBook Pro, iMac, iPad Pro, Chromebook und mehr*
UVP**: € 17,99
€ 13,98
Auf Lager
Preise inkl. MwSt., zzgl. Versandkosten
HP Color Laser 150nw Farb-Laserdrucker (Drucker, USB, LAN, WLAN),weiß-grau
HP Color Laser 150nw Farb-Laserdrucker (Drucker, USB, LAN, WLAN),weiß-grau*
UVP**: € 279,90
€ 206,49
Auf Lager
Preise inkl. MwSt., zzgl. Versandkosten
€ 199,95
Preise inkl. MwSt., zzgl. Versandkosten
€ 226,99
Preise inkl. MwSt., zzgl. Versandkosten
TP-Link RE500X WiFi 6 WLAN Verstärker Repeater AX1500(Dualband 1200MBit/s 5GHz + 300MBit/s 2,4GHz, Tri-Core 1,5 GHz CPU, Gigabit Port, maximale Abdeckung, kompatibel zu allen WLAN Routern)weiß
TP-Link RE500X WiFi 6 WLAN Verstärker Repeater AX1500(Dualband 1200MBit/s 5GHz + 300MBit/s 2,4GHz, Tri-Core 1,5 GHz CPU, Gigabit Port, maximale Abdeckung, kompatibel zu allen WLAN Routern)weiß*
UVP**: € 79,90
€ 32,99
Auf Lager
Preise inkl. MwSt., zzgl. Versandkosten
€ 79,95
Preise inkl. MwSt., zzgl. Versandkosten
HP Laptop | 15,6
HP Laptop | 15,6" FHD Display | Intel Celeron N4500 | 4 GB DDR4 RAM | 128 GB SSD | Intel UHD Graphics | Windows 11 Home im S-Modus | QWERTZ Tastatur | Silber | inkl. Microsoft Office 365 Single*
UVP**: € 299,00
€ 232,00
Auf Lager
Preise inkl. MwSt., zzgl. Versandkosten
Synology DS224+ 2-Bay Diskstation NAS (Intel Celeron J4125 4-Core 2.0 GHz 2GB DDR4 RAM 2xRJ-45 1GbE LAN-Port) 16 TB Bundle mit 2X HAT3310-8T
Synology DS224+ 2-Bay Diskstation NAS (Intel Celeron J4125 4-Core 2.0 GHz 2GB DDR4 RAM 2xRJ-45 1GbE LAN-Port) 16 TB Bundle mit 2X HAT3310-8T*
€ 849,00
Auf Lager
Preise inkl. MwSt., zzgl. Versandkosten
(*) Werbung / Affiliate-Links: Wenn Sie auf einen dieser Links klicken und einkaufen, erhalte ich eine Provision. Für Sie verändert sich der Preis dadurch nicht. Zuletzt aktualisiert am 15. Juli 2025 um 13:58. Die hier gezeigten Preise können sich zwischenzeitlich auf der Seite des Verkäufers geändert haben. Alle Angaben ohne Gewähr.
(**) UVP: Unverbindliche Preisempfehlung

Preise inkl. MwSt., zzgl. Versandkosten
Nach oben scrollen