Query: All Stories

	Include stories about projects I am a member of.

Thanks for reporting this! At least we know people actually use the signatures. ;)

*-update flavors are no longer used in LTS releases — there is no need to, and it's much simpler for users when they can just use openstack or whatever ISO flavor for upgrade.

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)

Im also getting a 404 for the commit link posted at 2025-03-23 11:50.

Thanks @Viacheslav, but no need to patch anything in FRR. The commit has made it into the FRR 10.3 release, it will be better to just wait until you guys bump to the latest FRR release. I can rebase and submit a PR at that point fairly quickly.

You do not need task on phorge for docs

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

Dependent FRR commit has made it to the 10.3 release. Waiting for VyOS to update and then I will create a PR.

Both dependent FRR commits have made it to the 10.3 release. Waiting for VyOS to update and then I will create a PR.

Well, it could go something like this:

Which option do you propose for CLI to configure it?

At the moment, it's not configurable in the CLI or if it is, it's not documented or it's buried somewhere that my question marking through the whole thing hasn't revealed it.

@woodsb02 Would you like to create a PR fix?

How do you see it in the CLI?
In my opinion each option should be configurable from the proper CLI if such option does not exist, it should be added.

This below specific configuration was allowed in 1.3.8 but not in 1.4.1 anymore, if defined it needs to be migrated in this format: "set system syslog host 10.29.113.213 port '9001'"

for me on VyOS 1.5-rolling-202503030030 it works if you first remove the ospf configuration, then delete the protocols:

I'm just sharing my thoughts here: Could it have something to do with the fact that the IPv4 prefix is a /32? why does it have to be a /32 anyway (when NHRP is configured)? On Cisco IOS there is no such restrictions.

I'm sorry, all it took was to disable PFS. PFS prevented future SA's from happening due to a policy mismatch.

This seems to be implemented:

for the record: I've successfuly imported private key after converting it from pkcs#1 to pkcs#8

All Stories
Use Results
Edit Query
Hide Query

Mar 24 2025

Mar 23 2025

Mar 22 2025

Mar 21 2025

Mar 20 2025

Mar 19 2025