Hi @francis the latest FRR version lacks support for Cisco authentication https://github.com/FRRouting/frr/blob/master/nhrpd/nhrp_peer.c#L1212

@c-po with this merge on FRR https://github.com/FRRouting/frr/pull/8153#event-4589485067 is migration possible? Possibly related to https://phabricator.vyos.net/T2326

Please, backport it to 1.3 rolling https://phabricator.vyos.net/rVYOSONEX4b646c1fb31a1a9f9c9d1658734d478fed5f19f1

Waiting for T3595 to clear up before I can test this on rolling release.

Why not use the mentioned method of sysctl`

@shaferstockton can you please post your entire generated openvpn.conf file?

@Viacheslav I seem to find a strange problem. If I run two containers of adguardhome and nginx, they seem to work normally in the same image. However, once I upgrade and boot the new system, these two containers will be abnormal and can only be restored manually (try to delete them first, then recommit them, and need to modify the program appropriately), This is a robustness problem, which needs to be confirmed. If there is a problem, it needs to be solved!

Note
ipsec-interface not deprecated. This option needed.

set vpn ipsec ipsec-interfaces interface 'eth1'

https://phabricator.vyos.net/T842

Here are some kernel features we need to consider:

1. Disable kexec. The user should never need to swap the kernel.
2. Restrict access to /proc/kallsyms for regular users, which makes sense since we're using a custom kernel.
3. Set hidepid to prevent regular users from seeing process IDs. Might be too intrusive.
4. Harden BPF JIT. Might interfere with XDP. Testing necessary.
5. Set kernel lockdown mode. Disables kexec and unprivileged BGP commands. Again, might interfere with XDP.

An easy start would be adding

export DEB_BUILD_MAINT_OPTIONS = hardening=+all
export DEB_CFLAGS_MAINT_APPEND  = -Wall -pedantic
export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed -Wl,-z,-defs

to debian/rules to harden our C programs (which is currently only VyShim and XDP). hardening=+all passes PIE and bindnow linker options to GCC.

just wanting to chime in here, I think I've been bitten by what appears to be a similar cause.

Turns out this was actually a very small change in the old framework - implemented also on 1.3 and backported to 1.2.8

thank you for the suggestion, I will work on this.

Also mentioned here: https://forum.vyos.io/t/roadwarrior-config-with-ikev2-and-different-user-groups/2457

Maybe a completion helper could work here, too?

When the following command "set system syslog file <filename> facility <keyword> level <keyword>" is applied, then the files are stored in the /var/log/user directory. These files can be deleted using the command "delete log file <text>"

This is possibly a problem on curl's end but funnily enough, there's a similar problem with the native implementation over T3563. Once that's solved, this bug will be rendered moot.

install-image now calls a routine that queries the size of the remote file and aborts if there isn't enough space to download the image.

commit-archive now uses Paramiko for SSH connections instead of curl and directly reads ~/.ssh/known_hosts if it exists.

New file transfer script parses the port field in the URL.

Also vpn ipsec site-to-site peer x tunnel x allow-nat-networks and vpn ipsec site-to-site peer x tunnel x allow-public-networks

We have had a lot of tickets about SNMP MIBS for BGP - most of them beeing for IPv6.

Re-Open - requires a strongswan update first - sorry

Thanks for testing!