In T5186#148294, @rh7819 wrote:this is cause by
tcindex classifier is removed by upstream kernel, so
08:04:48 DEBUG - filter add dev eth1 parent 11: protocol ip prio 1 handle 128 tcindex classid 11:a
fails.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed Search
May 9 2023
May 9 2023
Viacheslav changed the status of T5214: PPPoE-server incorrect warning if a named pool is defined from Open to In progress.
Viacheslav renamed T5213: Accel-ppp sending accounting interim updates acct-interim-interval option from Sending accounting interim updates to Accel-ppp sending accounting interim updates acct-interim-interval option.
Viacheslav changed the status of T5213: Accel-ppp sending accounting interim updates acct-interim-interval option from Open to In progress.
Viacheslav added a comment to T5211: route-map allows both IPv4 and IPv6 in one rule which never match.
We use FRR as the backend and it uses logical AND for match entries
May 8 2023
May 8 2023
PR https://github.com/vyos/vyos-1x/pull/1984
set high-availability disable set high-availability vrrp group GRP01 address 192.0.2.47/32 set high-availability vrrp group GRP01 interface 'eth1' set high-availability vrrp group GRP01 vrid '10'
It doesn't like protocol tcp
vyos@r14# sudo tc filter replace dev eth1 parent 1: protocol all u32 match ip protocol tcp 0xff action police rate 300000000 burst 15k flowid 1:a Illegal "match" [edit] vyos@r14#
But it works with protocol 6
vyos@r14# sudo tc filter replace dev eth1 parent 1: protocol all u32 match ip protocol 6 0xff action police rate 300000000 burst 15k flowid 1:a [edit] vyos@r14#
And next fail:
ardware UUID: 4d6f4d29-1ae8-446f-8d2b-3decd9da64c7
Viacheslav updated the task description for T5209: dhclient load-balancing exit hook 04-dhcp-wanlb returned non-zero exit status.
Viacheslav updated the task description for T5202: After removal load-balancing a pid remained which used in dhclient-exit-hooks.
Viacheslav closed T5203: load-balancing wan add systemd unit instead of old vyatta-wanloadbalance.init, a subtask of T4470: Rewrite load-balancing wan to XML/Python, as Resolved.
May 7 2023
May 7 2023
Viacheslav changed the subtype of T5053: Vyatta-cfg Post-Removal Hook Tries to Disable Deleted Service from "Task" to "Bug".
May 6 2023
May 6 2023
May 5 2023
May 5 2023
It should work for 1.4
set policy route foo interface eth1v1
Load-balancing op-mode output generated by https://github.com/vyos/vyatta-wanloadbalance/blob/current/src/lboutput.cc
Viacheslav renamed T5203: load-balancing wan add systemd unit instead of old vyatta-wanloadbalance.init from Add systemd unit instead of old vyatta-wanloadbalance.init to load-balancing wan add systemd unit instead of old vyatta-wanloadbalance.init.
Viacheslav changed the status of T5203: load-balancing wan add systemd unit instead of old vyatta-wanloadbalance.init, a subtask of T4470: Rewrite load-balancing wan to XML/Python, from Open to In progress.
Viacheslav changed the status of T5203: load-balancing wan add systemd unit instead of old vyatta-wanloadbalance.init from Open to In progress.
Viacheslav changed the status of T5171: Use XML for conf-mode "load-balancing wan" instead of legacy templates, a subtask of T4470: Rewrite load-balancing wan to XML/Python, from In progress to Needs testing.
Viacheslav changed the status of T5171: Use XML for conf-mode "load-balancing wan" instead of legacy templates from In progress to Needs testing.
May 4 2023
May 4 2023
Viacheslav added projects to T2934: proxy-arp-pvlan on VRRP interface: VyOS 1.4 Sagitta, VyOS 1.3 Equuleus (1.3.3).
Works in my test
set protocols static table 200 route 192.0.2.35/32 dhcp-interface 'eth4'
Show ip route
vyos@vyos2:~$ vtysh -c "show ip route table 200"
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
T - Table, v - VNC, V - VNC-Direct, A - Babel, F - PBR,
f - OpenFabric,
> - selected route, * - FIB route, q - queued, r - rejected, b - backup
t - trapped, o - offload failureMay 3 2023
May 3 2023
May 2 2023
May 2 2023
Viacheslav added a comment to T1797: Implement DPDK Fast-Path using FRR's Alternate Forwarding Planes and VPP.
VPP 23.02 failing on Debian 12 (bookworm) https://jira.fd.io/browse/VPP-2075
PR https://github.com/vyos/vyos-1x/pull/1975
set policy route-map foo rule 10 action 'permit' set policy route-map foo rule 10 match protocol 'connected' set policy route-map foo rule 20 action 'permit' set policy route-map foo rule 20 match protocol 'bgp'
Viacheslav changed the status of T5163: Policy route-map add match source-protocol from Open to In progress.
Apr 29 2023
Apr 29 2023
Viacheslav moved T4971: Radius attribute "Framed-Pool" for PPPoE from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.3) board.
Viacheslav added a project to T4971: Radius attribute "Framed-Pool" for PPPoE: VyOS 1.3 Equuleus (1.3.3).
Apr 28 2023
Apr 28 2023
Viacheslav added a comment to T5171: Use XML for conf-mode "load-balancing wan" instead of legacy templates.
Apr 27 2023
Apr 27 2023
Viacheslav edited projects for T5188: Update Intel igc driver for improved 2.5 GbE support, added: VyOS 1.3 Equuleus (1.3.3); removed VyOS 1.3 Equuleus.
Viacheslav reopened T5181: Wrong dependencies or priorities for zebra vni vrf interfaces and bgpd as "Needs testing".
Viacheslav edited projects for T5186: QoS test cannot pass for 1.3, added: VyOS 1.3 Equuleus (1.3.3); removed VyOS 1.4 Sagitta.
I think the only solution is to use network namespaces
https://docs.strongswan.org/docs/5.9/howtos/nameSpaces.html
Apr 26 2023
Apr 26 2023
Do you have users/passwords with specsymbols or not utf-8 or some ascii symbols?
Could you provide l2tp configuration? show conf com | match l2tp
I cannot reproduce it
vyos@r14:~$ vyos@r14:~$ show l2tp-server sessions ifname | username | ip | ip6 | ip6-dp | calling-sid | rate-limit | state | uptime | rx-bytes | tx-bytes --------+----------+--------------+-----+--------+---------------+------------+--------+----------+----------+---------- l2tp0 | alice | 100.64.203.0 | | | 192.168.122.1 | | active | 00:00:10 | 246 B | 208 B vyos@r14:~$ vyos@r14:~$ vyos@r14:~$ show version Version: VyOS 1.4-rolling-202304261027 Release train: current
@joshua.hanley Could you provide the output of the next command?
sudo accel-cmd -p 2004 show sessions
Apr 25 2023
Apr 25 2023
Viacheslav added a comment to T5181: Wrong dependencies or priorities for zebra vni vrf interfaces and bgpd.
Incorrect modify modify_section: starting search for '^vrf protocols' until '^exit-vrf'
vyos@r14# delete vrf name red vni
[edit]
vyos@r14# commit
[ vrf name red vni 3000 ]
{'name': {'protocols': {'bgp': {'address_family': {'ipv4_unicast': {'redistribute': {'connected': {}}},
'l2vpn_evpn': {'advertise': {'ipv4': {'unicast': {}}}}},
'system_as': '65001'}},
'table': '3000'}}
load_configuration: Configuration loaded from FRR daemon zebra
load_configuration: loaded 0 !
load_configuration: loaded 1 frr version 8.5
load_configuration: loaded 2 frr defaults traditional
load_configuration: loaded 3 hostname debian
load_configuration: loaded 4 log syslog
load_configuration: loaded 5 log facility local7
load_configuration: loaded 6 hostname r14
load_configuration: loaded 7 service integrated-vtysh-config
load_configuration: loaded 8 !
load_configuration: loaded 9 vrf red
load_configuration: loaded 10 vni 3000
load_configuration: loaded 11 exit-vrf
load_configuration: loaded 12 !
load_configuration: loaded 13 end
modify_section: starting search for '^vrf protocols' until '^exit-vrf'Viacheslav updated the task description for T5181: Wrong dependencies or priorities for zebra vni vrf interfaces and bgpd.
Viacheslav renamed T5181: Wrong dependencies or priorities for zebra vni vrf interfaces and bgpd from Wrong dependencies or priorities for zebra vni vrf and bgpd to Wrong dependencies or priorities for zebra vni vrf interfaces and bgpd.
Apr 24 2023
Apr 24 2023
@Harliff Could you check it? Available in the latest rolling release
vyos@r14# set protocols failover route 192.0.2.55/32 next-hop 192.168.122.1 check policy Possible completions: all-available All targets must be alive any-available Any target must be alive (default)
Apr 22 2023
Apr 22 2023
Apr 21 2023
Apr 21 2023
PR https://github.com/vyos/vyos-1x/pull/1966
set protocols failover route 192.0.2.55/32 next-hop 192.168.122.1 check policy 'any-available' set protocols failover route 192.0.2.55/32 next-hop 192.168.122.1 check target '192.168.122.1' set protocols failover route 192.0.2.55/32 next-hop 192.168.122.1 check target '192.168.122.11' set protocols failover route 192.0.2.55/32 next-hop 192.168.122.1 check timeout '3' set protocols failover route 192.0.2.55/32 next-hop 192.168.122.1 interface 'eth0'
Viacheslav added a comment to T5171: Use XML for conf-mode "load-balancing wan" instead of legacy templates.
Don't have any idea how to integrate this logic to XML https://github.com/vyos/vyatta-wanloadbalance/blob/973421035568810e2583187c48d14054970b9806/templates/load-balancing/wan/node.def#L2-L5
Apr 20 2023
Apr 20 2023
Viacheslav renamed T5171: Use XML for conf-mode "load-balancing wan" instead of legacy templates from Use XML for conf-mode "load-balancing wan" instead of legasy templates to Use XML for conf-mode "load-balancing wan" instead of legacy templates.
Viacheslav renamed T5171: Use XML for conf-mode "load-balancing wan" instead of legacy templates from Use XML for conf-mode "load-balancing wan" instead of templates to Use XML for conf-mode "load-balancing wan" instead of legasy templates.
Viacheslav changed the status of T5171: Use XML for conf-mode "load-balancing wan" instead of legacy templates, a subtask of T4470: Rewrite load-balancing wan to XML/Python, from Open to In progress.
Viacheslav changed the status of T5171: Use XML for conf-mode "load-balancing wan" instead of legacy templates from Open to In progress.
Apr 19 2023
Apr 19 2023
Viacheslav changed the subtype of T5166: Remove local minisign package from build repo for 1.4 from "Task" to "Feature Request".
Apr 18 2023
Apr 18 2023
In T1237#147125, @Harliff wrote:Sorry, missed some messages.
In T1237#146586, @Viacheslav wrote:We have targets-checks 203.0.113.1, 192.0.2.1, and if any of these targets are unreachable, we delete this route.
Is it correct?It is not correct. I think it would be better to remove the route if ALL of corresponding targets are unreachable.
A target may become unreachable due to a problem of its own rather than an uplink failure. This is the reason why I asked to add multiple targets per uplink.
Apr 17 2023
Apr 17 2023
Apr 16 2023
Apr 16 2023
Apr 14 2023
Apr 14 2023
Viacheslav added a comment to T5156: vyos unable to tell that it updated dynamic DNS on cloudflare correctly.
Provide your configuration
It is difficult to say without it
It uses other names in the newest versions, not cni-xxx
Apr 13 2023
Apr 13 2023