@c-po I guess it should be v5.4.234
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
May 12 2023
May 11 2023
In T4362#148361, @masterit wrote:one issue.
the migration scripts don't take into account older load balancing configs.if the test > rule > type > ping isn't explicitly set then the rule defaults to the next hop address and ignores the rule entirely.
the default rule seems to be the next hop address for the interface.
set default check type ping https://github.com/vyos/vyos-1x/pull/1998
Veth is not ready to work together with netns
As Interface moves entirely to logical stack and with the next commit will be recreated and try to move to netns again. As it doesn't see veth interface which moved to another logical stack, it tryes to recreate this interface.
We should either fix it or revert the previous commit.
May 10 2023
Add kernel module https://github.com/vyos/vyos-build/pull/348
PR for L2TP https://github.com/vyos/vyos-1x/pull/1988
May 9 2023
Fixed with rewriting to systemd unit vyos-wan-load-balance.service
In T5213#148346, @joshua.hanley wrote:@Viacheslav Thanks for the prompt response. Not sure if the change will also cover L2TP as well. For example:
set vpn l2tp remote-access authentication radius accounting-interim-interval '60'
Sometimes it stuck for ~1.5 minutes after deleting.
vyos@r14# delete load-balancing [edit] vyos@r14# commit
PR https://github.com/vyos/vyos-1x/pull/1986
set service pppoe-server authentication mode 'radius' set service pppoe-server authentication radius accounting-interim-interval '60' set service pppoe-server authentication radius server 203.0.113.1 key '123' set service pppoe-server client-ip-pool name POOL-01 gateway-address '192.0.2.1' set service pppoe-server client-ip-pool name POOL-01 subnet '192.0.2.0/24' set service pppoe-server interface eth1
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.
We use FRR as the backend and it uses logical AND for match entries
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
May 7 2023
May 6 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
May 4 2023
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 2 2023
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'
Apr 29 2023
Apr 28 2023
Apr 27 2023
I think the only solution is to use network namespaces
https://docs.strongswan.org/docs/5.9/howtos/nameSpaces.html
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