"No, no! The adventures first, explanations take such a dreadful time."
Lewis Carroll, Alice's Adventures in Wonderland & Through the Looking-Glass
Take a look at Alice-LG production examples at:
- https://lg.de-cix.net/
- https://lg.ams-ix.net
- https://lg.bcix.de/
- https://lg.megaport.com/
- https://lg.netnod.se/
- https://alice-rs.linx.net/
And checkout the API at:
- https://lg.de-cix.net/api/v1/config
- https://lg.de-cix.net/api/v1/routeservers
- https://lg.de-cix.net/api/v1/routeservers/rs1_fra_ipv4/status
- https://lg.de-cix.net/api/v1/routeservers/rs1_fra_ipv4/neighbors
- https://lg.de-cix.net/api/v1/routeservers/rs1_fra_ipv4/neighbors/R194_106/routes
- https://lg.de-cix.net/api/v1/lookup/prefix?q=217.115.0.0
Alice-LG is a BGP looking glass which gets its data from external APIs.
Currently Alice-LG supports the following APIs:
- birdwatcher API for BIRD
- GoBGP
Normally you would first install the birdwatcher API directly on the machine(s) where you run BIRD on and then install Alice-LG on a seperate public facing server and point her to the afore mentioned birdwatcher API.
This project was a direct result of the RIPE IXP Tools Hackathon just prior to RIPE73 in Madrid, Spain.
Major thanks to Barry O'Donovan who built the original INEX Bird's Eye BIRD API of which Alice-LG is a spinnoff
Alice-LG supports direct integration with GoBGP instances using gRPC. See the configuration section for more detail.
Alice-LG supports OpenBGP via bgplgd
and openbgpd-state-server
.
These examples include setting up your Go environment, if you already have set that up then you can obviously skip that
In case you have trouble with npm
and gulp
you can try using yarn
.
First add the following lines at the end of your ~/.bash_profile
:
GOPATH=$HOME/go
export GOPATH
PATH=$PATH:$GOPATH/bin
export PATH
Now run:
source ~/.bash_profile
# Install frontend build dependencies
sudo yum install golang npm
sudo npm install --global gulp-cli
sudo npm install --global yarn
go get github.com/GeertJohan/go.rice
go get github.com/GeertJohan/go.rice/rice
mkdir -p ~/go/bin ~/go/pkg ~/go/src/github.com/alice-lg/
cd ~/go/src/github.com/alice-lg
git clone https://github.com/alice-lg/alice-lg.git
cd alice-lg
make
Your Alice-LG source will now be located at ~/go/src/github.com/alice-lg/alice-lg
and your alice-LG executable should be at ~/go/src/github.com/alice-lg/alice-lg/bin/alice-lg-linux-amd64
An example configuration can be found at etc/alice-lg/alice.example.conf.
You can copy it to any of the following locations:
etc/alice-lg/alice.conf # local
etc/alice-lg/alice.local.conf # local
/etc/alice-lg/alice.conf # global
You will have to edit the configuration file as you need to point Alice-LG to the correct backend source. Multiple sources can be configured.
[source.rs1-example-v4]
name = rs1.example.com (IPv4)
[source.rs1-example-v4.birdwatcher]
api = http://rs1.example.com:29184/
neighbors_refresh_timeout = 2
# show_last_reboot = true
# timezone = UTC
# type = single_table / multi_table
type = multi_table
# not needed for single_table
peer_table_prefix = T
pipe_protocol_prefix = M
[source.rs1-example-v6]
name = rs1.example.com (IPv6)
[source.rs1-example-v6.birdwatcher]
api = http://rs1.example.com:29186/
[source.rs2-example]
name = rs2.example.com
group = AMS
[source.rs2-example.gobgp]
# Host is the IP (or DNS name) and port for the remote GoBGP daemon
host = rs2.example.com:50051
# ProcessingTimeout is a timeout in seconds configured per gRPC call to a given GoBGP daemon
processing_timeout = 300
OpenBGPD via openbgpd-state-server
:
[source.rs-example]
name = rs-example.openbgpd-state-server
[source.rs-example.openbgpd-state-server]
api = http://rs23.example.net:29111/api
# Optional response cache time in seconds
# Default: disabled (0)
cache_ttl = 100
OpenBGPD via bgplgd
:
[source.rs-example]
name = rs-example.openbgpd-bgplgd
[source.rs-example.openbgpd-bgplgd]
api = http://rs23.example.net/bgplgd
# Optional response cache time in seconds
# Default: disabled (0)
cache_ttl = 100
Launch the server by running
./bin/alice-lg-linux-amd64
We added a Makefile
for packaging Alice as an RPM using fpm.
If you have all tools available locally, you can just type:
make rpm
If you want to build the package on a remote machine, just use
make remote_rpm BUILD_SERVER=my-rpm-building-server.example.com
which will copy the dist to the remote server and executes fpm via ssh.
You can specify which system integration to use:
Set the SYSTEM_INIT
variable to upstart
or systemd
(default)
prior to building the RPM.
make remote_rpm BUILD_SERVER=rpmbuild.example.com SYSTEM_INIT=upstart
Alice now supports custom themes! In your alice.conf, you now can specify a theme by setting:
[theme]
path = /path/to/my/alice-theme
with the optional parameter (the "mountpoint" of the theme) url_base = /theme
You can put assets (images, fonts, javscript, css) in this folder.
Stylesheets and Javascripts are automatically included in the client's html and are served from the backend.
Alice provides early stages of an extension API, which is for now only used to modify the content of the welcome screen, by providing a javascript in your theme containing:
Alice.updateContent({
welcome: {
title: "My Awesome Looking Glass",
tagline: "powered by Alice"
}
});
For an example check out: https://github.com/alice-lg/alice-theme-example
The client is a Single Page React Application.
All sources are available in client/
.
Install build tools as needed:
npm install -g gulp-cli
Create a fresh UI build with
cd client/
make client
This will install all dependencies and run gulp
.
While working on the UI you might want to use make watch
,
which will keep the gulp watch
task up and running.
For convenience we added a Dockerfile
for building the frontend / client.
Create a fresh UI build using docker with
cd client/
# Dev build:
make -f Makefile.docker client
# Production build:
make -f Makefile.docker client_prod
You can use gulp with docker for watching the files while developing aswell:
make -f Makefile.docker watch
The development of Alice is now sponsored by
Many thanks go out to ECIX, where this project originated and was backed over the last two years.
Support for OpenBGP was sponsored by the Route Server Support Foundation.