Age | Commit message (Collapse) | Author |
|
Removing a VLAN (VIF) interface from the CLI always deleted all interfaces the
kernel listed as "upper" in the /sys/class/net folder. This had the drawback
that when deleting a VIF, also the VRF interface was simply deleted - killing
all VRF related services.
(cherry picked from commit 6458f91735412fb2e6e7e37f7b3e6ca587a5a235)
|
|
Add a new CLI command "monitor log colored" to run the log file monitoring
through grc (https://github.com/garabik/grc).
(cherry picked from commit 6330708f7ad50e56b16e1c7bc671eaddcd758bdb)
|
|
|
|
(cherry picked from commit 52323dcd620ef1b6d716787c9c4729b9ae9ee7e0)
|
|
(cherry picked from commit f22fa8e6454b1cd2539ddb7c354ac9eeeac725c5)
|
|
T3356, T3284: Backport remote.py fixes to Equuleus
|
|
|
|
op-mode: ipsec: T3055: Fixed parsing peer name error
|
|
|
|
(cherry picked from commit 137f50a1f00073842364ee373f98e1e215671c6b)
|
|
We can leak routes back to the default VRF, thus the check added by commit
9184dfb5 ("static: vrf: T3344: add target vrf verify()") must have a "bail out"
option when one want's to leak routes into the default VRF.
(cherry picked from commit 5adcc4ca30676338fca9a06409bbc72af4f68a1f)
|
|
ddclient: T3422: Allow zone property with cloudflare protocol
|
|
Allows Dynamic DNS services with custom names to use the zone field if
the protocol is set to cloudflare
|
|
T3284: Merge Paramiko-based remote.py implementation
|
|
|
|
The regex only validated interfaces according to the VyOS naming scheme, but
third party interfacs that are legit (e.g. exists within the kernel) failed
to validate.
The validator now also supports any kind of local interfaces attached to
the OS kernel.
(cherry picked from commit 911fe645928750f3ce38061a94c9b6db50db0749)
|
|
When NTP is executed inside a VRF context, we also must execute the op-mode
commands inside the given VRF.
This is a workaround until the op-mode programming library from T3402 is
available.
(cherry picked from commit f411351baef67740b76e800161fe55f495c4bd92)
|
|
(cherry picked from commit dd2eb5e5686655c996ae95285b8ad7eb73d63d0b)
|
|
(cherry picked from commit ce0600e97baec18c1781605f3a80c26d4ed01e2b)
|
|
(cherry picked from commit fbc10c8ccdcba6b8625cc8286d59bd854e8b30f2)
|
|
(cherry picked from commit ce7a4b77a59952042b698f6a1edabcfe26d90902)
|
|
|
|
Turns out we still need it, else a MC7710 card won't work on an APU4 device.
This reverts commit f9e0fb6bffd41c143ff5454c3b73cca4a588ca86.
|
|
(cherry picked from commit 658456982ad4543790a3835f6ddbfbe3b583ec44)
|
|
VyOS 1.2 (crux) rejected prefixes other then of site /64.
[ interfaces ethernet eth0 ipv6 address eui64 2006:ab00:abe1::2/127 ]
Error: Prefix lenght is 127. It must be 64.
Same should be done on VyOS 1.3 and newer
(cherry picked from commit 6f6cd6552384704700f08e9367e167796b1f7fde)
|
|
(cherry picked from commit b9ba3c08736b63c2455c06e6f36108128776fa00)
|
|
This is an extension to commit 801c5235 ("xdp: T2666: disable this highly
experimental feature in 1.3 LTS") by dropping all XDP references in the
equuleus codebase.
|
|
As the amount of include files now has reached a certain amount, it is getting
more and more crowsded, thuse introducing "per topic" subdirectories on the
filesystem to keep a clean structure makes sense.
|
|
As the amount of include files now has reached a certain amount, it is getting
more and more crowsded, thuse introducing "per topic" subdirectories on the
filesystem to keep a clean structure makes sense.
|
|
When including XML files they all contained a comment from where the snipped
had actually been included from. The comment had been "included start" and
"included end" instead of "include start" and "include end".
This commit corrects the glitch.
(cherry-picked from commit ee2dfee43f8319726c2225a5ad2367d936ec3176)
|
|
To also have an inline reference of the guidlines for fast access, copy the
contents of the "Prepare patch/commit" and "Writing good commit messages" to
out CONTRIBUTING document.
By this you get a fast reference to the guidelines when opening up a
PullRequest.
|
|
(cherry picked from commit 894a5d6daee5f785834a2f360d66eb9b8e112465)
|
|
A user can specify both "set system console device ttyS0 speed '9600'" and
"set service console-server device ttyS0 speed 9600". A serial interface can
not be used multiple times.
commit now produces an error:
vyos@vyos# commit
[ service console-server ]
Port "ttyS0" requires speed to be set!
|
|
rpki: T3399: Fix template dashes replace
|
|
|
|
(cherry picked from commit 8b195a2665ca9efa31ecbd297a60f2b19106cd66)
|
|
The completion helper was directly called on the /dev/serial/by-bus directory,
but it was not verified if the directory exists at all.
(cherry picked from commit e06e5b914cd0b51848d9b836467f49b99cfe40cc)
|
|
VyOS 1.2 had a default ttl of 16 hardcoded to the node.def file [1], so until
this is handled via a migration script we have to obey that particular
setting.
[1]: https://github.com/vyos/vyatta-cfg-system/blob/crux/templates/interfaces/vxlan/node.def#L23
|
|
Linux does not support changing the remote address from any (multipoint
GRE as used by DMVPN) to a discrete remote address. THis will return an
error: add tunnel "tun1" failed: Invalid argument
This can be handled by detecting the mGRE -> GRE change and re-create the tunnel
silently.
(cherry picked from commit ea2a22f7844735021fb638c911527e612abfbc69)
|
|
There had been four implementations of "ip -d -j link show interface" scattered
accross the codebase. Those implementations have now been combined into a new
helper:
vyos.util.get_json_iface_options()
(cherry picked from commit f13cc56d665a91ff3fac47df260301afefb1a3a5)
|
|
(cherry picked from commit bb3fb05b0dce3b4dc4f84b16fc257ea65b64953a)
|
|
Commit 52ee92b8 ("pppoe: T3386: Fix client ip-pool stop range") fixed the
generated client range configuration line for Accel-PPP but missed out altering
the testcase, too which validates the generated configuration line.
(cherry picked from commit 00d3ba7c7bc2f16a0a029d5f1be964bcd3c45fd9)
|
|
(cherry picked from commit 4cc8424dc79cef10199720b95ab65bba18b3ba03)
|
|
(cherry picked from commit 52ee92b8edf851939c5ea3dc90fac3f5f90096c2)
|
|
When a VIF/VLAN interface is placed in admin down state but the lower
interface, serving the vlan, is moved from admin down -> admin up, all its
vlan interfaces will be placed in admin up state, too.
This is bad as a VLAN interface will become admin up even if its specified as
admin down after a reboot.
To reproduce:
set interfaces ethernet eth1 vif 20 disable
set interfaces ethernet eth1 disable
commit
delete interfaces ethernet eth1 disable
commit
Now check the interface state and it returns UP,LOWER_UP
7: eth1.20@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:50:56:b3:09:07 brd ff:ff:ff:ff:ff:ff
inet6 fe80::250:56ff:feb3:907/64 scope link
valid_lft forever preferred_lft forever
(cherry picked from commit 49bc3f1e3ff8416908fc986bb60b444a75a1722d)
|
|
(cherry picked from commit 04724ed189553ce43f8504f68fef8024ef5796de)
|
|
(cherry picked from commit d41e8e860a66f45d295081f024aa2918f221443f)
|
|
(cherry picked from commit 5bcc549edeaeaa767d77a68b33751e834d467c34)
|
|
Linux prevents changing parameters on a gretap (which is used by gre-bridge)
interfaces. To overcome this limitation a tunnel must be destroyed and recreated
on demand when gre-bridge is used.
|
|
|