Age | Commit message (Collapse) | Author |
|
With a lot of firewall zones and rules the startup of vyos-router could
be aborted due to timeout on weak hardware (e.g. Intel ATOM D525).
Increase the systemd timeout value from 5 to 20 minutes to give the
vyos-service enough time to startup even on less powerful hardware.
(cherry picked from commit bdc9387450ff27981c7400b7f40b25275dbaa7cf)
|
|
|
|
|
|
|
|
|
|
at least until we figure out how to make watchfrr stop restarting
all daemons if just one failed and stop systemd from restarting
FRR if watchfrr is not enabled.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Do not use a shared library, since nothing else depends, or should depend on it.
|
|
|
|
|
|
T281: Add https support to the load command
|
|
* upstream/current:
Revert "T441: Remove dependency on vyatta-quagga. This package should not depend on any routing stack anyway."
|
|
depend on any routing stack anyway."
This reverts commit 460a08d652ab7f7f38bf6c5b46d57009300d81da.
|
|
This enables fetching a VyOS config from a http://foo/bar URL even when
http://foo/bar is a permanent redirect to https://foo/bar.
|
|
|
|
|
|
any routing stack anyway.
|
|
|
|
|
|
the return codes?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
if persistence is set for /config on an other device then also create and mount /config
|
|
Adding python-vyos-mgmt library to vyatta-cfg package
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|