VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git) https://git.amelek.net/vyos/vyos-1x.git/atom?h=1.3.2 2022-09-02T11:36:45+00:00 2022-09-02T11:36:45+00:00 initramfs initramfs@initramfs.io 2022-09-01T12:51:21+00:00 urn:sha1:0f1d29ac0480dc202595b96357789e6d15d49f2c Fixes several bugs around bonding member interface states not matching the committed configuration, including: - Disabled removed interfaces coming back up - Newly added disabled interfaces not staying down - Newly added interfaces not showing up in the bond 2022-08-29T18:40:24+00:00 Christian Poessinger christian@poessinger.com 2022-08-29T18:36:20+00:00 urn:sha1:27b94505582fb4f4c0c9188e8cc2026700a5a3bd Commit 31169fa8a763e ("vyos.ifconfig: T3619: only set offloading options if supported by NIC") added the new implementation which handles NIC offloading. Unfortunately every single implementation was copied from "gro" which resulted in a change to gro for each offloading option - thus options like lro, sg, tso had no effect at all. It all comes down to copy/paste errors ... one way or another. (cherry picked from commit b01f27b3bb3f4cbc6096011856d83009d0440313) 2022-08-22T16:39:52+00:00 Christian Poessinger christian@poessinger.com 2022-08-22T16:39:52+00:00 urn:sha1:2c7fe635994f81a4a8dd9708264b791ebc2a106b bridge: T4632: vlan aware bridge lacks CPU forwarding 2022-08-22T15:56:50+00:00 Christian Poessinger christian@poessinger.com 2022-08-22T15:52:58+00:00 urn:sha1:3b6f8bf8f7499af4a6841e5e1f1dafae9db55c38 The VLAN aware bridge was forwarding traffic between member ports, but traffic destined torwards the CPU was dropped. This resulted in a gateway not reachable or DHCP leases that could not be handed out. Tested via: VyOS set interfaces bridge br0 enable-vlan set interfaces bridge br0 member interface eth1 allowed-vlan '10' set interfaces bridge br0 member interface eth1 allowed-vlan '20' set interfaces bridge br0 member interface eth1 allowed-vlan '30' set interfaces bridge br0 member interface eth1 allowed-vlan '40' set interfaces bridge br0 member interface eth1 native-vlan '40' set interfaces bridge br0 member interface eth2 allowed-vlan '30' set interfaces bridge br0 member interface eth2 allowed-vlan '20' set interfaces bridge br0 member interface eth2 allowed-vlan '10' set interfaces bridge br0 member interface eth2 allowed-vlan '40' set interfaces bridge br0 vif 10 address '10.0.10.1/24' set interfaces bridge br0 vif 20 address '10.0.20.1/24' set interfaces bridge br0 vif 30 address '10.0.30.1/24' set interfaces bridge br0 vif 40 address '10.0.40.1/24' Arista vEOS vlan 10,20,30,40 interface Ethernet1 switchport trunk allowed vlan 10,20,30,40 interface Vlan10 ip address 10.0.10.2/24 interface Vlan20 ip address 10.0.20.2/24 interface Vlan30 ip address 10.0.30.2/24 interface Vlan40 ip address 10.0.40.2/24 interface Ethernet1 switchport trunk allowed vlan 10,20,30,40 switchport mode trunk spanning-tree portfast Cisco vIOS interface GigabitEthernet0/0 ip address 10.0.40.3 255.255.255.0 duplex auto speed auto media-type rj45 ! interface GigabitEthernet0/0.10 encapsulation dot1Q 10 ip address 10.0.10.3 255.255.255.0 ! interface GigabitEthernet0/0.20 encapsulation dot1Q 20 ip address 10.0.20.3 255.255.255.0 ! interface GigabitEthernet0/0.30 encapsulation dot1Q 30 ip address 10.0.30.3 255.255.255.0 ! (cherry picked from commit f60d0e1ce029925b843f635b36154c90049b9577) 2022-08-19T18:33:31+00:00 Christian Poessinger christian@poessinger.com 2022-08-04T06:28:55+00:00 urn:sha1:12c9c19a2f4f55ab1d7a70b496473ac41212c510 (cherry picked from commit 475fbb785dca76868715827833dc44115635c4a6) 2022-08-04T14:41:13+00:00 Daniil Baturin daniil@vyos.io 2022-08-04T14:41:13+00:00 urn:sha1:c8ba6bc59d981309552c90e845c560ec2bd9b21c mtu: T4572: Add DHCP-option MTU to get values from DHCP-server 2022-08-01T16:24:38+00:00 Viacheslav Hletenko v.gletenko@vyos.io 2022-08-01T13:19:53+00:00 urn:sha1:67583141f433c31ebccc8eeba06b2b285636e680 Ability to get MTU from DHCP-server and don't touch it per any interface change if interface 'dhcp-options mtu' is configured (cherry picked from commit 29b0ee30bf2622a40ca3d17e3f6b9e94e5b62072) 2022-08-01T15:30:30+00:00 Christian Poessinger christian@poessinger.com 2022-08-01T15:27:59+00:00 urn:sha1:8c10a12251533c9e8f00d2f52dc5d23f8bb9a3ae We should not print the entire dictionary - we only need the bridge interface name: Bug: Cannot assign address to interface "eth1" as it is a member of bridge "{'br0': {'allowed_vlan': ['5-50', '101'], 'native_vlan': '101'}}"! Fixed: Cannot assign address to interface "eth1" as it is a member of bridge "br0"! (cherry picked from commit 71f2f2d789bd3452ca7b5306f39df5f6537bfef0) 2022-07-31T17:43:09+00:00 Christian Poessinger christian@poessinger.com 2022-07-30T17:52:52+00:00 urn:sha1:8e54a26f11fee2578754d2fd99d4820c39d8c236 ... otherwise functionality like bridge VLANs will loose configuration on membe rinterface update (e.g. description) (cherry picked from commit a295ec1fc4cb9cdbb0bd5efd7c8e72060ce036f5) 2022-07-31T17:43:03+00:00 Christian Poessinger christian@poessinger.com 2022-07-30T17:52:03+00:00 urn:sha1:0bf98f8d75304b9554efd68e11ede9f72bed71d0 (cherry picked from commit 54227591a0eb3c7aa8c896c6ec8b1826ce070ddf)