Rare project developers

[Gabriel Tetzner <>]

Hi,

sudo nano docker-compose:

version: '3'
services:
  prometheus:
    image: prom/prometheus:latest
    container_name: prometheus
    restart: always
    ports:
    - 9090:9090
    command:
    - --config.file=/etc/prometheus/prometheus.yml
    volumes:
    - /etc/prometheus/prometheus.yml:/etc/prometheus/prometheus.yml:ro
    - /etc/prometheus/alert.rules:/etc/prometheus/alert.rules:ro

server forwarder prometheus:

server forwarder prometheus
 access-log
 access-rate 5 5000
 access-total 5
 access-peer 5
 port 9090
 logging
 target vrf inet
 target interface ethernet1
 target address 172.31.32.29
 target port 9090
 interface ethernet1
 vrf inet
 exit
!

Em seg., 15 de ago. de 2022 às 17:45, mc36 <> escreveu:

hi,

On 8/15/22 22:39, Gabriel Tetzner wrote:
> I think it is that way, since the public ip is associated with the freeRouter now, or is there another way to redirect the debian OS port (9090) to the freeRouter so that it is
> accessible externally? Or how to do this?
>

but in generally speaking, yeahh, the forwarder server is a way to do the work...
here is the test for it: http://sources.freertr.org/cfg/serv-forward.tst

 > But I can't access the prometheus server externally, I tried to make the server forwarder work to redirect this port, but I lose access to ssh from the vm.

did you created a new forwarder or reused the one for the ssh?

br,
cs