User Details
- User Since
- Jan 17 2019, 10:04 AM (302 w, 4 d)
Jun 6 2024
I don't know how to solve this problem. I suggest rejecting the problem.
Mar 15 2024
Mar 3 2024
Feb 25 2024
I'm using a workaround. I'm running a process in a script /config/scripts/vyos-postconfig-bootup.script:
Jul 29 2023
Jul 24 2023
Long commit time does not depend on the number of static routes, but on a size of the configuration or number of lines in the configuration. If a router has a large configuration (not necessarily static routes), committing any changes takes several minutes.
Jul 4 2023
Version: VyOS 1.4-rolling-202307040317
Jun 19 2023
Now the traffic limiter is broken.
Jun 13 2023
I opened an issue on github:
May 15 2023
Version 1.4-rolling-202305150317 does not have the problem.
May 5 2023
This can be implemented by multiple daemon instances in separate vrf's.
Mar 9 2023
QoS Policy Limiter now works correctly.
But the shaper classes for tagged traffic don't work.
Feb 9 2023
Jan 31 2023
Jan 27 2023
If I don't use advertise-all-vni I get an error
This command is only supported under EVPN VRF
Please use
advertise-all-vni
My full bgp config:
hmm, very strange.
Aug 19 2022
Successfully tested
Aug 16 2022
Jul 20 2022
Jul 18 2022
Duplicate T3871
Jul 14 2022
I propose a patch to fix this issue:
Similar problem in the latest rolling releases (vyos-1.4-rolling-202207111030). Traffic policy (limiter) not set in live configuration.
Jun 9 2022
This configuration commits without errors. Can the report be closed?
May 23 2022
Mar 21 2022
Mar 16 2022
Dec 23 2021
Forgot about the process "vyos-http-api-server". The process must be launched in the required vrf. Otherwise, we get an error: Otherwise, we get an error:
Dec 22 2021
Thank you, problem solved!
Dec 21 2021
I agree, when offloading is enabled, it is necessary to increase MTU for traffic policing.
# show traffic-policy limiter 1G { default { bandwidth 1gbit burst 188kb } }
Dec 20 2021
Similar problem:
Dec 6 2021
Dec 3 2021
Dec 1 2021
Nov 16 2021
{ "lldp": { "interface": [ { "eth0": { "via": "LLDP", "rid": "5", "age": "0 day, 00:00:16", "chassis": { "id": { "type": "mac", "value": "3c:61:04:5b:68:c0" }, "descr": "Juniper Networks, Inc. ex2200-c-12t-2g , version 11.4R7.5 Build date: 2013-03-01 09:18:42 UTC ", "capability": [ { "type": "Bridge", "enabled": true }, { "type": "Router", "enabled": true } ] }, "port": { "id": { "type": "local", "value": "521" }, "descr": "ge-0/0/9.0", "ttl": "120" }, "unknown-tlvs": { "unknown-tlv": { "oui": "00,90,69", "subtype": "1", "len": "12", "value": "47,50,30,32,31,33,33,36,30,36,39,36" } } } } ] } }
Aug 18 2021
Feb 12 2021
I have updated from an older version.
Version:
$show version
Feb 5 2021
Jan 9 2021
Jan 1 2021
Need 'nopmtudisc' option for tunnel interface. This is required for MPLS over gre or Ethernet over gre applications. This option is described in the iproute2 manuals (ip-tunnel).
Jun 11 2020
Hmm, sshd listens on port 2 by default.
SNMPD must listen to the socket on the loop in vrf default. This is necessary for the protocol agentx to work.
Jun 9 2020
Jun 8 2020
Can use systemd module file override?