VyOS command definitions, scripts, and utilities (mirror of https://github.com/marekm72/vyos-1x.git) https://git.amelek.net/marekm72/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-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-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-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) 2022-07-31T17:42:57+00:00 Christian Poessinger christian@poessinger.com 2022-07-30T17:14:10+00:00 urn:sha1:a782eb0711af53a0565589d67056c9706ec328fc Interface() base class already takes care about VLAN creation/removal of newly added or no longer required interfaces. No need to code this logic again. (cherry picked from commit 41477cc85208507be55f8db4e412ad78eae764eb) 2022-07-18T06:14:33+00:00 Christian Poessinger christian@poessinger.com 2022-07-14T19:46:55+00:00 urn:sha1:8bbde65979519d38712b1bd55cf50042513546bf When removing a VRF from an ethernet interface and adding the interface to a bond in the same commit led to an OSError: [Errno 16] Device or resource busy! (cherry picked from commit 3592f56a8deb6c44dcdd7a44ef54fc2c39eb1a3b) 2022-07-18T06:14:33+00:00 Christian Poessinger christian@poessinger.com 2022-07-10T21:01:09+00:00 urn:sha1:57d54b249ff04f70177b31fae0c10ac6677148ee Linux Kernel supports to specify the MII link monitoring frequency in milliseconds. This determines how often the link state of each slave is inspected for link failures. A value of zero disables MII link monitoring. A value of 100 is a good starting point. The default value is 100. set interfaces bonding bond0 mii-mon-interval <n> (cherry picked from commit 4315c8fa5bb090e2b7edd6bda205041623e2511d) 2022-07-11T06:17:50+00:00 Christian Poessinger christian@poessinger.com 2022-07-10T20:33:25+00:00 urn:sha1:872423e103a756ec470846108143e28f70c4d254 (cherry picked from commit cabfd006bed9cd2d1512cb313616a8e97fe29b9e)