Still exists
https://github.com/vyos/vyos-build/blob/current/data/live-build-config/package-lists/vyos-utils.list.chroot
https://github.com/vyos/vyos-build/blob/equuleus/data/live-build-config/package-lists/vyos-utils.list.chroot

@Rhongomiant could you re-check it? Clear conntrack table between tests

Not reproduced
Reopen it with instance details if required

Should be fixed, needs testing.

PR 1.3 https://github.com/vyos/vyos-user-utils/pull/6

Duplicate
Available for 1.4

Fixed in https://vyos.dev/rVYOSONEX0c2384114e8abbd9c883a57729564c70c0a86eec

It's trying to find the template in /etc/, but it is located in /opt/vyatta/etc

vyos@r1:~$ generate vpn x509 key-pair testone
Can't open /etc/key-pair.template for reading, No such file or directory
140089191929024:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:69:fopen('/etc/key-pair.template','r')
140089191929024:error:2006D080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c:76:
vyos@r1:~$ cat /etc/key-pair.template
cat: /etc/key-pair.template: No such file or directory
vyos@r1:~$ 
vyos@r1:~$ sudo find / -name key-pair.template
/boot/rw/opt/vyatta/etc/key-pair.template
/opt/vyatta/etc/key-pair.template

Impossible to expand with the old firewal l backend
There is a warning that doesn't now you to do it.

vyos@r1#  set fire group address-group foo add 10.1.0.2-10.1.0.3
[edit]
vyos@r1#  set fire group address-group foo add 10.1.0.2-10.1.0.5
[edit]
vyos@r1# compare 
+firewall {
+    all-ping enable
+    broadcast-ping disable
+    config-trap disable
+    group {
+        address-group foo {
+            address 10.1.0.2-10.1.0.3
+            address 10.1.0.2-10.1.0.5
+        }
+    }
+    ipv6-receive-redirects disable
+    ipv6-src-route disable
+    ip-src-route disable
+    log-martians enable
+    receive-redirects disable
+    send-redirects enable
+    source-validation disable
+    syn-cookies enable
+    twa-hazards-protection disable
+}
[edit]
vyos@r1# commit
[ firewall group address-group foo ]
Address 10.1.0.2 exists in more than one configuration enrty

I think it is already implemented

set system option root-partition-auto-resize

@zsdc can we close it?

PR for 1.4 https://github.com/vyos/vyos-1x/pull/2184

Sep 21 09:31:58 home-r1 pppd[2827]: Unsupported protocol 'IPv6 Control Protocol' (0x8057) received

You can ignore it or configure ipv6

set interfaces pppoe pppoe2 ipv6

@banditos13 add please a PR to https://github.com/vyos/vyatta-wanloadbalance

VyOS 1.3-stable-202308240442

As we use nftables we won't use iptables modules anymore.
Create please a new one if you find something for nftables, I didn't find it for quick searching

We should avoid raw options for configurations.
We agree don’t implement it anymore.

The old backend doesn't allow it to do it for 1.3 Release.
Available for 1.4

The old backend doesn't allow it to do it for 1.3 Release.

@Sonicbx As I remember, HyperV is not affected.
But thanks anyway,

Could you provide your policy route?

Not sure that it is a good idea.
At least not for the LTS release.
I close it until we don't really need it and there are no use cases to do it.
Reopen it if required.

In T2505#157736, @Viacheslav wrote:

@Sonicbx Is it an actual bug?

In T1311#157738, @syncer wrote:

@Viacheslav will you backport this to 1.3 ?

we have a version updated , this case should be closed:

azureuser@vyos-support:~$ sudo /usr/sbin/waagent -version
WALinuxAgent-2.2.45 running on debian 10.12
Python: 3.7.3
Goal state agent: 2.2.45

PR https://github.com/vyos/vyos-1x/pull/2183

@Viacheslav will you backport this to 1.3 ?

@Sonicbx Is it an actual bug?

@n.fort Add please a PR for 1.3 or delete the 1.3 tag if it is not required

Can be resolved by route-map acting on community (for example <ASN>:888) and setting nexthop to 192.0.2.1 (optional tag 666) or for IPv6 set nexthop 0100:: along with a static route where 192.0.2.1/32 and 0100::/64 have null0 as nexthop.

It is not a task for 1.3 LTS releases.
For 1.4, there a new feature that was implemented in https://vyos.dev/T5228
get_config_dict and add argument with_defaults

Route leaking for dynamic protocols won't be implemented in VyOS 1.3 due to the old backend.
You can set a table in the route-map or use virtual-ethernet interfaces

PR https://github.com/vyos/vyos-1x/pull/2182

vyos@r1:~$ show pppoe-server interfaces 
interface:   connections:    state:
-----------------------------------
     eth0              1    active
vyos@r1:~$

@dmaasland @jestabro Can we close it?

The event handler was rewritten to python3 and doesn't use pipes.

@runar Can we close it?

vyos@r1# set interfaces bridge br0 member interface eth1 
Possible completions:
+  allowed-vlan Specify VLAN id which is allowed in this trunk interface
   cost         Bridge port cost
   isolated     Port is isolated (also known as Private-VLAN)
   native-vlan  Specify VLAN id which should natively be present on the link
   priority     Bridge port priority

There are not such options in FRR

r14(config-route-map)# set ip next-hop 
  A.B.C.D       IP address of next hop
  peer-address  Use peer address (for BGP only)
  unchanged     Don't modify existing Next hop address
r14(config-route-map)#

It must be next-hop

The best option is to use containers https://docs.vyos.io/en/latest/contributing/build-vyos.html#build-container
Close it as out of date.

PR for 1.3 https://github.com/vyos/vyos-1x/pull/2181

limitations of old backend

In T2229#142155, @Viacheslav wrote:

@skoenman Could you write some examples of configuration?

Ill see if i can get a example more or less of what one wants but it would be there were you asign the queue to the pppoe accoynt when authing..