This command allows you to detect any connectivity problems when scanning a target hosted on your local network:
bright-cli configure. Also, it can be used to diagnose the connectivity when you run a scan via the local Repeater. This enables you to preliminary check if the Repeater can reach all the local targets. You will be able to reveal and fix the connectivity problems before you run a scan.
The command initializes the network testing wizard. Simply follow the wizard instructions to diagnose the communication between the Repeater and your local targets.
To run the testing, you will need a valid Repeater ID and an API token with the bot scope. You can get them in the Bright app:
- To create the Repeater, see Managing Repeaters.
- To create an API key, see organization API key or personal API key.
To find the connectivity test step-by-step guide, see Troubleshooting.
|Provides a full IP trace on a specific target. It means that this option returns a list of all the IPs along the route of the request, thus allowing you to detect the connectivity bottlenecks. You simply need to specify the target hostname or IP address to initialize the diagnostics.
- (For Windows users). Some Windows users might need to allow the ICMP network traffic through a firewall to enable this option. For the configuration instructions, see the Microsoft docs.
- (For Linux users). To enable this option on Linux, you need to apply the
CAP_NET_ADMIN capabilities to the
bright-cli or node binary. Once these capabilities are applied to the file, non-root users will be able to run this option. To apply the capabilities, you need to issue the following command:
sudo setcap 'cap_net_admin,cap_net_raw=eip' which node.
For more information, see here.
|Set the max time-to-live (max number of hops) used in outgoing probe packets.
|Set the number of probes per 'ttl'.
|Enables testing of the network connectivity on single or multiple targets. You are only required to enter the URL(s) of your internal (local) target application(s) to initialize the diagnostics. Multiple URLs should be separated by commas.
Updated 4 months ago