x
Send Your Inquiry Today
Quick Quote

Wireless Bridge for WISP Backhaul: A Rural Network Planning Checklist

Wireless Bridge for WISP Backhaul: A Rural Network Planning Checklist
Wireless Bridge for WISP Backhaul: A Rural Network Planning Checklist

A wireless bridge can carry rural WISP backhaul when the fixed path, usable capacity, permitted radio configuration and recovery arrangements meet the service requirement. Before comparing 2.4GHz bridges for fixed Ethernet links, separate a light customer branch from a relay that aggregates several access sites. A connection that serves one farm does not automatically have the capacity or operating margin to serve a village.

The useful starting point is a service plan: what crosses the link, where traffic concentrates, what an outage interrupts and how the network will grow. Distance and advertised wireless rate are inputs to that decision. Neither is an acceptance result.

Table of Contents
What Must a Rural WISP Backhaul Link Carry?. Wireless bridge for WISP backhaul planning.
What Must a Rural WISP Backhaul Link Carry?. Wireless bridge for WISP backhaul planning.

1. What Must a Rural WISP Backhaul Link Carry?

1.1 Define the backhaul service before selecting radios

Backhaul connects a remote network to its upstream aggregation or core; local subscriber access remains a separate job. A pair feeding one customer router, a relay feeding several access points and a tower carrying multiple subscriber sectors have different workloads and failure consequences. Write the job on the network drawing before requesting equipment.

Include the endpoints, traffic owners and expected operating period. A shop that closes overnight differs from a relay carrying continuous monitoring and residential evening traffic. If the same link serves both, the quieter business schedule does not define the whole requirement. The equipment request should describe the combined service rather than an attractive maximum distance.

1.2 Translate subscriber counts into traffic requirements

Subscriber count becomes useful only when paired with service tiers, actual concurrency and application demand. Adding every sold package rate gives one view of commitments, but it does not predict the busy-hour behaviour of shared residential service. Conversely, assuming that few customers are active can conceal a contractual guarantee the operator must honour.

Separate guaranteed demand from shared demand and record the evidence behind any forecast. A new site may need a conservative pilot because historical measurements do not exist. Keep school video sessions, business uploads and remote camera streams visible as distinct inputs. A single oversubscription ratio cannot establish the right capacity for every rural community.

1.3 Set service acceptance criteria before installation

Acceptable service means meeting agreed application and continuity requirements under representative load. Define what matters for the subscribers: usable transfer performance, delay, loss, session stability and expected interruption. The operator and technical approver should agree on these requirements before the installer is judged against them.

A local payment terminal and an evening video stream may respond differently to congestion. Decide which traffic needs protection, where any policy will operate and what reduced service is acceptable during a fault. Avoid promising uninterrupted operation simply because the radio pair connects. A successful association is the beginning of verification, not the complete customer service test.

Make the acceptance record specific enough to distinguish local recording from Internet access. A remote camera can keep recording while its off-site viewing path is unavailable, just as a subscriber can reach the gateway while an upstream service is down. Identify the intended application endpoint for each check so that the installer tests the service being sold.

Engineer Tip: Give each link one sentence of ownership: which endpoints it joins, whose traffic it carries, who an outage affects and who restores it.
Mapping Core, Relay and Subscriber Traffic Paths. Wireless bridge for WISP backhaul planning.
Mapping Core, Relay and Subscriber Traffic Paths. Wireless bridge for WISP backhaul planning.

2. Mapping Core, Relay and Subscriber Traffic Paths

2.1 Draw the complete rural service path

The topology should follow traffic from upstream handoff through the core, aggregation, radio link, remote switch and access layer. Mark where subscriber routing, authentication, management and application services actually terminate. A diagram that ends at the remote bridge hides the equipment needed to make that connection useful.

An illustrative layout is upstream connection → core gateway → bridge pair → remote switch → access equipment → subscriber devices. It is a planning example, not a documented COMFAST deployment. Add the management route and any local recorder or server before calculating load. Traffic that stays at the remote site may place a different demand on the backhaul from traffic returning to the core.

2.2 Compare dedicated branches with shared radio resources

Dedicated point-to-point branches and a shared point-to-multipoint arrangement require different capacity and failure assessments. Separate branches can make radio faults easier to isolate, while a shared central radio concentrates responsibility for several remote endpoints. Neither layout removes common upstream or power dependencies.

Confirm the exact operating modes, compatibility and allocation behaviour of the proposed platform before choosing a shared design. A directional antenna, several Ethernet ports or a generic bridge description does not establish subscriber capacity. Compare the total planned workload and its distribution across endpoints. If one remote site needs substantially more capacity, a dedicated path may deserve evaluation even when the other sites are light.

Comparison dimensionDedicated point-to-point branchesShared point-to-multipoint designSuitable planning question
Traffic boundaryEach branch has an identifiable radio pathRemote endpoints share central resourcesWhere does demand concentrate?
Failure impactA radio fault may remain within one branchA central radio fault can affect several endpointsWhich common dependencies remain?
Evidence neededMatched endpoint modes and branch testsSupported platform, concurrent load and allocation testsDoes the exact configuration meet the service plan?

2.3 Record capacity at every relay handoff

A relay must be assessed as an aggregation point, not simply another pair of radios. Record the traffic entering and leaving each interface, along with Ethernet rates, radio channels and the services that share them. Adding advertised rates from two hops does not create an end-to-end capacity figure.

If adjacent wireless hops use shared spectrum, test them operating together. A result obtained with one hop active may not survive when the whole route carries traffic. Also consider traffic from local subscribers joining the relay. The onward path must carry that additional demand as well as traffic arriving from earlier branches. A clean drawing exposes this concentration before equipment is ordered.

2.4 Place subscriber and management controls at verified boundaries

Transporting Ethernet frames, separating VLANs and enforcing subscriber policy are different functions. Establish which device performs each job and confirm that the bridge passes the required traffic in its intended mode. Do not attribute billing, firewall policy or authentication to a radio because it sits in the middle of the path.

The checks in VLAN transport and isolation across a wireless bridge are useful when management and subscriber traffic share a physical link. Verify allowed services and prohibited access at the real enforcement point. Document an administrator’s recovery route before restrictive changes. A tag reaching the far end proves transport; it does not alone prove an effective security boundary.

Busy-Hour Capacity and Ethernet Handoff Limits. Wireless bridge for WISP backhaul planning.
Busy-Hour Capacity and Ethernet Handoff Limits. Wireless bridge for WISP backhaul planning.

3. Busy-Hour Capacity and Ethernet Handoff Limits

3.1 Keep downstream and upstream demand separate

Backhaul capacity planning needs a demand profile for each direction. Residential streaming may concentrate downstream traffic, while cloud backups, business uploads and remote surveillance can increase upstream demand. Measure or estimate both rather than describing the link with one undirected traffic total.

Record the time window and sampling interval behind the figures. A long average can hide bursts that cause queues and application delays. For a new site, label forecasts as assumptions and identify how the pilot will replace them with observations. Include growth that is already planned, such as another access point or camera group. Demand introduced after commissioning changes the original acceptance basis even when the radio settings stay the same.

3.2 Use arithmetic examples without turning them into model claims

A planning example can explain demand without claiming a tested bridge capacity. Suppose a branch is forecast to need 45Mbps downstream and 8Mbps upstream, with another 5Mbps of traffic in the downstream direction. The resulting application-demand inputs are 50Mbps downstream and 8Mbps upstream.

These are hypothetical inputs, not customer measurements, service guarantees or a COMFAST test. They exclude transport overhead, retransmissions, operational reserve and future growth. Test the proposed system against the actual traffic mix rather than selecting hardware from the sum of the two directions. Keeping the assumptions beside the calculation makes it possible to revise the design when customer behaviour differs from the forecast.

3.3 Check the Ethernet handoff before trusting wireless rates

An Ethernet handoff can impose a lower ceiling than the advertised radio rate. Traffic traversing one 100Mbps Ethernet interface cannot deliver 300Mbps of application data through that interface in the same direction. Payload throughput may be lower because the path includes other constraints and overhead.

Inspect every relevant port, including the remote switch, gateway and test computer. Two Fast Ethernet ports do not establish link aggregation or a 200Mbps single-stream path. Full-duplex Ethernet also does not prove that the shared radio resources can deliver equivalent simultaneous upstream and downstream throughput. Request measured results for the intended topology instead of converting wireless rate to application speed with a universal efficiency percentage.

3.4 Set expansion triggers from service quality

The right expansion trigger combines demand, service quality and expected growth. Avoid choosing one utilisation percentage for every link regardless of traffic bursts, applications and recovery objectives. Observe how delay, loss and customer sessions behave when the link carries the planned load.

Document where approved traffic management runs and test its effect. A queue or rate policy cannot create missing backhaul capacity, and an unsupported policy should not be assumed in the quotation. Define the action attached to each trigger: investigate a path change, rebalance traffic, increase capacity or evaluate another medium. This turns monitoring into an operating decision rather than a chart that is reviewed only after subscribers complain.

Engineer Tip: Ask for separate-direction and simultaneous-load results, with topology and settings attached. A screen showing the negotiated radio rate does not answer the capacity question.

4. Can the Proposed Rural Path Support the Link?

4.1 Survey both endpoints and the intervening path

A map helps screen a proposed route, but a field survey must confirm the actual installation and intervening obstructions. Record coordinates, mounting positions, access rights, terrain, rooftops and vegetation. Photographs are useful evidence when their location and direction are identified.

Optical visibility alone does not settle radio clearance or propagation performance. The first Fresnel zone and ground-reflection conditions need engineering assessment for the selected path and equipment. ITU-R P.530 on terrestrial line-of-sight system design provides a formal propagation reference; its existence does not establish a particular product’s range. Keep model-specific performance claims dependent on appropriate evidence and site verification.

4.2 Include seasonal and operational obstructions

A rural path should be evaluated for normal changes, not only the easiest day to install it. Vegetation, crops, temporary structures and vehicles can alter the path. Distinguish permanent obstacles from changes that require a different mounting position or a maintenance agreement.

Check whether brackets and mounting structures retain alignment in their expected environment. A clear route with a moving antenna is still an uncertain link. Increasing transmit power is not a substitute for resolving an unsuitable location. If another endpoint or relay is proposed, repeat the capacity, permission, power and access assessment. The extra site introduces dependencies that should be visible in the service plan and maintenance budget.

4.3 Read radio measurements alongside delivered traffic

Radio measurements explain reception conditions; application tests show whether the service works. Record receiver identity, direction, channel width, firmware and load with readings such as RSSI, SNR, noise floor and radio rate. A connected state or familiar signal indicator does not prove busy-hour delivery.

The distinction is developed in wireless bridge signal metrics and commissioning tests. Use the readings to investigate changes relative to the link’s own baseline rather than applying one good-signal threshold to every model. If measurements look acceptable but customers lose service, examine the Ethernet, switching and application path as well. The radio is only one part of the end-to-end system.

4.4 Retain an alternative when the path is unsuitable

An obstructed, inaccessible or unapproved mounting location can make a bridge proposal impractical. Compare a different location, a properly designed relay, fibre or another suitable access and transport option. Keep the comparison tied to the service objective rather than forcing the originally preferred radio solution.

Evaluate construction, permissions, recurring charges, site visits, spares and expected upgrades together. Lower equipment cost does not necessarily mean a lower operating cost. Where cellular access is being considered, rural WISP planning with 4G/5G routers addresses the upstream cellular role. That decision should remain distinct from verifying the local fixed wireless route that distributes the connection.

Frequency Planning Within the Destination Country. Wireless bridge for WISP backhaul planning.
Frequency Planning Within the Destination Country. Wireless bridge for WISP backhaul planning.

5. Frequency Planning Within the Destination Country

5.1 Confirm permitted outdoor operation before configuration

The destination country’s current requirements determine which configuration may be deployed. A frequency range printed on a product page is not proof that every channel is available for outdoor WISP use. Assign responsibility for checking equipment approval, power, antenna-related limits and any licensing or registration requirements.

Keep the jurisdiction, hardware version and intended settings together in the procurement record. No single national channel list or power setting can be inferred for an unspecified African market. If the compliance decision remains unresolved, treat that configuration as unapproved for deployment. The sales quotation and sample configuration should not quietly become the compliance authority for a production operator network.

5.2 Compare bands using the actual site conditions

Band selection should follow legal options, path conditions, local spectrum observations and the intended workload. Avoid assuming that one frequency is always the long-range choice and another always the clean-capacity choice. The actual radio design and installation affect what can be delivered.

Record channel width as part of the comparison. A wider channel uses more spectrum and may be unsuitable where available channels or interference conditions constrain the design. A narrower setting also needs testing against the required throughput. Compare candidate settings using the same path and load, within approved operation. A higher advertised rate cannot resolve a poor path or a crowded local environment by itself.

5.3 Coordinate backhaul and access radios at relay sites

A relay needs a frequency plan for the equipment operating together. Inventory nearby backhaul radios, access equipment and other relevant transmitters. Record their placement, direction, channels and widths, then test the intended simultaneous operating arrangement.

A spectrum observation is a sample of conditions, not a permanent guarantee of an interference-free site. Repeat relevant observations during representative operating periods and after significant changes nearby. Keep both bridge endpoints in the assessment because their environments may differ. If a radio offers scanning or spectrum tools, verify their availability and interpretation for the exact firmware rather than assuming that every bridge provides the same diagnostic functions.

Engineer Tip: Put the destination country, equipment version and approved radio settings on the same record as the sample acceptance result.

6. Power, Maintenance and Recovery at Remote Relay Sites

6.1 Include every service dependency in the power plan

Backup power must cover the devices needed to deliver the service, not just the most visible radio. Trace the dependency through the upstream router, switches, both radio endpoints and remote access equipment. A powered bridge is of little use if its required upstream switch has stopped.

Assess operating load, conversion losses, environmental conditions and usable battery capacity before promising autonomy. Dividing nominal battery energy by a nominal equipment load gives an idealised calculation, not a verified outage runtime. The ITU’s rural communications overview identifies energy supply and backup costs as deployment considerations. Use that general context alongside current site measurements, not as a specification for a particular battery installation.

6.2 Verify PoE compatibility for the exact hardware

An RJ45 connector and the word PoE do not establish electrical compatibility. Confirm input voltage, supported standard or passive method, polarity, powered pairs, maximum demand and the approved injector or switch. Keep the hardware revision and supplied power equipment identifiable.

The system checks in PoE switch and power planning for WISP sites complement the device documentation. They cannot replace the selected bridge’s power requirements. Outdoor protection, bonding and cable arrangements need the site’s applicable electrical design and qualified implementation. Avoid treating a general networking article as installation approval, particularly when a remote cabinet uses batteries, solar conversion or a mixture of power methods.

6.3 Make remote recovery achievable when the link fails

Recovery needs a route that still exists during the fault being considered. If management access uses the same failed bridge, a remote reboot cannot be assumed available. Record site access, local contacts, replacement equipment, approved configuration backups and the practical time needed to reach the installation.

Where an independent maintenance connection is provided, test its power and access controls as well as its reachability. Where it is absent, include travel and entry arrangements in the expected restoration time. A spare radio stored far away does not provide the same recovery as an accessible, documented replacement. Maintenance planning should reflect the people and permissions actually available to the operator.

6.4 Identify shared failures before buying backup equipment

A second radio path does not remove a failure shared by both paths. Common power, switches, mounting structures, upstream handoffs and management dependencies remain relevant. Identify these before deciding what an additional bridge pair would protect.

This is a requirement to evaluate, not a claim that the three linked COMFAST models provide native automatic failover. Switching or routing through a backup path needs a compatible system and an appropriate tested configuration. Record who owns that design and which failure tests will prove it. Manual replacement can be a valid recovery method, but it should not be described to subscribers as automatic service continuity.

7. Choosing COMFAST Bridges for a Verified WISP Role

7.1 Check CF-E314N V2 against the branch handoff

The CF-E314N V2 bridge with separate WAN and LAN handoffs lists one 10/100Mbps WAN port and one 10/100Mbps LAN port. These published interface details help frame a branch design; they do not demonstrate operator capacity or aggregate the two ports into a faster individual path.

For a proposed remote branch, ask how those ports behave in the selected operating mode and firmware. Confirm the power arrangement and the traffic result with the actual upstream and downstream equipment. Keep the branch’s purpose explicit: candidate hardware for a verified fixed link, rather than an assumed high-capacity village aggregation platform. The workload and acceptance evidence should determine whether it fits.

7.2 Assess CF-E112N V2 with the remote switching plan

The CF-E112N V2 bridge with dual Fast Ethernet interfaces lists two 10/100Mbps WAN/LAN ports. A remote site that needs local switching or access equipment should check the intended role of each interface before building its cabinet around the product.

Two physical ports do not establish traffic isolation, a management VLAN, link aggregation or a particular switching policy. Request the corresponding mode and firmware evidence where those functions are required. Confirm power compatibility from the exact documentation rather than relying on a generic PoE description. Evaluate the candidate with the same branch workload used for the other models, so that a different port arrangement does not conceal an unmet service requirement.

7.3 Review CF-E130N V2 for a single-port branch

The CF-E130N V2 single-port point-to-point bridge lists one 10/100Mbps WAN/LAN interface. A light fixed branch can treat it as a candidate for testing when the handoff, management and power requirements are compatible. The single interface makes the local connection plan especially important.

Determine how maintenance access will coexist with business traffic in the intended mode. If the remote site needs additional endpoints, include the necessary compatible switching rather than assuming the radio supplies those ports. An advertised 300Mbps wireless rate does not make this Ethernet handoff suitable for more than its physical rate in one direction. Larger aggregation requirements should lead to an appropriately verified alternative.

7.4 Compare candidates with one acceptance matrix

Use the same service requirements to evaluate every candidate. Request the exact model and revision, firmware, operating mode, port behaviour, power method, management recovery and traffic test conditions. Record unresolved functions as supplier verification items rather than leaving them implicit in the purchase order.

The linked specifications support interface comparisons, not a ranking of tested WISP throughput. If the proposed growth or continuity objective exceeds the available evidence, compare a suitable higher-capacity platform or another medium. Do not lower the service requirement to justify a preferred product. A useful supplier response explains both where the candidate fits and which requirement still needs a sample test or additional equipment.

Comparison dimensionCF-E314N V2CF-E112N V2CF-E130N V2Suitable decision use
Listed Ethernet handoffOne 10/100Mbps WAN and one 10/100Mbps LANTwo 10/100Mbps WAN/LANOne 10/100Mbps WAN/LANCheck the remote connection and intended mode
Wireless rate versus deliveryAdvertised rate is not measured payload throughputSame evidence boundarySame evidence boundaryRequest comparable traffic tests
Operator functionsConfirm required functions separatelyConfirm required functions separatelyConfirm required functions separatelyDo not infer VLAN, billing or failover capability
How Should You Accept and Expand the Backhaul?. Wireless bridge for WISP backhaul planning.
How Should You Accept and Expand the Backhaul?. Wireless bridge for WISP backhaul planning.

8. How Should You Accept and Expand the Backhaul?

8.1 Build a repeatable pilot acceptance test

A pilot should reproduce the proposed equipment, settings and representative path as closely as practical. Record the test hosts, interfaces, firmware, traffic direction and measurement method. Establish a wired baseline so that a slow test computer or local handoff is not mistaken for radio performance.

Use an appropriate measurement tool with documented settings. The official iperf3 testing options explain reverse traffic with -R and simultaneous bidirectional testing with –bidir; check support in the installed version. These options measure test traffic, not the complete quality of subscriber applications. Keep results with their conditions and use application checks to establish whether the service objective has been met.

8.2 Validate concurrent demand rather than an idle link

Acceptance should include the traffic combinations the operator expects to carry. After testing directions separately, evaluate simultaneous demand and relevant applications, observing delay, loss and session behaviour as well as throughput. Include camera or management traffic if it shares the same path.

Choose the duration and observation period from the service and fault risks. A universal short test cannot prove every seasonal path or evening congestion condition. High-load testing can itself affect customers, so arrange a maintenance window or isolated pilot and preserve a rollback plan. Record what was not tested as clearly as what passed. This prevents an incomplete demonstration from being sold as a complete operating guarantee.

8.3 Verify restoration and configuration persistence

A service acceptance record should show how the site returns to operation after approved maintenance or power recovery. Check configuration persistence, management reachability and the intended sequence of dependent equipment. Where equipment replacement is part of the recovery plan, verify that the saved configuration and documentation are usable.

Plan disruptive tests with the operator; do not unplug live production equipment without an agreed window. Confirm that access controls and subscriber separation return with the service, rather than accepting connectivity alone. Give failed checks an owner and a retest action. A failure recorded during a pilot is useful evidence when it changes the design before customers depend on the link.

8.4 Tie expansion to measurements and operational ownership

Expansion decisions should follow busy-hour service results, growth and maintenance experience. Additional subscribers, access sites, cameras or relay hops can invalidate the original demand model even if the same radio pair remains installed. Keep the commissioning baseline available for comparison.

Assign a measurement source, review owner and action to each important trigger. Rising delay under load may call for capacity investigation, while repeated site visits may expose a power or access problem. If the available observations are insufficient, continue collecting evidence rather than declaring the link suitable indefinitely. A clear upgrade plan protects both the operator’s investment and the service expectations established with customers.

Preserve the commercial consequence of an expansion decision as well. If another relay is proposed, record its site rental, access arrangements, power dependencies and recurring support responsibilities before approving the equipment order. A technically feasible route can become difficult to operate when nobody owns the new location or the budget for maintaining it.

Acceptance objectEvidence to retainAction when evidence is insufficientSuitable scenario
Rural radio pathSurvey, mounting and environmental conditionsReassess the location or routeFixed outdoor branches and relays
Delivered capacityDirectional, concurrent and application testsReduce planned load or compare another platformSubscriber and relay aggregation
Power and restorationDependency list, recovery sequence and observed resultsRevise power or recovery arrangementsUnattended remote sites
Permitted operationDestination jurisdiction and approved configurationHold deployment until verifiedOutdoor operator installations

Conclusion: Approve the Rural Service Path Before the Hardware

A wireless bridge is a candidate for a surveyed, measured and maintainable fixed rural connection. Select it through the service path: define subscribers and traffic, verify the route and permitted settings, check every handoff and prove the recovery arrangement. Neither advertised distance nor wireless rate can replace those decisions.

For a WISP, the useful purchase outcome is a service that meets agreed requirements under representative load and can be restored by the available team. Keep unverified model functions in the supplier acceptance record. Revisit capacity when the network grows, and compare other platforms or media when the branch becomes an aggregation link with different demands.

Frequently Asked Questions

Can one wireless bridge serve an entire village?

Only if the complete design and measured capacity support the village’s demand. A bridge may transport traffic to access equipment, but it does not automatically provide subscriber coverage, billing or enough capacity for every household. Identify where users connect, how their traffic aggregates and what service tiers are being offered. Then test the proposed link and its Ethernet handoffs under representative concurrent load. A successful connection to one building cannot establish village-wide service capacity.

Should a rural WISP use a bridge or a cellular router?

Choose by the network role and the available upstream service. A cellular router obtains connectivity through a mobile network, while a fixed bridge can transport an existing connection between suitable locations. Some deployments use both, with the cellular router at a favourable reception point and a bridge feeding another site. Evaluate cellular capacity and recurring terms separately from the fixed radio path. Neither component removes the need to plan subscriber access and busy-hour demand.

Is 300Mbps enough for WISP backhaul?

An advertised 300Mbps wireless rate cannot answer that question. Usable performance depends on the radio conditions, equipment, operating mode, Ethernet path and actual traffic mix. The three linked product pages list Fast Ethernet handoffs, which need to be included in the capacity assessment. Request measured directional and simultaneous-load results for the intended configuration. Compare those results with service requirements and realistic growth instead of assigning a subscriber count from the advertised wireless rate.

Does a WISP bridge need its own backup power?

It needs power continuity consistent with the service objective, but protecting one radio alone may leave other dependencies unprotected. Trace the upstream gateway, switches, both bridge endpoints and remote access equipment before sizing backup. Confirm actual load, conversion losses, usable battery capacity and recovery behaviour with the responsible electrical designer. A nominal battery calculation is a planning input rather than a guaranteed runtime. If no backup is provided, document the resulting outage and restoration expectation.

Can two bridge pairs provide automatic failover?

Two pairs can be components of a resilient design, but their presence alone does not provide automatic switching. A compatible routing or switching system must select the intended path and handle the relevant failure safely. Shared power, upstream equipment and mounting can also defeat the proposed independence. Specify the protected failures, acceptable interruption and validation tests before buying. Confirm the actual protocol and mode support instead of assuming that every radio includes automatic failover functions.

Which COMFAST bridge should a WISP evaluate first?

Start with the role and handoff requirement rather than a model ranking. CF-E314N V2 lists separate Fast Ethernet WAN and LAN ports, CF-E112N V2 lists two Fast Ethernet WAN/LAN interfaces, and CF-E130N V2 lists one. Those differences help frame a fixed branch proposal, but they do not prove WISP throughput or subscriber functions. Send the same topology, workload, power and management requirements for each candidate, then accept only the configuration supported by documentation and representative tests.

Define the Rural Backhaul Before Ordering

Share the topology, destination country, site path, directional workload, power and recovery requirements to discuss a suitable COMFAST bridge candidate and the evidence needed for acceptance.

Scroll to Top