Troubleshooting Repeater
The purpose of this section is to help you solve common problems that you may encounter while using the Repeater.
Connectivity test
In order to scan a target on a local network in the Repeater mode, you first need to make sure that a registered (created) Repeater has a proper access to the target.
You can use the bright-cli configure
command to run a simple connectivity testing process.
Prerequisites
- The machine on which the Repeater will be run must have the latest version of the Bright CLI.
- A valid API key (
Repeater API Token
) with the following scopes:bot
,scans:run
,scans:read
,scans:stop
.
You can create an organization API key or a personal API key. - A valid
Repeater ID
. To register (create) the Repeater, see Managing Repeaters.
Step-by-step guide
-
Run the command
bright-cli configure
in your console.
The Bright Network Testing wizard is launched. -
Enter your
Repeater ID
andRepeater API Token
in the relevant fields.
![Group 1316.png 1114](https://files.readme.io/54fbe11-Group_1316.png)
-
The CLI runs the first stage of the external communication diagnostics:
- Validating that the connection to amq.app.brightsec.com:5672 at port 5672 is open is required for the Repeater to reach the scan engine.
- Validating that the connection to app.brightsec.com at port is open is required to reach the Bright API endpoints.
- Verifying provided Token and Repeater ID is required to validate the credentials.
The diagnostics results are provided next to the validation parameters.
![external-diagnostics.png 888](https://files.readme.io/be58f5b-external-diagnostics.png)
Once the external communication diagnostics is completed, the CLI switches to the validation of the Repeater communication with local target application(s).
- Enter the target URL(s) to test if the Repeater can reach them.
![internal-testing.png 803](https://files.readme.io/0b2fe1b-internal-testing.png)
The internal communication diagnostics starts, and the Repeater tries to reach the specified applications.
![internal-diagnostics.png 711](https://files.readme.io/794808e-internal-diagnostics.png)
- Once the diagnostics is completed, you can see how many targets cannot be reached by the Repeater.
To exit the wizard, close the console.
Updated over 1 year ago