Study guide
7.2 Wireless Forwarding Modes: Bridge vs Tunnel Mode
HPE Aruba Networking Certified Associate - Campus Access HPE6-A85
Track your progress as you read
Finished sections get a check mark.
1 Introduction: HPE6-A85 Exam Overview
HPE6-A85 Exam Facts and Current Blueprint
2 Chapter 1: Network Stack Fundamentals
1.1 OSI Reference Model and Encapsulation 1.2 TCP/IP Protocol Suite and IP Headers 1.3 Layer 2 Operation, ARP, and 802.1Q Tagging
3 Chapter 2: Physical Connectivity and Host Addressing
2.1 Ethernet Media and Transceiver Standards 2.2 Power over Ethernet (PoE, PoE+, PoE++) Standards and Budgeting 2.3 LLDP, LLDP-MED, and Voice VLAN Configuration 2.4 Host IP Addressing and DHCP Relay Operations
4 Chapter 3: Network Resiliency and Virtualization
3.1 Virtual Switching Framework (VSF) Architecture and Topologies 3.2 VSF Split Detection, Failover, and Auto-Stacking 3.3 Virtual Switching Extension (VSX) Architecture and Operations 3.4 High-Availability Gateways: VRRP and VSX Active-Gateway
5 Chapter 4: AOS-CX Architecture and Switch Operation
4.1 AOS-CX Hardware Portfolio and State Database Architecture 4.2 Network Analytics Engine (NAE) and Automated Telemetry 4.3 AOS-CX Interface Configuration and Port Control 4.4 Link Aggregation (LAG) and LACP Configuration
6 Chapter 5: Layer 2 Protocols and Spanning Tree
5.1 AOS-CX VLAN Configuration and Native VLAN Handling 5.2 Spanning Tree Protocols: STP, RSTP, and MSTP 5.3 Spanning Tree Protections and Loop Prevention 5.4 MAC Address Table Learning, Aging, and Forwarding
7 Chapter 6: Wireless Fundamentals, Standards, and RF
6.1 IEEE 802.11 Standards and Wi-Fi Generations 6.2 RF Fundamentals, Signal Propagation, and Channel Design 6.3 Aruba Access Point Hardware Portfolio and Suffix Conventions 6.4 WLAN Topologies, BSSID/ESSID, and Roaming Standards
8 Chapter 7: Aruba Wireless Architecture and Management
7.1 AOS 10 Architecture and Aruba Central Integration 7.2 Wireless Forwarding Modes: Bridge vs Tunnel Mode 7.3 Automated RF and Client Optimization: AirMatch and ClientMatch 7.4 Secure Wireless Access: WPA3, SAE, and MPSK Implementation
9 Chapter 8: IP Routing Fundamentals and OSPF
8.1 IP Routing Principles and Packet Forwarding 8.2 OSPFv2 Protocol Mechanics and Adjacency Formation 8.3 OSPF Designated Routers and Multi-Area Deployments 8.4 ECMP, Static Routing, and VRF Isolation
10 Chapter 9: Campus Network Security and Segmentation
9.1 DHCP Snooping and Dynamic ARP Inspection 9.2 Port Security and MAC Address Limiting 9.3 ClearPass Policy Management and RADIUS Change of Authorization 9.4 Dynamic Segmentation, User-Based Tunneling, and Policy Enforcement
11 Chapter 10: Authentication, Authorization, and Accounting
10.1 The AAA Framework and Architecture 10.2 802.1X Authentication and EAP Methods 10.3 MAC Authentication and Captive Portal Onboarding 10.4 Administrative Access Control: RADIUS vs TACACS+
12 Chapter 11: Network Management and Telemetry
11.1 Aruba Central Cloud Architecture and Group Configuration 11.2 Zero-Touch Provisioning (ZTP) and Aruba Activate 11.3 AI Insights and Aruba User Experience Insight (UXI) 11.4 Network Telemetry, Streaming APIs, and SNMP/Syslog
13 Chapter 12: Troubleshooting the Solution
12.1 Structured Troubleshooting Methodologies and Scope Isolation 12.2 AOS-CX Layer 2 and Interface Diagnostic Commands 12.3 Layer 3, IP Services, and End-to-End Diagnostics 12.4 Physical-Layer Troubleshooting 12.5 Troubleshooting Wireless Clients and Network Access
14 Chapter 13: Optimizing Performance: QoS, Baselines, and Comparisons
13.1 Quality of Service (QoS) Classification and Marking 13.2 Queuing Algorithms and Congestion Management 13.3 Traffic Policing, Shaping, and Broadcast Rate Limiting 13.4 Establishing a Performance Baseline 13.5 Comparing Results to the Baseline
15 Chapter 14: Plan the Solution
14.1 Analyzing the Current Environment 14.2 Interpreting an Architect's High-Level Design 14.3 Creating a Low-Level Design 14.4 Preparing for Implementation
16 Chapter 15: Validate and Operate the Solution
15.1 Validating the Solution 15.2 Performing Firmware Updates 15.3 Making Basic Ongoing Configuration Changes 15.4 Maintaining Network Documentation
7.2 Wireless Forwarding Modes: Bridge vs Tunnel Mode
Key Takeaways Explain This Topic AI
Bridge mode forwards client traffic directly onto the local access switch VLAN at the AP Ethernet port, minimizing latency and eliminating the need for centralized gateway hardware.
Tunnel mode carries client traffic from APs to an Aruba gateway cluster; AOS 10 campus APs build IPsec tunnels (signaling) and GRE tunnels (client data) to every gateway in the cluster, enabling centralized firewalling and roaming across Layer 3 boundaries.
Mixed forwarding deployments allow organizations to bridge non-sensitive, high-bandwidth traffic (such as Guest or IoT) locally while tunneling corporate and voice traffic to centralized gateways for inspection.
In an AOS 10 gateway cluster, the cluster leader publishes a bucket map, and each tunneled client is anchored to a User Designated Gateway (UDG) with a standby UDG chosen by hashing the client MAC address.
In AOS 10, Gateways are dedicated purely to data-plane policy enforcement and routing, completely freed from managing AP configurations or radio RF algorithms.
Last updated: October 2026
Wireless Forwarding Modes: Bridge vs Tunnel Mode
Quick Summary: In modern enterprise WLAN architectures, the control plane (managed by Aruba Central) is fully decoupled from the data forwarding plane. Network architects can configure traffic forwarding on a per-WLAN (per-SSID) basis using two primary modes: Bridge mode and Tunnel mode . Bridge mode provides local breakout directly onto the access switch VLAN, maximizing throughput and eliminating gateway dependencies. Tunnel mode carries client traffic to Aruba gateways , unlocking centralized Policy Enforcement Firewall (PEF) inspection, micro-segmentation, and seamless roaming across complex Layer 3 campus networks.
The Data Plane Architecture: Decoupling Forwarding from Control
One of the most powerful capabilities of Aruba wireless networks is forwarding flexibility. In traditional legacy networks, all traffic was forced through centralized controllers regardless of destination. In AOS 10, because management and control reside in Aruba Central, the data plane can be tailored specifically to the security and performance requirements of each individual SSID.
An administrator deploying an enterprise campus can choose between:
Bridge Mode (Local Breakout): Decentralized, distributed switching at the network edge.
Tunnel Mode (Gateway-Centric): Centralized encapsulation, stateful inspection, and policy enforcement.
Mixed Mode: Simultaneously running Bridge mode on select SSIDs and Tunnel mode on others from the very same physical access points.
Bridge Mode (Local Breakout Architecture)
In Bridge mode , the access point acts as an intelligent 802.11-to-802.3 bridge. When an associated client transmits an 802.11 wireless data frame, the AP immediately strips the wireless encapsulation, converts the frame into a standard IEEE 802.3 Ethernet frame, tags it with the configured VLAN ID, and forwards it directly out its physical Ethernet uplink port onto the access switch. [Wireless Client] --(802.11)--> [Aruba AP] --(802.3 Tagged VLAN)--> [Access Switch] --> [Local Core / Internet]
Packet Flow and Operational Characteristics
Local Switching: The access switch receives the tagged Ethernet frame on its switch port. All subsequent Layer 2 switching and Layer 3 routing occur within the local wired infrastructure.
Default Gateway & DHCP: The client's default gateway resides on the local wired network (typically a Virtual Switching Framework [VSF] stack or a core switch Virtual Routing and Forwarding [VRF] interface). DHCP requests are serviced by local enterprise DHCP servers or local DHCP relay agents.
VLAN Configuration Requirements: Because traffic breaks out locally, every VLAN associated with a Bridge-mode SSID must be configured and tagged on the upstream switch port connecting to the AP, as well as on all inter-switch trunks up to the default gateway.
Advantages of Bridge Mode
Zero Gateway Dependency: Operates without requiring Aruba Mobility Gateways or gateway hardware licenses, significantly reducing capital expenditure.
Minimal Latency & Maximum Throughput: Traffic takes the most direct physical path to local servers, printers, or direct internet breakouts, avoiding trombone routing across WAN or campus core links.
Optimized WAN Bandwidth: In distributed branch or retail deployments, high-bandwidth traffic (such as video streaming or cloud SaaS applications) exits straight to the local ISP router rather than congesting enterprise WAN or VPN circuits.
Complete Branch Survivability: If WAN connectivity to corporate headquarters or the cloud drops, local clients continue to communicate with local servers, printers, and checkout registers without interruption.
Ideal Use Cases for Bridge Mode
Distributed remote branch offices and retail stores.
High-density student dormitories, hotel guest rooms, or public venues where traffic primarily targets the public Internet.
Environments with limited WAN bandwidth or where local peer-to-peer traffic (e.g., local video rendering or storage) dominates.
Tunnel Mode (Centralized Gateway Forwarding)
In Tunnel mode , client traffic is not placed onto the local access switch VLAN. Instead, the access point carries the client's frames to an Aruba gateway cluster (for example 7000, 7200, 9000, 9100, or 9200 Series gateways using the Mobility persona). In AOS 10, each campus AP builds an IPsec tunnel and a GRE tunnel to every gateway in the cluster , orchestrated by Central: IPsec carries device signaling and broadcast/multicast toward clients, and GRE carries client unicast traffic (AOS 10 TechDocs, "Cluster roles"). [Wireless Client] --(802.11)--> [Aruba AP] ==(GRE Tunnel over L3 Network)==> [Aruba Gateway] --> [PEF / Core]
Packet Flow and Operational Characteristics
Encapsulated Transport: The AP encapsulates client frames in GRE packets addressed to the client's anchor gateway. To the intermediate access and distribution switches, this traffic appears simply as standard unicast IP packets traversing the AP's management VLAN.
Switch Port Simplicity: The access switch port connected to the AP requires only the AP management VLAN . The client VLANs (e.g., VLAN 10 for Corporate, VLAN 20 for Voice) do not exist on the access switch or distribution trunks; they exist exclusively inside the GRE tunnel and at the Gateway!
Centralized Decapsulation: The Aruba Gateway decapsulates the GRE packet, recovers the inner client frame, and processes it through the Policy Enforcement Firewall (PEF) .
Role-Based Inspection: The Gateway inspects traffic bidirectionally at Layers 4 through 7 using stateful packet inspection, deep packet inspection (DPI) application identification, and web content filtering before forwarding the frame onto the campus core network.
Key Advantages of Tunnel Mode
Centralized Security Enforcement (Zero Trust): The Policy Enforcement Firewall (PEF) enforces stateful role-based access control. Unauthorized east-west traffic between clients on the same subnet is blocked at the gateway firewall level.
Seamless Layer 2 Mobility Across Layer 3 Boundaries: In a large campus where access switches are separated by routed Layer 3 boundaries, a wireless client can roam across dozens of buildings. Because client traffic is tunneled back to the central gateway cluster, the client retains its original IP address, default gateway, and open TCP/UDP sessions without requiring complex mobile IP protocols.
Dynamic Segmentation Integration: Enables uniform policy enforcement across both wired and wireless users. Wired switch ports can tunnel traffic to the same Gateway cluster using User-Based Tunneling (UBT), ensuring consistent security policies regardless of connection medium.
Simplified Wired Switch Configuration: Eliminates the need to prune, trunk, and manage dozens of user VLANs across hundreds of edge access switches.
Mixed-Mode Deployments: Balancing Performance and Security
AOS 10 allows network engineers to combine both forwarding models on the same physical access point simultaneously on a per-SSID basis: +-----------------------------------+
- | Aruba Access Point |
- +-----------------------------------+
- / \
- / \
- [Corporate-SSID: Tunnel Mode] [Guest-SSID: Bridge Mode]
- / \
- (GRE Tunnel) (Local L2)
- / \
- v v
- +---------------------+ +-------------------+
- | Aruba Gateway | | Access Switch |
- | (PEF Inspection, | | VLAN 500 |
- | Micro-segmentation) | | (Direct Internet) |
- +---------------------+ +-------------------+
In this highly popular hybrid deployment:
SSID 1: "Corp-Secure" (Tunnel Mode): Employee laptops and confidential corporate devices are tunneled to the campus Gateway cluster. All traffic undergoes stateful PEF inspection, application filtering, and micro-segmentation, preserving enterprise data integrity.
SSID 2: "Guest-Internet" (Bridge Mode): Guest visitors and personal devices break out locally onto a dedicated guest VLAN (e.g., VLAN 500) directly at the access switch. This traffic bypasses the Gateway cluster entirely, saving gateway compute resources, reducing campus core traffic, and routing guest web browsing straight to the internet firewall.
Aruba Gateway Clustering and High Availability
When deploying Tunnel mode in enterprise environments, the Aruba Gateway must not become a single point of failure or performance bottleneck. AOS 10 solves this through Aruba Gateway Clustering .
Cluster Architecture and Operational Mechanisms
A cluster of one or more gateways: Even a single gateway is treated as a cluster in AOS 10. One gateway is elected cluster leader ; it assigns roles and computes the bucket map .
Device Designated Gateway (DDG): Each AP is assigned a DDG and a standby DDG. The DDG publishes the bucket map to the AP and forwards broadcast and multicast traffic toward that AP's clients.
User Designated Gateway (UDG): Each tunneled client is anchored to a UDG and a standby UDG (S-UDG). The AP hashes the last three bytes of the client MAC address (an index from 0 to 255) into the bucket map to find them, so a client keeps the same anchor gateway as it roams between APs.
Failover: If a gateway fails or is taken down for maintenance, the standby takes over the designated role and the leader publishes a new bucket map. Assignments are event driven; AOS 10 does not periodically rebalance.
When gateways are needed: HPE recommends or requires gateways when a roaming domain exceeds about 500 APs or 5,000 clients, when user VLANs cannot be extended between APs, for Layer 3 mobility, for a RADIUS proxy, and for Dynamic Segmentation of wired UBT users.
The Role of Gateways in AOS 10
It is critical to recognize how the role of the Gateway has changed in AOS 10 compared to AOS 8:
In AOS 8 , the Mobility Controller handled AP configurations, firmware images, and radio RF settings.
In AOS 10 , the Gateway is dedicated purely to data-plane traffic enforcement, routing, and tunneling . It does not manage AP configurations, RF parameters, or AP firmware; those responsibilities belong entirely to Aruba Central.
Detailed Comparison: Bridge Mode vs Tunnel Mode
Feature / Attribute Bridge Mode Tunnel Mode
Data Forwarding Path Local breakout directly at the AP Ethernet port onto access switch GRE (data) and IPsec (signaling) tunnels to every gateway in the cluster
Gateway Hardware Required No (functions entirely with APs and switches) Yes (requires Aruba Mobility / Campus Gateways)
Firewall Inspection Location Distributed basic ACLs at AP or upstream switch router Centralized stateful Policy Enforcement Firewall (PEF) at Gateway
VLAN Requirements at Access Switch Client VLANs must be created and tagged on all switch ports and trunks Only AP management VLAN is required on access switch ports
Layer 2 Roaming Scope Limited to contiguous Layer 2 broadcast domains Campus-wide across routed Layer 3 boundaries
WAN / Uplink Impact Conserves WAN; local traffic remains local Transports all client traffic back to centralized gateway
Dynamic Segmentation Support Limited to local switch ACL enforcement Full integration with ClearPass and User-Based Tunneling (UBT)
High-Availability Mechanism Upstream switch redundancy (VSF / VSX / STP) Gateway cluster with designated and standby roles (UDG/S-UDG)
Common Exam Traps
The All-or-Nothing Trap: Believing that an access point must operate either entirely in Bridge mode or entirely in Tunnel mode. Aruba APs support mixed-mode deployments , allowing different SSIDs on the same physical radio to use different forwarding modes simultaneously.
Access Switch VLAN Pruning: Assuming that client VLANs must be configured on access switches for Tunnel-mode SSIDs. In Tunnel mode, the access switch only needs the AP management VLAN; client VLANs live on the gateway cluster.
AOS 10 Gateway Role: Thinking that an Aruba Gateway in AOS 10 configures AP radios or pushes WLAN profiles. In AOS 10, the Gateway is purely a data-plane policy and routing enforcement engine ; Aruba Central handles all configuration and RF control.