- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Feb 27 2021
The neighbor can contain a string
set protocols bgp 64501 neighbor eth1 set protocols bgp 64501 neighbor eth1 remote-as 65001
Feb 26 2021
Something wrong with that check https://github.com/vyos/vyos-1x/blob/8732ebc46a2daddc6e4dfa05f3f70bf2ac9400af/src/conf_mode/protocols_bgp.py#L170-L171
Fail
set protocols bgp 64501 neighbor 203.0.113.1 remote-as 65001 set protocols bgp 64501 neighbor 203.0.113.1 peer-group FOO set protocols bgp 64501 peer-group FOO
PR https://github.com/vyos/vyos-1x/pull/748
Add checks for neighbor "is_addr_assigned"
Thanks @rob, it is true that nginx is not redirecting to a non canonical https port. Using the nginx custom https status code 497, this can be added; I will update the template accordingly.
This should now work aswell with the latest vyos 1.3 versions!
Tested in the lab the following simple topology on 1.2.6-S1 and 1.3-beta, behavior the same and GARP works by default.
VyOS1 config
set high-availability vrrp group eth1 hello-source-address '100.64.0.1' set high-availability vrrp group eth1 interface 'eth1' set high-availability vrrp group eth1 peer-address '100.64.0.2' set high-availability vrrp group eth1 rfc3768-compatibility set high-availability vrrp group eth1 virtual-address '100.64.0.50/24' set high-availability vrrp group eth1 vrid '1' set interfaces ethernet eth0 address 'dhcp' set interfaces ethernet eth0 duplex 'auto' set interfaces ethernet eth0 hw-id '50:00:00:01:00:00' set interfaces ethernet eth0 speed 'auto' set interfaces ethernet eth1 address '100.64.0.1/24' set interfaces ethernet eth1 duplex 'auto' set interfaces ethernet eth1 hw-id '50:00:00:01:00:01' set interfaces ethernet eth1 speed 'auto'
VyOS2 config
set high-availability vrrp group eth1 hello-source-address '100.64.0.2' set high-availability vrrp group eth1 interface 'eth1' set high-availability vrrp group eth1 peer-address '100.64.0.1' set high-availability vrrp group eth1 virtual-address '100.64.0.50/24' set high-availability vrrp group eth1 vrid '1' set interfaces ethernet eth0 address 'dhcp' set interfaces ethernet eth0 duplex 'auto' set interfaces ethernet eth0 hw-id '50:00:00:02:00:00' set interfaces ethernet eth0 speed 'auto' set interfaces ethernet eth1 address '100.64.0.2/24' set interfaces ethernet eth1 duplex 'auto' set interfaces ethernet eth1 hw-id '50:00:00:02:00:01' set interfaces ethernet eth1 speed 'auto'
In traffic dump on VyOS3 we can see traffic when BACKUP node switched to MASTER state
14:02:34.152959 50:00:00:02:00:01 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 100.64.0.50 (ff:ff:ff:ff:ff:ff) tell 100.64.0.50, length 28 14:02:34.153042 50:00:00:02:00:01 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 100.64.0.50 (ff:ff:ff:ff:ff:ff) tell 100.64.0.50, length 28 14:02:34.153086 50:00:00:02:00:01 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 100.64.0.50 (ff:ff:ff:ff:ff:ff) tell 100.64.0.50, length 28 14:02:34.153090 50:00:00:02:00:01 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 100.64.0.50 (ff:ff:ff:ff:ff:ff) tell 100.64.0.50, length 28 14:02:34.153092 50:00:00:02:00:01 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 100.64.0.50 (ff:ff:ff:ff:ff:ff) tell 100.64.0.50, length 28 14:02:34.153467 50:00:00:02:00:01 > 50:00:00:01:00:01, ethertype IPv4 (0x0800), length 54: 100.64.0.2 > 100.64.0.1: VRRPv2, Advertisement, vrid 1, prio 100, authtype none, intvl 1s, length 20 14:02:35.153544 50:00:00:02:00:01 > 50:00:00:01:00:01, ethertype IPv4 (0x0800), length 54: 100.64.0.2 > 100.64.0.1: VRRPv2, Advertisement, vrid 1, prio 100, authtype none, intvl 1s, length 20 14:02:36.154117 50:00:00:02:00:01 > 50:00:00:01:00:01, ethertype IPv4 (0x0800), length 54: 100.64.0.2 > 100.64.0.1: VRRPv2, Advertisement, vrid 1, prio 100, authtype none, intvl 1s, length 20 14:02:37.154233 50:00:00:02:00:01 > 50:00:00:01:00:01, ethertype IPv4 (0x0800), length 54: 100.64.0.2 > 100.64.0.1: VRRPv2, Advertisement, vrid 1, prio 100, authtype none, intvl 1s, length 20 14:02:38.154470 50:00:00:02:00:01 > 50:00:00:01:00:01, ethertype IPv4 (0x0800), length 54: 100.64.0.2 > 100.64.0.1: VRRPv2, Advertisement, vrid 1, prio 100, authtype none, intvl 1s, length 20
The same behavior with rfc3768-compatibility option.
I think we don't need to change behavior because it should be suitable for all cases.
Your rolling release so old. As I remember it was a bug with FRR, which was fixed.
Try more latest versions or vyos-1.3.0-rc1 https://community.vyos.net/get/snapshots/
@c-po confirmed, works OK in vyos-1.3-beta-202102250443-amd64.iso. Thanks a lot!
Put in a PR for this, https://github.com/vyos/vyos-1x/pull/744
Feb 25 2021
This should have been fixed in the latest 1.3 beta - please try again
It seems the same problem (lack of "ethtool -g" support) happens also with "veth" interfaces.. ref T2516
I'm seeing the same problem with Xen HVM guests, where the paravirtualized nic-driver "xen_netfront" doesn't seem to support "ethtool -g".. ref T3347
Please ignore this task, it works fine!
Feb 24 2021
I can confirm this bug is still present in the latest 1.3-rolling-202101 snapshot as well as the latest stable release. (1.2.6-S1)
Better not touch crux ;)