add doc how to activate the local configuration interface

Signed-off-by: Marek Küthe <m.k@mk16.de>
This commit is contained in:
Marek Küthe 2023-01-08 00:20:00 +01:00
parent f5b4c8b4d2
commit f5f86e6365
No known key found for this signature in database
GPG Key ID: 7E869146699108C7
2 changed files with 42 additions and 0 deletions

View File

@ -138,6 +138,25 @@ babeld -c <config>
Once babeld is started, forwarding is enabled in the kernel for IPv4 and IPv6. As soon as babeld is stopped, forwarding is deactivated again. A separate enabling like with bird is not necessary. So if you use babeld, you can ignore the steps of [IPv6 forwarding](../forwarding).
## Local configuration interface
babeld offers a local configuration interface. This can be activated with the flag `-g`. For example, to enable the configuration interface on port `33123`, you can use the following command:
```
babeld -g 33123
```
The configuration interface can be used to find out various status information on the one hand and to configure babeld on the other. Furthermore, the configuration interface can be used by monitoring programs such as babelweb2.
To connect to the configuration interface, you can use telnet:
```
telnet ::1 33123
```
With the command `dump` you can display the current status:
```
dump
```
## Further links
- [babeld homepage](https://www.irif.fr/~jch/software/babel/)

View File

@ -0,0 +1,23 @@
# babelweb 2
babelweb 2 is a monitoring tool for Babel. It shows with a web interface the current neighbors, the current routes and a graphical overview of the babel network.
## Installation
First you have to download go. You can do this on Debian for example with the following command:
```
sudo apt install golang
```
After that you have to clone the current git repo and compile the program:
```
git clone https://github.com/Vivena/babelweb2
cd babelweb2
go build
```
Now you have an executable program `babelweb2`.
By default, the web interface runs on port 8080. You can also specify a different endpoint with the `-http` parameter.
babelweb2 uses the local configuration interface of babeld. This must have been activated beforehand. babeld assumes that this is active on `[::1]:33123`. Alternatively, you can specify the endpoint with the `-node=` flag.