- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
May 29 2023
May 28 2023
PR for VyOS 1.3 LTS branch https://github.com/vyos/vyos-1x/pull/2019
Yes, T4737 looks the same.
In T5243#149267, @Viacheslav wrote:Maybe the related bug described in T4737
Could you show a version of FRR?show version all | match frr
Maybe the related bug described in T4737
Could you show a version of FRR?
show version all | match frr
May 27 2023
In T970#149229, @olivier.hault wrote:How far are we in the testing of this important feature ?
May 26 2023
Added extension and example for test_vif_8021q_mtu_limits.
One fix added; I'm looking at an extension for the case of test_vif_8021q_mtu_limits, as mentioned in the comment in base_interfaces_test.py.
Let me cherry-pick these and commit all at one
I discovered that conntrack are enabled by default in two files:
Example implementation:
https://github.com/vyos/vyos-1x/compare/current...jestabro:cli-defined
How far are we in the testing of this important feature ?
All of the modem specific settings appear to be done through the web GUI of the modem.
May 25 2023
I could have sworn it took quite a while for the wlb.out to be populated when testing earlier on. However as I´ve built out the config a bit more I am now only able to reproduce it a few seconds after reboot - so your theory holds. Let's close out the bug report for now and I´ll reopen if something changes down the line.
Virtual-ethernet interfaces veth implemented in T4825
For veth in "netns" it should be a separate task.
I can't reproduce it VyOS 1.4-rolling-202305250317
set load-balancing wan flush-connections set load-balancing wan interface-health eth0 failure-count '3' set load-balancing wan interface-health eth0 nexthop '192.168.122.1' set load-balancing wan interface-health eth0 success-count '5' set load-balancing wan interface-health eth0 test 1 target '1.1.1.1' set load-balancing wan interface-health eth0 test 2 target '8.8.8.8' set load-balancing wan interface-health eth2 failure-count '10' set load-balancing wan interface-health eth2 nexthop 'dhcp' set load-balancing wan interface-health eth2 success-count '10' set load-balancing wan interface-health eth2 test 1 target '1.1.1.1' set load-balancing wan interface-health eth2 test 2 target '8.8.8.8' set load-balancing wan rule 1 failover set load-balancing wan rule 1 inbound-interface 'eth1.10' set load-balancing wan rule 1 interface eth0 weight '100' set load-balancing wan rule 1 interface eth2 weight '10'
May 24 2023
Thanks Viacheslav , for this clarification . Veths /Netns are strong powerful , using this technology we can use to join different hypervisor or bridge technology . leave some example namespaces /veth / bridging.
Sorry to write on a closed task, but without specifying a vrf (or some kind of identifier for that matter), how will the DHCP server decide which shared network to use since they have identical subnets configured?
PR https://github.com/vyos/vyos-1x/pull/2017
set interfaces virtual-ethernet veth10 peer-name 'veth100' set interfaces virtual-ethernet veth10 vif 50 address '10.0.50.0/31' set interfaces virtual-ethernet veth100 peer-name 'veth10' set interfaces virtual-ethernet veth100 vif 50 address '10.0.50.1/31'
Check:
vyos@r14:~$ show interfaces virtual-ethernet Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down Interface IP Address S/L Description --------- ---------- --- ----------- veth10 - u/u veth10.50 10.0.50.0/31 u/u veth100 - u/u veth100.50 10.0.50.1/31 u/u vyos@r14:~$
Pings:
vyos@r14:~$ ping 10.0.50.1 source-address 10.0.50.0 PING 10.0.50.1 (10.0.50.1) from 10.0.50.0 : 56(84) bytes of data. 64 bytes from 10.0.50.1: icmp_seq=1 ttl=64 time=0.132 ms 64 bytes from 10.0.50.1: icmp_seq=2 ttl=64 time=0.085 ms 64 bytes from 10.0.50.1: icmp_seq=3 ttl=64 time=0.087 ms ^C --- 10.0.50.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2064ms rtt min/avg/max/mdev = 0.085/0.101/0.132/0.021 ms vyos@r14:~$
It is a part of T3829
We should find a solution to check if the interface "neighbor" is in a separate netns. For now, we don't do this check.
veth pair should be in the local router only, VRF or NETNS and it won't work between 2 separate routers or 2 VMs.
May 23 2023
So after a small test, I've come to the following:
I started working on a jool nat64 implementation at https://github.com/vyos/vyos-1x/pull/1993 for anyone that would like to try it out. Not everything is implemented yet, but I have been running this for the past few weeks with no issues. Any comments or feedback on the UX would be appreciated
danhusan@vyos-1:~$ cat /var/run/load-balance/wlb.out cat: /var/run/load-balance/wlb.out: No such file or directory
@danhusan Could you check if the file /var/run/load-balance/wlb.out exists?
https://github.com/vyos/vyatta-wanloadbalance/blob/5a3ab6c426928644dc9ad9a70296263781523919/templates-op/show/wan-load-balance/node.def#L2C15-L5
PR https://github.com/vyos/vyos-1x/pull/2015
vyos@r14# run show reverse-proxy Proxy name Role Status Req rate Resp time Last change ------------ -------- -------- ---------- ----------- ------------- http FRONTEND OPEN 0 https FRONTEND OPEN 16 stats FRONTEND OPEN 0 bk-01 BACKEND UP 1 ms 1h34m45s default-bk BACKEND UP 0 ms 1h34m45s bk-01 serv-01 UP 1 ms 1h34m45s bk-01 serv-02 DOWN 0 ms 1h34m44s default-bk serv-03 no check 0 ms 1h34m45s [edit] vyos@r14#