- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Aug 28 2023
The old backend doesn't allow it to do it for 1.3 Release.
Available for 1.4
The old backend doesn't allow it to do it for 1.3 Release.
@Sonicbx As I remember, HyperV is not affected.
But thanks anyway,
Could you provide your policy route?
Not sure that it is a good idea.
At least not for the LTS release.
I close it until we don't really need it and there are no use cases to do it.
Reopen it if required.
@kroy What is wrong here?
set policy prefix-list foo rule 10 action 'permit' set policy prefix-list foo rule 10 prefix '10.0.0.0/8'
In T2505#157736, @Viacheslav wrote:@Sonicbx Is it an actual bug?
In T1311#157738, @syncer wrote:@Viacheslav will you backport this to 1.3 ?
we have a version updated , this case should be closed:
azureuser@vyos-support:~$ sudo /usr/sbin/waagent -version WALinuxAgent-2.2.45 running on debian 10.12 Python: 3.7.3 Goal state agent: 2.2.45
@Viacheslav will you backport this to 1.3 ?
@Sonicbx Is it an actual bug?
Implemented in previous versions, https://github.com/vyos/vyos-1x/blob/a5c5998a84917cc45f9fb3234607f53b27a109fc/interface-definitions/include/interface/mirror.xml.i#L1-L25
vyos@r1# set interfaces ethernet eth0 mirror Possible completions: egress Mirror the egress traffic of the interface to the destination interface ingress Mirror the ingress traffic of the interface to the destination interface
@n.fort Add please a PR for 1.3 or delete the 1.3 tag if it is not required
Can be resolved by route-map acting on community (for example <ASN>:888) and setting nexthop to 192.0.2.1 (optional tag 666) or for IPv6 set nexthop 0100:: along with a static route where 192.0.2.1/32 and 0100::/64 have null0 as nexthop.
It is not a task for 1.3 LTS releases.
For 1.4, there a new feature that was implemented in https://vyos.dev/T5228
get_config_dict and add argument with_defaults
Route leaking for dynamic protocols won't be implemented in VyOS 1.3 due to the old backend.
You can set a table in the route-map or use virtual-ethernet interfaces
PR https://github.com/vyos/vyos-1x/pull/2182
vyos@r1:~$ show pppoe-server interfaces
interface: connections: state:
-----------------------------------
eth0 1 active
vyos@r1:~$The cluster feature will be deprecated, as we use systemd we should avoid init.d scripts.
All logic should be rewritten to VRRP
@dmaasland @jestabro Can we close it?
The event handler was rewritten to python3 and doesn't use pipes.
@runar Can we close it?
vyos@r1# set interfaces bridge br0 member interface eth1 Possible completions: + allowed-vlan Specify VLAN id which is allowed in this trunk interface cost Bridge port cost isolated Port is isolated (also known as Private-VLAN) native-vlan Specify VLAN id which should natively be present on the link priority Bridge port priority
There are not such options in FRR
r14(config-route-map)# set ip next-hop A.B.C.D IP address of next hop peer-address Use peer address (for BGP only) unchanged Don't modify existing Next hop address r14(config-route-map)#
It must be next-hop
The best option is to use containers https://docs.vyos.io/en/latest/contributing/build-vyos.html#build-container
Close it as out of date.
Same issue. So building Equuleus isn't possible at all anymore? I don't quite understand that the message is "it will be fixed eventually" but at the same time it's tagged as "Wont fix".
PR for 1.3 https://github.com/vyos/vyos-1x/pull/2181
I don't see any errors in VyOS 1.3-stable-202308240442
vyos@r1# set firewall group network-group FW-OUT network '191.200.161.8/31' [edit] vyos@r1# set firewall group network-group FW-OUT network '191.200.161.8/32' [edit] vyos@r1# commit [edit] vyos@r1# delete firewall group [edit] vyos@r1# commit [edit] vyos@r1#
limitations of old backend
Fixed
[edit] vyos@r1# set policy route-map TEST rule 10 set metric -10 [edit] vyos@r1# commit [edit] vyos@r1# sudo vtysh -c "show run" Building configuration...
This task for the ldpd
https://vyos.dev/T4020
My bad, I don't know how I missed them!
The smoketest was in the same PR https://github.com/vyos/vyos-1x/pull/2162/files#diff-59a88cf4e56c56db9de173bbdeb31600f9733d8598570831364d2d368402af77
@Apachez thanks to you.
Let me check it.
Some tests on filesystem.squashfs from VyOS 1.4-rolling-202308280021.
In T5472#157591, @aderouineau wrote:Should a smoke test be added?
Better to have it
it will be fixed eventually
A note from https://forum.vyos.io/t/clear-logs-on-vyos/6878/10?u=viacheslav that there might be issues if removing directories from within / var/log/* doesnt occur to PR381 since that PR was specific about which files and directories to remove when it comes to / var/log. That is only files NOT directories were removed from / var/log.
Validated the change on version 1.4-rolling-202308250021.
https://github.com/vyos/vyos-1x/pull/2180 implement a workaround by changing the default values of stdout and stderr from PIPE to None.
Aug 27 2023
A baseline could be to look at the linux kernel config used by Alpine Linux for their RPI-builds:
@sdev I saw c-po revert the merge.
and I didn't expect that it will cost lots of time also.
It's better to revert it.
Currently, I will maintain kernel configs in my own branch.