Wireless Access Point vs Bridge: Which Do You Need—and When Do You Need Both?

Use an access point to give nearby devices WiFi; use a wireless bridge to carry a network connection between fixed locations. If a remote building needs both an upstream link and local WiFi, you may need both. Start with the network job before comparing 2.4GHz wireless bridges for fixed outdoor links, APs or advertised range figures.

The expensive mistake is buying coverage equipment when the site lacks backhaul, or buying a bridge and expecting it to serve every phone nearby. Product names alone cannot settle the choice: some radios support multiple modes, and some APs can bridge networks. The deciding questions are what must connect, where it connects, and which functions the selected firmware actually supports.

1. What Is the Core Difference Between a Bridge and an AP?

1.1 A bridge solves a fixed backhaul problem

A wireless bridge is planned as a connection between two known network locations. One endpoint connects to the main LAN, and the other connects to equipment at the remote site. The radio path replaces part of a cable route that may be expensive or difficult to install.

Typical destinations include a gate camera, guard room, warehouse cabinet, farm building, parking entrance or detached office. The remote bridge may feed a PoE switch, IP camera, access controller, local recorder or another network device. The key question is whether the endpoints can maintain a usable path and remote handoff.

The bridge is therefore a backhaul component. It carries a planned network connection between fixed places. It is not automatically a broad WiFi service area for every phone, tablet or roaming client near the remote endpoint.

1.2 An AP solves a local client-access problem

An access point creates a WiFi service layer that compatible client devices can join. It suits a car park, courtyard, warehouse loading area, farm hub, office floor, residential common area or outdoor work zone where several devices need local access.

Those clients may include wireless cameras, handheld scanners, sensors, payment terminals, maintenance tablets or staff phones. An AP is flexible when devices can move or when new devices may be added inside the service area. It is evaluated by coverage, client capacity, roaming behaviour, airtime use and the quality of the wired or wireless uplink behind it.

An AP is not simply a stronger version of a bridge. It must serve client radios in different positions and orientations. Walls, foliage, metal structures, vehicles, device placement and client transmit power all affect the usable area. A theoretical range number cannot replace a coverage survey at the actual camera, reader and user locations.

1.3 A hybrid design separates the two jobs

Many real projects need both products. A bridge can carry connectivity from the main building to a remote cabinet. A switch at the remote cabinet can connect fixed cameras. An AP connected to that switch can serve a patrol tablet, sensor cluster or local maintenance devices.

Separating the roles makes troubleshooting clearer. If the bridge is reachable but a camera is unavailable, inspect the remote switch, PoE path or camera. If wired cameras work but a tablet has poor wireless service, inspect AP placement and local client conditions. If the entire remote LAN disappears, test the bridge endpoints, power and path.

Do not add both devices automatically. A nearby fixed camera may be cheaper and simpler on Ethernet. Wireless is most useful when it removes a genuinely difficult, disruptive or costly cable route.

2. AP, Bridge and Repeater Modes: The Differences That Matter

Compare the connection each option must provide before comparing hardware. A fixed link and a local client area have different survey and acceptance requirements. Use the role comparison below to identify which requirement is actually missing at your site.

2.1 Bridge and AP selection by network role

Neither option is automatically cheaper, faster or more reliable. A bridge can simplify one long connection, while an AP can simplify access for many nearby clients. If both requirements exist, compare the complete topology, including the remote switch, power and local AP, rather than comparing one radio with another in isolation. The wrong device can still appear to work during a short demonstration and fail when the site adds cameras, users, obstructions or peak-hour traffic.

2.2 Why AP and bridge labels can overlap

An AP can perform bridging at the network layer and still have a client-access role. Some products can also operate as dedicated bridges or workgroup bridges. Cisco's explanation of access-point configurations distinguishes these uses. That is why “APs cannot bridge” is too absolute, while “any two APs make a bridge” is equally unsafe.

Read the operating-mode description for the actual hardware and firmware. Check how the upstream side connects, what the remote Ethernet port does, and whether ordinary wireless clients can associate in that mode. A management SSID used during installation is not proof of a permanent client-access service. Record the intended mode at each end before ordering.

2.3 AP, bridge, client and repeater functions

Choose a mode by the connection it must provide. Functions vary by product and firmware. This is a generic comparison, not a COMFAST compatibility table. The manufacturer's operation-mode explanations illustrate why one product family may use familiar labels differently from another.

2.4 When one radio can provide backhaul and access

Some systems can carry client traffic and backhaul on the same radio, but the feature must be explicitly supported and configured. Cisco's documented backhaul-client-access example shows one implementation. It does not establish the same capability for the COMFAST models discussed later.

A combined arrangement may reduce hardware, but it also ties local access to the placement and radio resources of the upstream link. A separate AP is often easier to position for people inside a building while a bridge is mounted for the outdoor path. Test the intended workload before treating a combined mode as a substitute for two separately planned functions.

3. When Is a Wireless Bridge the Right Choice for a Remote Site?

3.1 Remote gate camera and access-control point

A gate at the end of a driveway is usually a bridge-shaped problem when the camera, intercom and access controller are fixed. The main building can connect to one bridge endpoint, while a second endpoint at the gate feeds a local PoE switch or injector.

The camera then has a defined local Ethernet connection after the wireless hop. That makes fault isolation more systematic: check the source switch, first radio, physical path, second radio and remote PoE equipment in sequence. The design can also keep the gate equipment on a controlled network segment rather than exposing it directly to unrelated local WiFi clients.

For a fixed gate link, the CF-E130N V2 point-to-point bridge is a product page to review after the path is defined. Its published table lists a single Ethernet interface and a 15V supply. That makes remote distribution and power compatibility explicit questions. It does not establish that the radio powers a camera, provides local client WiFi, or meets a particular video load.

3.2 Second building or guard room

When the main office has the internet connection or recorder and a guard room needs cameras, an intercom and a workstation, the first task is normally connecting the buildings. A bridge can provide the cross-site path, while a switch distributes Ethernet inside the guard room.

If guards also need WiFi, add an AP at the destination. Treating the bridge as the backhaul and the AP as the local access layer gives each device a clear responsibility. Changing the local SSID, client policy or AP position then does not require redesigning the inter-building link.

Use the building-to-building wireless link planning article to organise the cross-site questions, then check roofs, wall edges, trees, cranes, water tanks and future construction before choosing mounting points. A short map distance does not prove a usable radio path. The two endpoints need stable brackets, safe maintenance access and a cable route that protects the radio and power equipment.

3.3 Farm building, storage area or remote work zone

Rural sites often have one central building and several remote zones. A bridge is appropriate when one remote building or cabinet needs a defined network handoff. The remote side may then contain a local switch, fixed cameras, sensors or an AP for a work area.

Map the property by zones rather than treating the entire farm as one WiFi coverage circle. Identify the central network, remote endpoints, possible relay locations, power sources, seasonal vegetation and areas where users actually need wireless access. Keep the backhaul path separate from the areas where workers use WiFi. A remote storage cabinet may need only Ethernet, while an occupied workshop may need an AP. Treat seasonal vegetation and maintenance access as survey inputs rather than assuming a frequency label solves an obstructed path.

3.4 Temporary construction or event site

A temporary site can justify a bridge when a fixed office, camera zone or storage compound needs connectivity without trenching cable. The design should identify which endpoints remain stationary, how the radios are powered, how equipment is protected from theft and how the system will be removed or relocated.

An AP may serve workers within the temporary zone, but it does not remove the need for an upstream connection. A bridge can connect the temporary compound to the main network, while an AP serves local devices. If the site changes weekly, use a mounting and alignment method that can be documented and repeated.

4. When Does Local WiFi Coverage Need an Access Point?

4.1 Car park, yard or loading area

A car park may have cameras at entrances, staff tablets, sensors and payment equipment spread across an outdoor area. An AP can be the better base layer when these devices need to associate directly and the service area can be surveyed.

Place the AP for the actual client positions rather than for the easiest cable entry. A metal sign, steel cabinet, concrete wall or parked vehicle can change the signal available to a camera or sensor. Also consider the return path from the client to the AP; a powerful AP does not eliminate a weak client radio.

If the area is too large or includes separate buildings, an AP alone may not solve the upstream problem. A bridge can carry the network to a remote zone, and an AP can then serve clients within that zone.

4.2 Warehouse floor or outdoor logistics zone

An AP suits a warehouse or logistics area when handheld scanners, tablets, sensors and mobile staff devices need local WiFi. The coverage plan should follow aisles, loading points and workstations rather than simply placing the radio where the Ethernet cable is shortest.

Metal racks, stored goods, forklifts and changing inventory can alter the radio environment. Survey during representative operating conditions where possible. A client that works beside an empty rack may behave differently after the rack is loaded with metal goods or liquid containers.

If the warehouse is a remote building, solve the building-to-building backhaul first. The AP should then be selected and positioned for the indoor or outdoor client area. This sequencing prevents an AP coverage discussion from hiding a weak upstream link.

4.3 Residential compound or shared outdoor area

An AP is usually more suitable than a bridge when residents or visitors need WiFi across a courtyard, shared garden, parking area or common building entrance. The design should define the intended coverage boundary, expected client density, guest separation and maintenance access.

Do not use a bridge simply because it has a directional antenna and a high advertised range. A directional link may be excellent for two fixed endpoints but unsuitable for users moving around the compound. Conversely, an AP positioned behind a concrete wall may provide poor service even if the access point itself has a high nominal rate.

4.4 Sensor cluster or moving client group

An AP is useful when sensors or client devices are spread through a local area rather than concentrated at one fixed remote point. The survey should identify device height, orientation, battery condition and expected reporting interval. Low average traffic does not remove the need for reliable association and recovery after outages.

For battery-powered or small client devices, client transmit power and antenna placement may limit the usable area. Test the actual device model in the final enclosure and installation position. Do not judge coverage only from a laptop or phone with a different radio capability.

5. Bridge Backhaul and AP Coverage in One Network

5.1 Bridge topology: point to point, then local distribution

A common bridge topology is:

Main LAN -> switch or injector -> bridge endpoint A )) wireless path (( bridge endpoint B -> remote switch -> cameras, AP or controller

The wireless path is one segment in a larger network. The source switch must have the right uplink and power budget. The remote switch must accept the traffic and power the devices that need PoE. The bridge endpoints need secure mounting, suitable cable entry and a documented management path.

This topology works well when the remote site is stable and the traffic boundary is clear. It also allows fixed cameras to remain wired at the remote side while an AP serves occasional local users. The installer can test each section separately instead of treating the entire site as one wireless problem.

5.2 AP topology: wired uplink or planned remote backhaul

An AP typically connects to a switch by Ethernet and PoE. Its service quality depends on the wired uplink, local radio conditions, client distribution, channel plan and security configuration. If the AP is remote, the upstream connection may be a bridge, fibre or another approved network path.

The AP should be placed where clients need service, not where the network cabinet happens to be. Plan cable length, PoE budget, mounting height, antenna pattern, channel reuse and access for maintenance. If several APs are used, also plan overlap, roaming behaviour and wired uplink capacity.

5.3 Hybrid topology: bridge for distance, AP for local coverage

The hybrid architecture is useful for a detached building, gate complex, farm hub or outdoor work zone. The bridge provides the upstream path. A remote switch distributes wired service. An AP provides local wireless access only where needed.

This arrangement lets each radio be positioned for its main job, even when a supported combined mode would also be possible. The bridge can use a focused endpoint-to-endpoint design, while the AP can be optimised for local client positions. It also creates clearer failure domains: a backhaul issue and a local coverage issue are tested separately.

5.4 Avoid unnecessary wireless layers

Every additional wireless hop introduces another path, power source, alignment or airtime condition to maintain. If a cable can reach a fixed camera safely and economically, it may be the simpler choice. If a remote zone needs local WiFi, use one planned backhaul and one appropriately placed AP instead of adding repeaters without a traffic and maintenance plan.

Where several buildings need service, evaluate shared point-to-multipoint backhaul versus separate links as a separate topology decision. Do not infer PtMP compatibility from the ability to build one PtP link.

The right design is not the one with the most wireless devices. It is the one that meets the service requirement with a clear path, manageable failure modes and enough room for expected expansion.

6. Site Surveys, Mounting and Power for Outdoor Networks

6.1 A bridge survey checks a narrow path

A bridge survey focuses on two endpoints, mounting stability, alignment and the physical path between them. Trees, cranes, water tanks, roof edges, vehicles and future construction can interrupt a narrow directional path. The installer should inspect the route from both ends and consider objects around the direct line, not only what is visible at ground level.

Direct visual visibility is useful but incomplete. The path also needs practical clearance around the direct line. The required clearance depends on distance and frequency, so use a suitable planning method rather than assuming that seeing the far endpoint is enough.

6.2 An AP survey checks a service area

An AP survey focuses on usable coverage at each real client position. Walk the camera, reader, sensor, scanner and user locations. Record walls, metal surfaces, expected vehicle positions, client height and areas where users will move.

Measure both signal and service behaviour where possible. A phone may show a usable signal while a low-power sensor cannot return traffic reliably. A camera may associate but lose packets when its enclosure or mounting bracket changes the antenna environment. Do not convert a theoretical range into a promised floor area.

6.3 Mounting and environmental protection matter to both

Wireless does not remove the need for wired power and local Ethernet. A bridge normally needs power and network connectivity at both endpoints. An AP also needs a suitable uplink and power source, often through PoE where the equipment supports it.

Check switch or injector capacity, cable length, weather protection, connectors, grounding, surge protection and safe maintenance access. Keep outdoor equipment away from unplanned metal obstructions. Use drip protection and strain relief on cable entries. The exact protection method depends on the equipment manual and local electrical practice. The outdoor bridge installation preparation checklist is a related planning resource; use the current manual for model-specific wiring and electrical requirements.

6.4 Power and radio faults can look similar

A device that reboots, disappears or repeatedly reconnects may have a power or Ethernet problem rather than an RF problem. Record the power method, switch port, cable route, injector or PoE budget and environmental exposure during commissioning.

Troubleshoot in layers: local power, Ethernet link, radio association, signal and noise, IP reachability, network policy and application service. This sequence prevents a team from changing frequency when the actual fault is a damaged cable or overloaded injector.

7. Backhaul Capacity and AP Airtime Planning

7.1 Bridge capacity is shared by the remote site

List every service crossing the bridge: camera streams, access events, intercom audio, management traffic, file transfers, cloud synchronisation and internet access. Separate normal traffic from peak or exceptional traffic.

For cameras, use the intended resolution, frame rate, codec, scene movement and recording mode where known. Continuous recording and event recording create different patterns. Do not state a universal camera count because stream settings, network overhead and link conditions vary.

Include traffic in both directions. A remote site may send video while receiving management commands, time synchronisation, software updates or internet responses. A link that looks adequate in one direction can still fail when return traffic and retransmissions are included.

7.2 AP capacity is shared by clients and airtime

An AP must share airtime among associated clients. Capacity depends on client radio capability, signal quality, channel width, retries, contention, application traffic and the number of active devices. A high link rate for one client does not prove that all clients will receive the same service.

For a warehouse, list scanners, tablets, voice devices, cameras and guest users. For a yard, list cameras, sensors, staff devices and maintenance access. Identify which traffic is critical and whether it needs separation or prioritisation through compatible switching, gateway or controller equipment.

7.3 Separate nominal rates from usable throughput

The rate shown by a radio interface is not the same as application payload. Modulation, coding, acknowledgements, contention, Ethernet framing, management traffic and retransmissions reduce usable capacity. The rate can change as signal and noise conditions change.

Use current model documentation to understand interfaces and supported modes, then validate with representative traffic. A speed-test application alone may not reveal packet loss or variable latency that affects video, access events or roaming clients.

7.4 Plan for growth and maintenance traffic

The network may be adequate on installation day but become congested when another camera, higher-resolution stream or new application is added. List planned expansion for the next maintenance cycle. Also include firmware updates, storage synchronisation, backups and large file transfers that may overlap with operational traffic.

Decide whether maintenance traffic is scheduled, rate-limited or separated from critical services. A small reserve can be less expensive than replacing roof-mounted radios or pulling new cable after the site is operational.

8. Security and Management Across the Bridge and AP

8.1 Separate backhaul security from client access security

A bridge carries traffic between network locations; securing that path requires the supported encryption and management controls to be configured. An AP controls how client devices join and use a local wireless service. Both require secure credentials, current firmware processes and restricted management access, but the risk surface is different.

For a bridge, restrict management to authorised network locations and document both endpoints. For an AP, define SSIDs, authentication, guest access, client isolation and device onboarding according to the wider network design. Do not assume that an AP alone provides the complete firewall, VLAN or captive-portal policy.

8.2 Segment cameras, operations and guest devices

Security cameras, access controllers, staff devices and guests do not have the same trust level. Use separate SSIDs, VLANs, switch ports and firewall policies where the network supports them. A remote bridge may carry more than one network, but VLAN behaviour must be confirmed for the exact model and topology.

The safe statement is that segmentation may require a compatible switch, gateway, controller and documented bridge behaviour. Do not attribute VLAN, routing, RADIUS, captive portal or cloud-management features to a radio unless current model documentation explicitly supports them.

8.3 Document management and recovery

Record management addresses, device names, firmware versions, cabinet locations, power sources, reset procedures and authorised maintenance contacts. A remote link that works but cannot be safely maintained is not a complete project design.

For outdoor equipment, define how a technician will reach the device, how power will be isolated, how configuration backups are stored and what spare equipment is available. Recovery planning matters more when the endpoint is on a high pole, behind a gate or at a remote farm building.

9. Matching COMFAST Bridge Models to the Network Design

9.1 Review the bridge category after defining the role

Use the COMFAST 2.4GHz bridge model collection when the design calls for a fixed wireless Ethernet link and that product family is being considered. The collection is a shortlist starting point, not proof that every listed model shares the same power input, ports or supported modes.

Decide the operating country, endpoint layout, traffic and remote handoff before comparing devices. A buyer should not choose 2.4GHz simply because it sounds like longer range, or reject it simply because another product advertises a larger rate. Path feasibility, interference and legal configuration still need separate review. The category decision does not replace an AP coverage plan.

9.2 Check remote Ethernet and power for a warehouse link

Review interfaces and power before deciding how a remote warehouse cabinet will feed its equipment. The CF-E112N V2 wireless Ethernet bridge page lists two Fast Ethernet interfaces and a 48V adapter. Confirm their behaviour in the selected mode, the correct injector or power arrangement, and the need for a separate switch or AP.

Two sockets do not prove two independent upstream links, automatic redundancy, or the ability to power connected cameras. Ask how data passes between them in the intended configuration. A warehouse needing wired cameras and moving scanners should have separate acceptance criteria for its bridge backhaul, local switching and AP coverage. Select by that topology rather than a general “outdoor coverage” phrase.

9.3 Check radio-rate claims against the wired handoff

A radio headline does not establish end-to-end application speed. The CF-E314N V2 outdoor bridge with dual Ethernet ports page lists Fast Ethernet interfaces alongside its wireless-rate information. The relevant buying question is whether the complete path can carry the required workload, including its wired handoff, protocol overhead and changing radio conditions.

Request measured results for the intended mode and traffic rather than treating an advertised radio rate as a delivered Ethernet rate. This is particularly important when a remote AP will serve users while cameras are also active. Do not turn a higher-gain antenna or a larger headline number into a universal distance ranking. Confirm the installation and test evidence for the actual site.

9.4 Verify COMFAST operating modes before approving a sample

Obtain written confirmation of Bridge, AP, Client and Repeater modes for the exact hardware revision and firmware. Ask whether a phone can join while the bridge link is active, whether a setup SSID is temporary, and which Ethernet interfaces remain usable. Confirm VLAN handling only if the design requires it; do not infer it from basic Ethernet connectivity.

Public product descriptions are useful for identifying equipment, but they do not replace a mode-by-mode acceptance record. Before approval, ask for current documentation and a sample test that reproduces the required topology. The supplier and installer should agree on the tested configuration, the connected devices and the conditions that would require a different AP, bridge or wired solution.

10. How Do You Verify the Bridge Link and WiFi Coverage?

10.1 Bridge acceptance checks the path and application

Record the exact model and firmware, endpoint positions, band, channel, channel width, power setting, antenna orientation, cable route, power method and available radio indicators. Where the interface exposes RSSI, SNR, noise or capacity, record them without assuming a universal pass threshold. Measure packet loss and application behaviour with suitable test tools.

For CCTV, view representative streams while generating the expected background traffic. For access control, test event delivery and recovery after a controlled power interruption if the operating procedure permits. For a remote office, test both upload and download behaviour. Save the baseline for future comparison.

10.2 AP acceptance checks locations and client behaviour

Test the actual client types at the actual service boundary. Record coverage, association, packet loss, latency, throughput, roaming where required and behaviour during peak activity. Include the weakest expected client, not only a modern laptop.

For a warehouse, walk the scanners or tablets through the aisles. For a car park, test cameras and access points at the entrance and edge positions. For a farm, test the remote zone under representative foliage and weather conditions where practical.

10.3 Separate RF, Ethernet and application acceptance

An associated radio does not prove that a camera stream, access event or business application works. A healthy wireless path can still have a VLAN, IP addressing, firewall, gateway, recorder or switch problem.

Use separate acceptance records for RF indicators, Ethernet counters, IP reachability and the user-facing service. This gives the installer, network administrator and application owner a shared method for assigning responsibility when a fault appears.

10.4 Keep a baseline for maintenance

The acceptance record should state what was tested and for how long. “Signal is good” is not an acceptance result. A useful record names the traffic, test window, radio settings, measured indicators and observed application behaviour.

When a later complaint arrives, compare the live system with that baseline. A changed signal level points toward alignment, mounting or cable inspection. Similar signal with lower capacity points toward noise, channel use, retries or traffic growth. Repeated reboots point toward power, Ethernet or environmental exposure.

11. Deployment Mistakes That Leave Remote Devices Offline

11.1 Expecting a bridge to provide broad WiFi

A bridge can be reachable while phones, tablets or sensors near the remote endpoint have no suitable local WiFi service. The bridge solves the backhaul, not necessarily the local coverage. Add a correctly placed AP or use a wired connection for fixed devices.

11.2 Expecting an AP to replace a fixed backhaul

An AP may provide good service near one building but fail to deliver a stable connection to a distant building or gate. A long fixed route needs endpoint alignment, path clearance, traffic planning and suitable mounting. Use a dedicated bridge or another engineered backhaul where the path requires it.

11.3 A link works during installation but fails later

Common causes include growing foliage, a moved bracket, a new obstruction, seasonal rain, changed neighbouring activity, water ingress or a power problem. Compare live measurements with the commissioning baseline and inspect the physical path first.

If signal has changed, inspect alignment, mounting and cable. If signal is similar but capacity has fallen, inspect noise, channel use and retries. If the device reboots or disappears, inspect power, injector, switch port and environmental exposure.

11.4 Cameras work but mobile clients do not

This pattern makes local AP coverage, association, authentication and airtime useful starting points, although different traffic policies or loads can also affect the shared backhaul. Check the client's position, radio capability, SSID policy, signal, retries and local interference. If wired remote cameras remain normal, keep the bridge and AP investigations separate.

12. A Final Selection Checklist for Project Buyers

12.1 Pre-order questions for the buyer

Before ordering, confirm:

• Is the requirement a fixed point-to-point connection, a local coverage area or both?
• Which devices are fixed, and which devices move or associate directly over WiFi?
• Where are the main and remote network endpoints?
• What traffic must cross the backhaul at normal and peak times?
• What coverage boundary and client density must the AP support?
• Are walls, trees, metal structures, vehicles or future construction relevant?
• Is power available at every radio, switch, AP and camera location?
• Are management, encryption, segmentation and remote-access requirements documented?
• Have country-specific spectrum and certification requirements been checked?
• Are current datasheets and manuals available for the exact hardware?

12.2 Installer acceptance questions

Ask the installer for endpoint photos, path clearance assumptions, mounting details, cable route, power and surge plan, AP coverage measurements, channel survey, alignment method, commissioning values and maintenance access.

Require the installer to state what change would trigger a redesign: a new tree line, an added camera, a new building, higher traffic, a different client type or a moved cabinet. This record creates a shared boundary between buyer, installer and supplier.

12.3 A simple selection rule

Choose a wireless bridge when the dominant question is “How do I connect this fixed remote location?” Choose an AP when the dominant question is “How do I serve several wireless clients in this area?” Choose both when the remote zone needs a backhaul and local wireless service.

The rule is simple, but approval still depends on path, coverage, traffic, power, security, country requirements and commissioning evidence.

13. Conclusion: Choose by Backhaul and Coverage Requirements

A wireless bridge and a wireless access point should not be selected from the same rule. A bridge is primarily a planned backhaul between fixed locations. An AP is primarily a local WiFi access layer for multiple clients. A bridge-plus-AP design is appropriate when a remote zone needs both an upstream connection and local wireless service.

Start with the physical job, then validate the path, client positions, traffic, power, security and maintenance requirements. This reduces the risk of buying an AP for a long fixed link or expecting a bridge to behave like a broad local WiFi network. The best choice is the one whose role, evidence and acceptance test match the service the project must deliver.

Frequently Asked Questions