Does it possible to cherry-pick to 1.3? Because in 1.3 rollings we have the same bug.

PR https://github.com/vyos/vyatta-wanloadbalance/pull/8

Successfully tested on 1.3-rolling-202012230217

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

successfully tested on the self-build image from crux branch and the latest rolling image

Thanks, @c-po , works as expected.

vyos@vyos:~$ show  lldp neighbors 
Capability Codes: R - Router, B - Bridge, W - Wlan r - Repeater, S - Station
                  D - Docsis, T - Telephone, O - Other

It seems related to this patch https://github.com/vyos/vyos-1x/commit/b39d623170377b2e99fd7e88b627afea71e4d00c#diff-e4557e4a7b41f0e9328ac0e7d7c0305416f0f1e42d46af27c2135ca976434fce
Appears only if you have 2 or more lldp neighbors.

Ok, with cisco device and added vif 1 I can reproduce this issue

vyos@vyos# run show lldp neighbors 
Traceback (most recent call last):
  File "/usr/libexec/vyos/op_mode/lldp_op.py", line 121, in <module>
    config_text = tmpl.render(parse_data(neighbors))
  File "/usr/libexec/vyos/op_mode/lldp_op.py", line 50, in parse_data
    for local_if, values in data.items():
AttributeError: 'list' object has no attribute 'items'

I still can't reproduce this issue.

vyos@vyos:~$ show configuration commands | match lldp
set service lldp interface eth1
set service lldp legacy-protocols cdp
set service lldp management-address '192.168.255.31'
set service lldp snmp enable
vyos@vyos:~$ show lldp neighbors 
Capability Codes: R - Router, B - Bridge, W - Wlan r - Repeater, S - Station
                  D - Docsis, T - Telephone, O - Other

@thadrumr please provide your lldp configuration. show configuration commands | match lldp
I can't reproduce this issue in lab with the latest rolling. Provide please detailed reproducing steps, also will be helpful to get an output

sudo lldpcli show neighbors

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

PR with changed types in docs https://github.com/vyos/vyos-documentation/pull/380
ESP transport mode works properly on Cisco Router and VyOS routers together.

DMVPN Spokes work properly behind a NAT if we use transport mode instead of tunnel. e.g.

set vpn ipsec esp-group ESP-HUB mode transport

So I think we need to add this info to docs.vyos.io and close this Feature Request

Following this issue request https://sourceforge.net/p/opennhrp/support-requests/3/ we need to use transport mode instead of a tunnel. Was tested on AWS node and it looks working even with selector remote_ts = dynamic[gre]

Let's run pimd only if IGMP or PIM configured.
https://github.com/vyos/vyos-1x/pull/618
https://github.com/vyos/vyos-build/pull/134

How about these changes https://github.com/vyos/vyos-1x/blob/current/src/op_mode/powerctrl.py#L37

diff --git a/src/op_mode/powerctrl.py b/src/op_mode/powerctrl.py
index 69af427e..c000d7d0 100755
--- a/src/op_mode/powerctrl.py
+++ b/src/op_mode/powerctrl.py
@@ -34,7 +34,11 @@ def utc2local(datetime):
 def parse_time(s):
     try:
         if re.match(r'^\d{1,2}$', s):
-            return datetime.strptime(s, "%M").time()
+            if (int(s) > 59):
+                s = str(int(s)//60) + ":" + str(int(s)%60)
+                return datetime.strptime(s, "%H:%M").time()
+            else:
+                return datetime.strptime(s, "%M").time()
         else:
             return datetime.strptime(s, "%H:%M").time()
     except ValueError:

It looks like need to do some calculation

vyos@vyos:~$ show version | match Version
Version:          VyOS 1.3-rolling-202011130217
vyos@vyos:~$ show date 
Fri 13 Nov 2020 07:18:44 AM UTC
vyos@vyos:~$ reboot in 60
Invalid time "60". The valid format is HH:MM
vyos@vyos:~$ reboot in 59
Reboot is scheduled 2020-11-13 08:18:04
vyos@vyos:~$ reboot in 61
Invalid time "61". The valid format is HH:MM

Tested on 1.3-rolling-202011130217, all works as expected.
Thanks to @ernstjo

PR https://github.com/vyos/vyos-1x/pull/590
I hope it will be helpful for many people from France. As for me it better solution then glue stickers with QWERTY keys =)

Ok, let's review the situation when you install VyOS on bare metal and you have an only AZERTY keyboard. You press key A but in console, you see Q, you press Z on the console you see W.
Debian way, install console-data from https://packages.debian.org/sid/console-data and run sudo loadkeys fr

To add the possibility to switch from default QWERTY keyboard type to AZERTY.

@Viacheslav if we set acct-port=0 it should to disable accounting.

[radius]
server=x.x.x.x,secret,auth-port=1812,acct-port=0

It looks like this works, but when we don't have any connected user, it listed the current directory file

vyos@RTR1:~$ touch 1.txt
vyos@RTR1:~$ reset vpn remote-access user <tab>
Possible completions:
  1.txt         Terminate specified user's current remote access VPN session(s)

After a user connected, all works properly

vyos@RTR1:~$ reset vpn remote-access user <tab>
Possible completions:
  test1         Terminate specified user's current remote access VPN session(s)

PR https://github.com/vyos/vyos-build/pull/128

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

Yes, both clients configured as DHCP clients.
Client 1 - eth0 - 50:00:00:06:00:00
Client 2 - eth0 - 50:00:00:07:00:00

PR for CRUX https://github.com/vyos/vyos-1x/pull/568

PR with increasing validator values https://github.com/vyos/vyos-1x/pull/566

@c-po , it looks like the wrong CLI definition, we can increase the limit in XML.

Note: New xl2tpd package does not work with the followings params in options.xl2tpd

crtscts
lock

PR for CRUX https://github.com/vyos/vyatta-cfg-system/pull/130

PR https://github.com/vyos/vyos-build/pull/127
Also will be good cherrypick this to crux.

Works properly, tested on 1.3-rolling-202009290117.
One remark, jitter will be applied for all accounting packet except the first packet. The first packet is a flag that the session is started.

Works properly on VyOS 1.3-rolling-202009290117.
When command set service pppoe-server authentication radius preallocate-vif committed, pppoe-server send the next attributes in Access-Request packet on a client authorization:

NAS-Port = 0
NAS-Port-Id = "ppp0"
NAS-Port-Type = Virtual

Successfully tested on 1.3-rolling-202009290117

set service pppoe-server authentication radius called-sid-format 'ifname:mac'

Radius recived Called-Station-Id = "eth1:50:00:00:05:00:01"

set service pppoe-server authentication radius called-sid-format 'ifname'

Radius recived Called-Station-Id = "eth1"
By default radius recive Called-Station-Id = "50:00:00:05:00:01"

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

Marked as resolved

Thanks, let's merge it only after 1.2.6 release

Can we add this implementation for crux in the old style?
https://github.com/DmitriyEshenko/vyatta-cfg-system/commit/0adc41a62b6d532da7c4b47cb5da920d1ed39664

@c-po , the same behavior even with kernel 5.8.8

vyos@R1:~$ uname -a
Linux R1 5.8.8-amd64-vyos #1 SMP Thu Sep 10 08:58:42 UTC 2020 x86_64 GNU/Linux

How about migrating this iptables rule from mangle to filter?

New PR for fixing it https://github.com/vyos/vyos-1x/pull/541