Hello,
It appears you haven't launched BIRD for it to 1. create the socket, and
2. to listen on it.
If you don't have any other manually started running instances (to
verify, run ps -aux | grep bird and check if there are any other
instances), you should just run systemctl start bird and if you
Yes, you get connection refused. That generally means that bird daemon
is not listening to the socket. May be something strange has happened.
Check who may be listening to the socket:
netstat -nap | grep bird.ctl
You'll see the process if any. If nothing is there, then try to run
bird daemon again
Yes, but how can I do that command if when I try to connect to birdc I get
the error above?
Il Dom 22 Mar 2020, 09:18 Alexander Zubkov ha scritto:
> It is right there in the documentation:
> https://bird.network.cz/?get_doc=20=bird-4.html#cli-down
>
> down
> Shut BIRD down.
>
> On Sat, Mar 21,
