Query: Search

	Include stories about projects I am a member of.

@Viacheslav we already have ip6tnl support.

I've had this bite me a few times now as well, but I wasn't able to pin it down before to being a bug.

Please retest with the latest 1.4 rolling version. TTL can now be set.

It seems it some upstream issue

vyos@r-roll01# sudo ip tunnel add tun22 mode gre local 203.0.113.1 remote any 
[edit]
vyos@r-roll01# sudo ip tunnel change tun22 mode gre local 203.0.113.1 remote 203.0.113.254
add tunnel "tun22" failed: Invalid argument
[edit]
vyos@r-roll01#

For 1.4 the same fail
Config

set interfaces tunnel tun1 address '10.20.30.1/30'
set interfaces tunnel tun1 encapsulation 'gre'
set interfaces tunnel tun1 source-address '192.168.122.11'
set interfaces tunnel tun1 multicast 'disable'
commit
set interfaces tunnel tun1 remote 192.168.122.12
commit

Updated PR
I replace raw dhcpv6 global-parameters with leafNode.

I think it related T2651

ipsec policys, policy prefix-lists,

It seems a bug with your configuration. It is incorrect.

It used different scripts in 1.3 and 1.4.
show interfaces => run: ${vyos_op_scripts_dir}/show_interfaces.py --action=show-brief
show interfaces vrrp => run: ${vyatta_bindir}/vyatta-show-interfaces.pl --vrrp --action=show-brief

Giving the nature of the nesting of node.def files and their execution pattern this can not be fixed in 1.2.

Frr doesn't provide such option for ipv4, only for ipv6

I will try the latest

Yes, agree it works by show interfaces vrrp, but behavior in 1.2.x also displayed VIP by command show interfaces
I think this is a bug and need to fix it.

Temporary workaround for the VyOS 1.3-rc1 users:

I agree we should just check if it starts with a letter and doesn't include characters that an FQDN cannot have.

Backport is complete - It will "work" once the 1.3 kernel is updated to 5.10 series

A work-around for this was added in 1.2.6 and I verified it's working in 1.3.0-rc1

Just chiming back in to let you guys know I installed the latest vyos rolling release after all this time and the issue seems to have been fixed!

@Viacheslav, tested on VyOS 1.3-beta-202102270443. It works

Node "protocols" in 1.4 also doesn't have a description

This is not applicable to VyOS 1.4 because of T3364.

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.

Screenshot 2021-02-26 at 17.04.44.png (472×545 px, 45 KB)

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/

Search
Use Results
Edit Query
Hide Query

Mar 3 2021

Mar 2 2021

Mar 1 2021

Feb 28 2021

Feb 27 2021

Feb 26 2021