Dryad Silvanet Documentation
Get StartedExplore SilvanetPlan a SiteDeploy SilvanetFAQ
  • Dryad Silvanet Documentation
  • Tutorials
    • Get started tutorial (Gen 2)
    • Get started tutorial (Gen 3)
    • Planning tool tutorial
  • Silvanet Suite
    • Explore Silvanet
    • Silvanet Suite (Gen 2)
      • Silvanet Wildfire Sensor (Gen 2)
      • Silvanet Mesh Gateway (Gen 2)
      • Silvanet Border Gateway (Gen 2)
    • Silvanet Suite (Gen 3)
      • Silvanet Wildfire Sensor (Gen 3)
      • Silvanet Mesh Gateway (Gen 3)
      • Silvanet Border Gateway (Gen 3)
    • Silvanet Cloud Platform
    • Silvanet Mesh Network
    • Site Management App
      • User access
      • Dashboard
      • Sites view
      • Site details
        • Device overview
        • Wildfire Sensor data
        • Device info tabs
      • Map view
      • Alert center
      • User Management view
      • User preferences
    • Deployment App
    • Fire detection
  • Site Planning
    • Plan Sites
    • Planning guidelines
      • Deployments stages
      • Scout deployment locations
      • Gateway ratios
      • Gateway ranges
      • Sensor ratios
      • Sensor range
      • Sensor density
    • Coverage planning
      • Planning tool
      • Import KML, KMZ and Shapefiles
      • High density paths
      • Low density areas
      • Connectivity zones
      • Add or move Sensors
      • Export plan
    • Packet editor
  • Silvanet Deployment
    • Deploy Silvanet
    • Deployment guidelines
      • Deployment preparation
      • Border Gateway guidelines
      • Border Gateway scenarios
      • Mesh Gateway guidelines
      • Wildfire Sensor guidelines
    • Deploy Border Gateways (Gen 2/3)
      • Register Border Gateway
      • Mount Border Gateway (Gen 2)
      • Mount Border Gateway (Gen 3)
      • Border Gateway Connectivity Test
    • Deploy Mesh Gateways (Gen 2/3)
      • Register Mesh Gateway
      • Mount Mesh Gateway (Gen 2)
      • Mount Mesh Gateway (Gen 3)
      • Mesh Gateway Connectivity Test
    • Deploy Wildfire Sensors
      • Register Wildfire Sensors
      • Mount Wildfire Sensors
      • Sensor Calibration
      • Sensor normalization
    • Relocate a Silvanet Sensor or Gateway
  • Silvanet API
    • Silvanet API - MQTT Sensor Data Integration
    • Silvanet API - Webhook Integration
  • Silvanet Test Fires
    • Overview
    • Test fire preparation
    • Run test fires
    • Modify fire setups
  • Resources
    • Contact Technical Support
    • Release Notes
    • FAQs
      • General Questions
      • Border Gateway FAQs
      • Mesh Gateway FAQs
      • Wildfire Sensor FAQs
      • Site Management FAQs
      • User Management FAQs
    • Glossary of Terms
    • Status icons
    • Device troubleshooting
    • Firmware updates (FUOTA)
    • Declaration of Conformity (EU)
  • Chandler Burning Index (CBI)
Powered by GitBook

Docs Version

  • Version 4.6.4

Sales Enquiry

  • Contact Dryad Sales

Dryad

  • Dryad.net

© 2025, Dryad Networks GmbH, Eisenbahnstr. 37, 16225 Eberswalde, Germany

On this page
  • Wired - Mains and router
  • Wireless - Mains and mobile networks
  • Wireless - Solar and mobile networks
  • Satellite - No mobile and mains power source

Was this helpful?

Export as PDF
  1. Silvanet Deployment
  2. Deployment guidelines

Border Gateway scenarios

The Border Gateway can be deployed in various scenarios based on the availability of a power supply, Internet connectivity and location.

PreviousBorder Gateway guidelinesNextMesh Gateway guidelines

Last updated 3 months ago

Was this helpful?

Wired - Mains and router

In this setup, the Border Gateway uses a mains power supply (via PoE Injector) and a router (via Ethernet). The solar panel acts as a backup power supply.

When using the built-in Ethernet connection, this setup is supported only in combination with the PoE Injector. The solar panel does not provide enough energy to support Ethernet connectivity of the border gateway.

  • Internet connectivity: The Border Gateway is connected to a cable or ADSL router via Ethernet which is connected to the PoE injector. In case of loss of Internet connectivity via the router, the Border Gateway uses its built-in 4G/LTE-M (or 2G/GPRS) mobile radio or its satellite connectivity.

  • Power supply: The Border Gateway uses the PoE Injector connected to a mains power supply.

  • Backup power supply: In case of power failure, the solar panel is used.

PoE Injector

The Border Gateway includes a PoE Injector that provides a voltage range of between 36V and 57V. The PoE is IEEE 802.3af compliant. If a replacement is required, ensure it has the same specifications.

Wireless - Mains and mobile networks

In this setup, the Border Gateway is deployed in a location without a fixed-line Internet connection (without a router) but has a mains power supplied by the PoE Injector.

  • Internet connectivity: Provided by the Border Gateway's built-in 4G/LTE 2G/GPRS radio. In case of loss of Internet connectivity via 4G/LTE-M (or 2G/GPRS) mobile radio, the Border Gateway uses satellite connectivity.

  • Power supply: The Border Gateway uses the PoE Injector connected to a mains power supply.

  • Backup power supply: In case of power failure, the solar panel is used.

Wireless - Solar and mobile networks

Often Internet connectivity and a mains power source is unreliable in remote locations. Border Gateways deployed in these locations have neither fixed-line Internet connectivity nor a reliable power supply. In these cases, the Border Gateway uses its solar panel for a power supply. It uses mobile radio connectivity (if available) or a satellite uplink (to send fire alert signals to the Silvanet Cloud).

  • Internet connectivity: Provided by the Border Gateway's built-in LTE-M 2G/GPRS mobile radio, if a mobile tower is accessible. If a mobile tower is inaccessible, the Border Gateway uses a satellite uplink.

  • Power supply: Powered by the solar panel which charges the Border Gateway's internal energy storage. However, depending on the amount of sunlight, data transfer might be limited.

Satellite - No mobile and mains power source

Normally, as a fallback, the Border Gateway supports several methods to ensure uninterrupted Internet connectivity. If the Border Gateway does not have wired or wireless Internet connectivity and/or power supply, the solar panel and satellite ensures uninterrupted Internet connectivity.

  • Satellite replaces wired or wireless Internet connectivity: If the Border Gateway loses Ethernet due to network failure and cannot connect to a mobile network, a satellite uplink provides as backup connection. However, only Fire alarms are sent.

  • Solar panel replaces mains power supply: The solar panel provides a backup emergency power supply. The solar panel charges the internal batteries and allows the mobile data connection to be used. As the system runs in power saving mode, no other sensor data other than fire alerts can be transmitted.

Natural disasters and connectivity

Should the installation location of the Border Gateway have neither a mains power supply nor access to a mobile network (4G/LTE 2G/GPRS), the Border Gateway can still transmit minimal messages to the satellite.

However, messages are restricted to fire alerts only. This scenario is applicable, for example, where natural disasters like thunderstorms or earthquakes bring down Internet connectivity.

See .

PoE and router
PoE and mobile network
Remote location
Loss of power and Internet
PoE (Power over Internet)