Bug #3102
closed
bgpd not starting when "network" option is set in config file
100%
Description
openbgpd doesn't start with the default generated config file by the UI.
It also doesn't report any error in the log files.
The only message available on the UI is that the bgpd.sock file doesn't exist.
the workaround for me has been to remove entirely the "network connected" line in the configuration file.
the value "network static" was also tried creating the same problem.
The only way I could see the error was by starting bgpd on the command line, reporting the error in the config file on the "network connected" line.
I am running openbgpd 0.6 on pfsense 2.1-RC0 (amd64), built on Mon Jul 8 09:32:55 EDT 2013.
Updated by Jeremy Huylebroeck almost 12 years ago
based on the man page of bgpd.conf (http://www.openbsd.org/cgi-bin/man.cgi?query=bgpd.conf)
the correct syntax is "network inet connected" or "network inet6 connected"
which I confirm working after editing the conf file manually and restarting bgpd.
Updated by Renato Botelho almost 12 years ago
- Status changed from New to Feedback
what did you put on network field on GUI?
Updated by Jeremy Huylebroeck almost 12 years ago
in the GUI itself, I tried "connected" and "static".
the comment on GUI says the following:
"Announce the specified network as belonging to our AS. If set to connected, routes to directly attached networks will be announced. If set to static, all static routes will be announced."
Not being that familiar with openbgpd, I exactly did what it says...
What was the most confusing was the lack of error/logs.
Now that my bgpd.conf was edited by hand both on the command line and in the GUI, the "settings" screen is completely out of sync and doesn't show at all the values entered in the config file.
The settings screen says "static" but the network config in the bgpd.conf file is actually as follow:
network inet connected
network 172.30.254.64/28
Updated by Renato Botelho almost 12 years ago
- % Done changed from 0 to 100
Applied in changeset commit:d88e8e657a759c8f79fecf3a54d54b8225520b08.
Updated by Chris Buechler about 11 years ago
- Status changed from Feedback to Resolved