| Age | Commit message (Collapse) | Author |
|---|
|
data
Due to the AWK regex pattern data from a different peer was returned as
the first match was shown.
|
|
|
|
This change then adds supper to filter for given route types under a VRF
instance. You will have "show ip route bgp" in the global VRF and "show ip route
vrf red bgp" in the red VRF. Same commands apply to IPv6 routes.
|
|
http-api: T4071: allow API to bind to unix domain socket
|
|
|
|
configd: T2582: add smoketest for vyos-configd initialization
|
|
|
|
|
|
|
|
|
|
The BGP conditional advertisement feature uses the non-exist-map or the
exist-map and the advertise-map keywords of the neighbor advertise-map command
in order to track routes by the route prefix.
non-exist-map
=============
* If a route prefix is not present in the output of non-exist-map command, then
advertise the route specified by the advertise-map command.
* If a route prefix is present in the output of non-exist-map command, then do
not advertise the route specified by the addvertise-map command.
exist-map
=========
* If a route prefix is present in the output of exist-map command, then
advertise the route specified by the advertise-map command.
* If a route prefix is not present in the output of exist-map command, then do
not advertise the route specified by the advertise-map command.
This feature is useful when some prefixes are advertised to one of its peers
only if the information from the other peer is not present (due to failure in
peering session or partial reachability etc).
The conditional BGP announcements are sent in addition to the normal
announcements that a BGP router sends to its peer.
CLI nodes can be found under:
* set protocols bgp neighbor <ip> address-family <afi> conditional-advertisement
* set protocols bgp peer-group <p> address-family <afi> conditional-advertisement
|
|
|
|
In the past a peer-group was only assigned to the BGP process but not bound
to any neighbor. This has been changed.
|
|
This command is applicable at the global level and at an individual bgp level.
If applied at the global level all bgp instances will wait for fib installation
before announcing routes and there is no way to turn it off for a particular
BGP vrf.
|
|
Administrative shutdown of all peers of a bgp instance. Drop all BGP peers,
but preserve their configurations. The peers are notified in accordance with
RFC 8203 by sending a NOTIFICATION message with error code Cease and subcode
Administrative Shutdown prior to terminating connections.
This global shutdown is independent of the neighbor shutdown, meaning that
individually shut down peers will not be affected by lifting it.
|
|
This command enables rejection of incoming and outgoing routes having AS_SET
or AS_CONFED_SET type.
|
|
This command allows user to prevent session establishment with BGP peers with
lower holdtime less than configured minimum holdtime.
When this command is not set, minimum holdtime does not work.
|
|
Whenever BGP peer address becomes unreachable we must bring down the BGP
session immediately. Currently only single-hop EBGP sessions are brought down
immediately. IBGP and multi-hop EBGP sessions wait for hold-timer expiry to
bring down the sessions.
This new configuration option helps user to teardown BGP sessions immediately
whenever peer becomes unreachable.
This configuration is available at the bgp level. When enabled, configuration
is applied to all the neighbors configured in that bgp instance.
|
|
Set the period to rerun the conditional advertisement scanner process.
The default is 60 seconds.
|
|
|
|
expose OS
|
|
|
|
|
|
|
|
|
|
(cherry picked from commit 5e7243db4ced47dbad48913f86909ba284fcc24d)
|
|
(cherry picked from commit e73b40a04ee90a91b778ce72a60cbb751f42a306)
|
|
(cherry picked from commit a8ebb4817955b3f33f773a4d05c753dfc77958cd)
|
|
|
|
Background information [1]. Specifies whether an external control plane
(e.g. ip route encap/EVPN) or the internal FDB should be used.
[1]: https://legacy.netdevconf.info/2.2/slides/prabhu-linuxbridge-tutorial.pdf
|
|
|
|
|
|
This prevented VyOS to actually boot as the configuration could not be
loaded, as "system host-name" was unable to commit.
|
|
|
|
|
|
|
|
|
|
|
|
in __init__"
This reverts commit bcfe967f607a83192d75c01e7f414655891eec60.
|
|
Commit ee80d0aebd ("vyos.ifconfig: T2738: do not remove OS assigned IP
addresses from interface") addressed an issue with IP addresses added to
interfaces by daemons and not by the CLI. The solution in this commit for IP
address removal unfortunately did not cover VLAN (802.1q and 802.1ad) IP address
removal in the same way as it is done for non VLAN interfaces. The code was
missing.
(cherry picked from commit 91898b8bd876af6b4d7fae54981e78400f57e008)
|
|
(cherry picked from commit 1a814661a0ade01f144398b91dd6998e42018fdd)
|
|
T562: Config syntax for defining DNS forward authoritative zones
|
|
|
|
|
|
... thus we simply read the configuration the first time it really becomes
necessary and a message requireing the data needs it actually.
|
|
pppoe-server: T3006: Add range to regex generator
|
|
|
|
T3006: add a range validator
|
|
|
|
VRRP: T4033: VRRP script_security parameter removed
|
