Rafael Possamai
Rafael Possamai
@netfreak98 The configuration variable `peeringdb-cache` is set to true by default, and it should help alleviate this. How often are you running `pathvector generate`? Personally, I run it nightly and...
> prefixes: > - [ "123.123.123.0/24","123,456", "123:4:567"] > - [ "2000:3000:400::/40", "123,457", "123:4:568"] > - 2a0a:2222:/32 > ``` > > or some sort of similar expression to add certain community...
> I think communities should be handled via a new configuration directive, i.e. #135 > What do you think about using both only-announce and prefix-communities for this use case? I...
> I seem to have found a way around this. If you install fping, and then from the web page Administration\Server management\phpIPAM settings make sure the FPing path is correct...
This is an excellent suggestion.
Here is my docker-compose for the Portainer "stack". Keep in mind I am passing through a directory on the host for the volume. ``` version: "3" services: tasmoadmin: image: ghcr.io/tasmoadmin/tasmoadmin:latest...
Thanks @inverse :) Sorting is going to be really useful
You can add custom NGINX config to the proxy host so that it adds headers to pass through the correct IP to origin server. If you search issues (open/closed) you...
Sorry for the noise - shortly after creating this issue I managed to figure this out. I used the following config line in my peer: ```pre-import-accept: 'if (bgp_path ~ [=...
I can confirm this is an issue when creating new proxy hosts, currently on latest version (2.3.1) running on docker (latest) on Debian 10.4.