prpl/prplMesh
1
0
Fork 0
mirror of https://gitlab.com/prpl-foundation/prplmesh/prplMesh.git synced 2025-12-20 01:21:22 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Page: Deploying prplMesh on PC (dummy)
Pages
Building prplMesh for RDK B Building prplMesh for prplOS Building prplMesh on linux (dummy) Configuring steering Deploying prplMesh on Axepoint or NEC AX3000HP Deploying prplMesh on Gl.iNet Deploying prplMesh on PC (dummy) Deploying prplMesh on Turris Omnia (RDK B) Deploying prplMesh on Turris Omnia (prplOS) Example data model FAQ & Glossary Getting started with prplMesh How to contribute How to update prlMesh version in prplOS and RDK B Introduction to prplMesh Obtaining pre built images Onboarding Backhaul Manager Onboarding debugging guide Onboarding with pWHM Persistent configuration PrplMesh NBAPI datamodel Pushing prplOS changes and bringing them into prplMesh in Gitlab Pushing prplOS code to gitlab Release schedule Static Puncturing TR 181 components configuration Triggering WPS Tutorials and videos Version 1.5 Version 1.6 Version 1.7 Version 2.0 Version 2.1 WPA3 Compatibilty Mode _sidebar home pWHM get EHTCapabilities and EHTOperations IEs prplMesh Northbound API prplMesh Onboarding prplMesh UI using MMX prplMesh Wireless Hardware Manager pwhm prplMesh with rbuscli prplmesh cli pwhm APMLD Datamodel pwhm Backhaul MLO STA support pwhm static puncturing
Clone
Deploying prplMesh on PC (dummy)
Raphaël Mélotte edited this page 2021-04-20 15:24:40 +00:00
Table of Contents

Build prplmesh using Docker

  1. Download sources and go to prplMesh directory
git clone https://gitlab.com/prpl-foundation/prplmesh/prplMesh.git
cd prplMesh
  1. Build prplMesh using Docker
./docker-builder.sh

prplMesh will be compiled under ./build. You can then use it by running it in Docker.

  1. Run the containers
./docker-runner.sh
  1. Run tests
./tests/test_gw_repeater.sh -f -u user -g gateway-$USER -r repeater1-$USER -r repeater2-$USER -d 7

Debugging

If you want to debug, you can't easily use the test_gw_repeater.sh script because it will run everything without attaching a debugger, and attaching it afterwards may be too late. You need to start the processes one by one:

./build/install/bin/beerocks_transport &
./build/install/bin/beerocks_agent &
gdb ./build/install/bin/beerocks_controller