| Age | Commit message (Collapse) | Author |
|---|
|
The CLI begin transaction restrictions make this impossible to
do in a stable manner.
Related to bug 4537
|
|
node.def below node.tag is meaningless
|
|
Move the default import-check enabled from template to command line
option in bgpd. This resolves some of the startup issues.
|
|
BGPD needs to be started when parameters and neighbors are set.
Bug 4486
|
|
need remote-as to be highest priority sibling
Bug 4486
|
|
Multiple value nodes are never updated, only created or deleted.
|
|
This is what CLI Primer says is supposed to work.
|
|
New CLI appears to require 'update:' rather than 'create:' on
tag nodes in order for them to get applied correctly. Workaround
this by changing all the create: to update: in Quagga config
Bug 4486
|
|
Use same syntax as other nodes
Precursor to automated edit of nodes for other bugfix.
|
|
The new CLI doesn't fail transaction automatically when one command fails.
|
|
This may resolve some of the priority issues.
|
|
Bug 4391
Quagga allows IP address or interface as update source, so generalize
existing template.
|
|
There were several problems with the quagga-manager update.
1) can not have multiple end: tags in same tree path
2) can not shutdown bgp without losing policy
3) watchquagga timing races
|
|
Wrong way to fix it.
This reverts commit b6f1a09410983507a7cfc8b08dafbd13600ed8e5.
|
|
|
|
Fixing vyatta-bgp checker found a bug in this template.
Template refered to wrong node in commit check.
It would do:
vyatta-bgp.pl --check-as --as <neighbor> --neighbor soft-reconfiguration
|
|
Avoid config issues with update on multi-node
|
|
|
|
|
|
|
|
explicit stop is not needed. Removed from
delete node, but might promote end action to delete action
|
|
|
|
|
|
Use scripts to do start/stop (instead of disable template).
Integrate reload into new quagga-manager script
|
|
Need way to get daemons started before top level node.
Really a hack because of the way priorities are managed on
node hieararchy
|
|
Much cleaner to do sudo once rather than repeatedly
|
|
1. Shutdown bgp on last neighbor removed
2. use daemon name consistently
3. change options to watchquagga
|
|
Bug 3828
Start protocols from configuration system, and use watchquagga
to restart protocol daemons after failure
|
|
This reverts commit 588492cf8a9ddf438b649c6db4986bcab9c22435.
|
|
|
|
|
|
|
|
|
|
|
|
No longer need the perl wrapper, the logging and error suppression
are now in the command itself. This helps with the speed of route
creation with lots of routes.
|
|
Wrong shell variable in earlier commit
|
|
Using perl to check prefix boundary, is slow because of the overhead
of compiling the same script many times. So convert this simple task
to a C program.
|
|
Quagga supports BGP over TCP-MD5 now, so need CLI support.
Bugfix: 2661
|
|
|
|
- help strings standardized in vyatta-cfg-quagga
|
|
|
|
|
|
add comp_help strings to BGP
remove enforce-capability parameter since in quagga it's an alias
remove interface parameter since it's ipv6 related
remove password parameter as the md5 code isn't in the current release
fixed a couple of parameter relationship bugs
|
|
|
|
|
|
|
|
- BGP - peer-port range changed to <1-65535>, also indicated in the help
|
|
|
|
engine, "neighbor A.B.C.D update-source W.X.Y.Z" always works, and there is no ip address saved under interface hence "neighbor A.B.C.D update-source INTERFACE_NAME" doesn't work.
2. Removed the last $VAR(@) from the "delete:" part, since the routing engine treats "no neighbor A.B.C.D update-source W.X.Y.Z" as "Unknown command", but "no neighbor A.B.C.D update-source" does work and accomplishes the deletion correctly.
|
|
|
