User Details
- User Since
- Jun 8 2022, 9:47 AM (182 w, 1 d)
Fri, Nov 28
Fri, Nov 21
I have tested it in the lab with 1.4.3, but I cannot reproduce it. But during the implementation of OpenVPN for our customer, I met this issue. It happened when the config was too large (around 9K command lines) and the system was overloaded (old servers or GNS3).
Mon, Nov 17
Oct 17 2025
Sep 24 2025
Tested https://github.com/vyos/vyos-build/pull/1040. Now it works as expected.
Sep 9 2025
We migrated the NHRP protocol from OpenNHRP to FRR NHRPd in version 1.5.
Using /32 mask on the NHRP tunnel is the FRR limitation. It is mentioned in https://docs.vyos.io/en/latest/configuration/vpn/dmvpn.html
Also, we have a blueprint https://docs.vyos.io/en/latest/configexamples/dmvpn-dualhub-dualcloud.html
Added commands:
Aug 29 2025
The same issue using the VTI interface. Tested in 1.4.3
Aug 27 2025
Aug 25 2025
Aug 20 2025
Aug 13 2025
$ ansible-galaxy collection list | grep -E "vyos.vyos|ansible.netcommon" ansible.netcommon 6.1.3 vyos.vyos 6.0.0
- name: BackUp Cuideo router's config hosts: CUIDEO_ROUTERS
Aug 8 2025
Aug 1 2025
Jul 22 2025
Jul 15 2025
Jul 8 2025
Jun 18 2025
Jun 17 2025
Jun 12 2025
Jun 6 2025
Jun 5 2025
May 29 2025
May 28 2025
May 27 2025
May 23 2025
Tested. It works
May 22 2025
May 21 2025
May 20 2025
May 19 2025
May 17 2025
The file "new_config" did not contain a footer for proper migration.
May 13 2025
May 12 2025
May 5 2025
May 2 2025
I have tested the lab without IPSec for 3.5 hours - PIMD is alive
Apr 22 2025
Apr 11 2025
Mar 24 2025
If I use 1M in the command, everything works well for 3 hours
I reproduced this issue in my lab.
Network MAP
HOST1(debian)---VyOS1----(GREoverIPSEC)-----VyOS-2-- HOST2(debian)
Mar 21 2025
I built a lab and generated traffic as the customer did. However, I could not reproduce this issue. Maybe it is a problem with the packets generated by the switch (192.168.10.10).
There are periodic messages in the log file
Mar 7 2025
After deep investigation with @zsdc, we found that the issue can be here https://github.com/FRRouting/frr/blob/f3a7077df01176164c0bb5775ecb886cf233089e/ldpd/neighbor.c#L629
Mar 4 2025
Feb 28 2025
@sarthurdev I think, conntract should be transferred from input or forward to the global section or used in prerouting. Because now it looks like conntrack is used only in these rules, not for all traffic.
I did more tests. If I create any rule called conntrack (in input, forward, with different conditions), Conntrack affects all traffic that passes through or to the router.
