PR for 1.3.4 https://github.com/vyos/vyatta-cfg-quagga/pull/101
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Aug 30 2023
Works fine VyOS 1.3-stable-202308240442
vyos@r1# run generate wireguard client-config c1 interface wg0 server 203.0.113.1 address 10.0.0.2/32
@dsummers Could you re-check? Should be fixed in https://github.com/PowerDNS/pdns/pull/12203
We didn't get the requested information.
Reopen it if it is required with steps to reproduce and some output.
Implemented, checked in VyOS 1.3-stable-202308240442
vyos@r1# set policy local-route Possible completions: > local-route IPv4 policy route of local traffic > local-route6 IPv6 policy route of local traffic
@Rhongomiant could you re-check it? Clear conntrack table between tests
Not reproduced
Reopen it with instance details if required
Should be fixed, needs testing.
I tried on VyOS 1.4-rolling-202308300021 .
PR1 didnt seem to have any affect on this night build:
Aug 29 2023
Duplicate
Available for 1.4
It's trying to find the template in /etc/, but it is located in /opt/vyatta/etc
vyos@r1:~$ generate vpn x509 key-pair testone
Can't open /etc/key-pair.template for reading, No such file or directory
140089191929024:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:69:fopen('/etc/key-pair.template','r')
140089191929024:error:2006D080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c:76:
vyos@r1:~$ cat /etc/key-pair.template
cat: /etc/key-pair.template: No such file or directory
vyos@r1:~$
vyos@r1:~$ sudo find / -name key-pair.template
/boot/rw/opt/vyatta/etc/key-pair.template
/opt/vyatta/etc/key-pair.templateImpossible to expand with the old firewal l backend
There is a warning that doesn't now you to do it.
vyos@r1# set fire group address-group foo add 10.1.0.2-10.1.0.3
[edit]
vyos@r1# set fire group address-group foo add 10.1.0.2-10.1.0.5
[edit]
vyos@r1# compare
+firewall {
+ all-ping enable
+ broadcast-ping disable
+ config-trap disable
+ group {
+ address-group foo {
+ address 10.1.0.2-10.1.0.3
+ address 10.1.0.2-10.1.0.5
+ }
+ }
+ ipv6-receive-redirects disable
+ ipv6-src-route disable
+ ip-src-route disable
+ log-martians enable
+ receive-redirects disable
+ send-redirects enable
+ source-validation disable
+ syn-cookies enable
+ twa-hazards-protection disable
+}
[edit]
vyos@r1# commit
[ firewall group address-group foo ]
Address 10.1.0.2 exists in more than one configuration enrtyAlready present VyOS 1.3-stable-202308240442
release dhcp interface eth1
Looks like fixed VyOS 1.3-stable-202308240442
vyos@r1# run show conf com | match "traf|bon" set interfaces bonding bond0 member interface 'eth1' set interfaces bonding bond0 traffic-policy in 'BAND-IN' set traffic-policy limiter BAND-IN class 1601 bandwidth '100mbit' set traffic-policy limiter BAND-IN class 1601 match 16xx vif '1601' set traffic-policy limiter BAND-IN default bandwidth '10gbit' set traffic-policy shaper BAND-OUT class 1602 bandwidth '100mbit' set traffic-policy shaper BAND-OUT class 1602 match 16xx vif '1602' set traffic-policy shaper BAND-OUT default bandwidth '10gbit' [edit] vyos@r1# run show ver
I think it is already implemented
set system option root-partition-auto-resize
@zsdc can we close it?
We agree not to use RAW options for service configuration anymore.
PR for 1.4 https://github.com/vyos/vyos-1x/pull/2184
Fixed VyOS 1.3-stable-202308240442
vyos@r1# show interfaces ethernet eth2
description LAN
hw-id 52:54:00:6c:c7:ac
vrf foo
[edit]
vyos@r1# compare
[edit interfaces bridge br11]
+member {
+ interface eth2 {
+ }
+}
[edit]
vyos@r1#
[edit]
vyos@r1# commit
[ interfaces bridge br11 ]
Can not add interface "eth2" to bridge, it has a VRF assigned!Sep 21 09:31:58 home-r1 pppd[2827]: Unsupported protocol 'IPv6 Control Protocol' (0x8057) received
You can ignore it or configure ipv6
set interfaces pppoe pppoe2 ipv6
@banditos13 add please a PR to https://github.com/vyos/vyatta-wanloadbalance
VyOS 1.3-stable-202308240442
Works, tested with this steps https://docs.vyos.io/en/latest/installation/virtual/docker.html
root@r14:/home/vyos# podman ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES d49f99e058d7 localhost/vyos:1.3-stable-202308240442 /sbin/init About a minute ago Up About a minute ago vyos root@r14:/home/vyos# root@r14:/home/vyos# root@r14:/home/vyos# sudo podman exec -ti vyos su - vyos vyos@vyos:~$ vyos@vyos:~$ vyos@vyos:~$ show version
As we use nftables we won't use iptables modules anymore.
Create please a new one if you find something for nftables, I didn't find it for quick searching
We should avoid raw options for configurations.
We agree don’t implement it anymore.
Aug 28 2023
PR created: https://github.com/vyos/vyos-live-build/pull/1
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 ?