Age | Commit message (Collapse) | Author |
|
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.
|
|
|
|
|
|
No sequence number support in FRR 7.3 for
- community-list
- extcommunity-list
- large-community-list
|
|
(cherry picked from commit 2c798f7b9064bc9833935eae534a885b97d34738)
|
|
(cherry picked from commit 1ac2e363013d0b04ea2eae66607e7c3e54aade92)
|
|
|
|
(cherry picked from commit 99b1d9ee28d11d43840f9e2c1c9e8bda1176d866)
|
|
(cherry picked from commit bddeae3755c8d83f4c47bc3b3798858a95427530)
|
|
In addition to commit cf1156a60e ("ethernet: T3163: probe driver for maximum
rx/tx ring-buffer size") this extends the logic in a way as not every driver
supports setting the buffers at all so it will properly error out.
When invoking "ethtool -g" both stdout and stderr are captured and no exception
is raised if it's an unsupported driver feature. The verify() section will
inform the user about the illegal operation.
(cherry picked from commit 159899ed9ba5661e4bdcfdadf1292e237f117063)
|
|
(cherry picked from commit 25b86442d987bf57a801a607648527aaf6158d69)
|
|
(cherry picked from commit 913cd3c8809ea8a17ede7608654e956dcf718980)
|
|
smoketest: T3211: Extend smoketest for redistribute isis
|
|
|
|
rip: T3211: Add redistribute protocol IS-IS into rip
|
|
|
|
(cherry picked from commit 09b1b533d14e029427234ca153c0b700dbf04a09)
|
|
(cherry picked from commit a3e11ace758f447ddbbabd31d4903b3f71baa0b8)
|
|
VXLAN will get tos, ttl and flowlabel options thus make individual parameter
settings reusable by splitting tunnel-parameters-ip.xml.i into individual files.
(cherry picked from commit 577ae00d0c7329bea8102fcf75de82cb188b4fb8)
|
|
|
|
(cherry picked from commit 3c64c79d7977869da3ca4dc70eb97ff9c6682e52)
|
|
(cherry picked from commit cf1156a60e1d03a752cde0baadbc9ac8118b2a52)
|
|
|
|
(cherry picked from commit f67568bc2307706116f5509fca3a188dc4ab5d48)
|
|
If the subprocess is producing enough data (in this case showConfig on a
large config file), then the construction:
p = subprocess.Popen(.., stdout=subprocess.PIPE, ..)
p.wait()
will deadlock with the subprocess waiting for data to be consumed, while
the Python process waits for its termination. So consume data, then wait
for termination.
(cherry picked from commit 83bcd13775323bec35d018223029e9a8b13179c8)
|
|
.. if BFD connections will be source from invalid sources this will
crash bfdd in FRR 7.3
(cherry picked from commit 82bdae42ceefb1132f8a98628fa9681543f4f269)
|
|
|
|
is_ip_network and compare_netmask Jinja2 filter have been added via commit
920789798 ("nat: T2947: add many-many translation") on "current" and are
required for the 1:1 NAT functionality.
jinja2.exceptions.TemplateAssertionError: no filter named 'is_ip_network'
|
|
(cherry picked from commit b01c23d48a3ff3b95175568198fb307ffbc04b86)
|
|
Fix destination NAT template trying to map source->translation
instead of destination->translation.
Fixes https://phabricator.vyos.net/T3307
(cherry picked from commit 4a0504a96cf0f3078e964ed201f196fb55172e00)
|
|
(cherry picked from commit cec4b325ea014c09d3c60fac07651ec2a0b2d522)
|
|
(cherry picked from commit 55b763e1a8ae48f1bc7f46c341479f6140cad3b6)
|
|
deprecation warnings.
|
|
(cherry picked from commit f89969c1729a94901a817bd97da6f5b2a3712af0)
|
|
(cherry picked from commit 46b749388e0198f0cb3eb5eca1bd1d6e940b2702)
|
|
(cherry picked from commit 72c82bf8f2c294ca9023d2cbf9285b679188fae3)
|
|
(cherry picked from commit e84dece28a7f3e46235f178eec5622547cb2eab6)
|
|
Commit 0f8beae7426 ("system: T2486: migrate disable-dhcp-nameservers to
name-servers-dhcp") added a migration script for moving the name-servers.
A small glitch was introduced when referencing vif-c interfaces unter a vif-s
interface where a variable got referenced which was not defined.
(cherry picked from commit 89108f629ec8cc6990473468c1c67ffa8742b884)
|
|
(cherry picked from commit e7d5f996e1ecca228bc67def2b19a0790d8c7370)
|
|
If the RPKI cache name equals the configured address, renaming is not possible,
as rename expects the new path to not exist.
(cherry picked from commit af2a22fb114b7d00f50fb32dc64b49e132ccca61)
|
|
(cherry picked from commit 37c961b8fc57d0f811758034f51fe0fed401275a)
|
|
|
|
(cherry picked from commit ea4c72ed0dbcee3f7e8f9693c5310190833651d8)
|
|
(cherry picked from commit dd89255dcc82e315d6106936a97b8c0be360519b)
|
|
(cherry picked from commit 3dfbd19e0f3676d70dc32f0e001e4589eb9e97d6)
|
|
In the past it was possible to configure a vif-s interface and a vif interface
both with the same VLAN ID. VyOS 1.2 reported a Kernel error:
RTNETLINK answers: File exists
Error creating VLAN device eth1.100
so this should not be possible at all in VyOS 1.3
(cherry picked from commit ccd516b4d10c518ea445928c01d6c7dc2770777b)
|