This is now resolved for us.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed Search
Nov 6 2021
Nov 6 2021
Viacheslav changed the subtype of T3971: Ability to build ISO images for XCP-NG hypervisor from "Bug" to "Feature Request".
Nov 5 2021
Nov 5 2021
c-po moved T3964: SSTP: local-user static-ip CLI node accepts invalid IPv4 addresses from Open to Finished on the VyOS 1.4 Sagitta board.
c-po moved T3972: Removing vif-c interface raises KeyError from Open to Finished on the VyOS 1.4 Sagitta board.
Reported by @shyrwall
Viacheslav moved T3971: Ability to build ISO images for XCP-NG hypervisor from Need Triage to Finished on the VyOS 1.3 Equuleus board.
PR for crux https://github.com/vyos/vyos-build/pull/198
vyos@vyos:~$ show version all | match xe-g ii xe-guest-utilities 7.16.0-2 amd64 Virtual Machine Monitoring Scripts vyos@vyos:~$
Viacheslav changed the status of T3971: Ability to build ISO images for XCP-NG hypervisor from In progress to Needs testing.
Viacheslav added a project to T3971: Ability to build ISO images for XCP-NG hypervisor: VyOS 1.2 Crux (VyOS 1.2.9).
Great. As soon as there is an example available I think I can also help provide additional commands.
@adestis there were discussions on this in the past week --- I will be helping @dmbaturin with the task
Viacheslav changed the status of T3971: Ability to build ISO images for XCP-NG hypervisor from Open to In progress.
Who can help with the architecture of this webservice?
Alternatively, can you provide the contact information of NET-SNMP's PRIST? I can also contact him for vulnerability disclosure.
Yes, I also believe that this crash exists in all current versions of NET-SNMP. And I also found this vulnerability in the source code of the latest version of Net-SNMP( version 5.9.1), and I compiled and installed net-SNMP on Ubuntu to duplicate this vulnerability. But I can't find the contact information of NET-SNMP. It seems that only the cooperative manufacturer can contact him. Can you negotiate with them to disclose this vulnerability?
Nov 4 2021
Nov 4 2021
c-po closed T3662: Container configuration upgrade destroys system, a subtask of T2216: Containerized third-party applications for VyOS, as Resolved.
Nov 3 2021
Nov 3 2021
c-po updated the task description for T3964: SSTP: local-user static-ip CLI node accepts invalid IPv4 addresses.
Viacheslav changed the status of T2281: DHCP and Static IPs on Same Interface from In progress to Needs testing.
I also have some of those APU4 devices and they work actually pretty good. The reasons for those "low" defaults are actually not from VyOS but from the Linux Kernel itself.
Same issue for me, i use the last RC 1.3 release (manualy builded yesterday).
Will you correct this bug until the LTS release ?
Im not sure its possible to delete the "le" part from vtysh cli? I tried running no ipv6 prefix-list PUBLIC-IPV6 seq 10 permit 2001:db8::/32 le 64 from vtysh, but it never removed le part.
Viacheslav added a comment to T3932: L2TP Configuration with WAN interface DHCP assigned IP address.
@sajiby3k you can use 0.0.0.0
set vpn l2tp remote-access outside-address '0.0.0.0'
Nov 2 2021
Nov 2 2021
@zoenan7 Sorry for the late reply! Yes, I got your email and could reproduce the crash using your PoC.
Nov 1 2021
Nov 1 2021
c-po removed a project from T2683: no dual stack in system static-host-mapping host-name : Ready for Crux (1.2.x).
c-po moved T2683: no dual stack in system static-host-mapping host-name from Backport Candidates to Backlog on the VyOS 1.3 Equuleus board.
c-po moved T2683: no dual stack in system static-host-mapping host-name from Need Triage to Backport Candidates on the VyOS 1.3 Equuleus board.
c-po moved T3795: WWAN: issues with non connected interface / no signal from Need Triage to Backlog on the VyOS 1.3 Equuleus board.
c-po added a comment to T2892: Remove command: "set firewall options interface <interface> disable".
We keep this in 1.3 as the CLI is fixed - it was removed in the 1.4 development cycle with T3090
c-po moved T3724: Allow setting host-name in l2tp section of accel-ppp from Need Triage to In Progress on the VyOS 1.3 Equuleus board.
c-po moved T2281: DHCP and Static IPs on Same Interface from Open to Backlog on the VyOS 1.4 Sagitta board.
Viacheslav moved T2683: no dual stack in system static-host-mapping host-name from Open to Finished on the VyOS 1.4 Sagitta board.
PR for 1.4 https://github.com/vyos/vyos-1x/pull/1058
Viacheslav changed the status of T2281: DHCP and Static IPs on Same Interface from Open to In progress.
For 1.4 it is impossible to set both dhcp + static in one commit.
set interfaces ethernet eth2 address dhcp set interfaces ethernet eth2 address 192.0.2.4/24
Oct 31 2021
Oct 31 2021
Viacheslav added a comment to T2498: Expected error when deleting vif that has dhcp-server configured.
What wrong with it?
As you use some service which belong to some interface
Or what you expected?
Provide please an example of configurations and steps to reproduce.
Viacheslav moved T3945: Add route-map for bgp aggregate-address from Backport Candidates to Finished on the VyOS 1.3 Equuleus board.
Bug still present in 1.3.0-epa2 version.
Oct 30 2021
Oct 30 2021
Viacheslav closed T1293: Zone-policy implementation does not allow secondary IP on an interface to communicate as Not Applicable.
Oct 29 2021
Oct 29 2021
n.fort added a comment to T1293: Zone-policy implementation does not allow secondary IP on an interface to communicate.
I have done a lab using 1.3.0-epa2 version, and got no troubles.
Have configured 2 IP addresses on interface, and configured zone based firewall. I'm able to ping everywhere, using both IP addresses of that interface.
Also I checked that counters on firewall rules got increased while pinging from any of both IP addresses.
c-po added a comment to T3943: "netflow source-ip" prevents image upgrades if IP address does not exist locally.
cpo@LR2.wue3# commit [ system flow-accounting ] Your "netflow source-ip" does not exist in the system
Viacheslav added a comment to T3953: IPSec with vti interfaces by default add default route to table 220.
Require migration scripts to check option set vpn ipsec options disable-route-autoinstall in the configuration
Viacheslav added a comment to T3953: IPSec with vti interfaces by default add default route to table 220.
Viacheslav changed the subtype of T3953: IPSec with vti interfaces by default add default route to table 220 from "Bug" to "Feature Request".
Viacheslav moved T3745: op-mode IPSec show vpn ipse sa sorting from Needs Triage to Finished on the VyOS 1.2 Crux (VyOS 1.2.9) board.
PR for crux https://github.com/vyos/vyos-1x/pull/1054
Viacheslav moved T3745: op-mode IPSec show vpn ipse sa sorting from Need Triage to Finished on the VyOS 1.3 Equuleus board.
Viacheslav added a project to T3745: op-mode IPSec show vpn ipse sa sorting: VyOS 1.2 Crux (VyOS 1.2.9).
PR for 1.3 https://github.com/vyos/vyos-1x/pull/1052
@ajgnet Can you re-test it?
Oct 28 2021
Oct 28 2021
Send it by email - christian@poessinger.com
Yep, that's fine - what's the best way the details over to you?
That is great news, any chance I can get SSH access to this machine for testing myself?
The similar FRR tasks
https://github.com/FRRouting/frr/issues/9020
https://github.com/FRRouting/frr/issues/2350
Oct 27 2021
Oct 27 2021
c-po moved T3944: VRRP fails over when adding new group to master from Open to Finished on the VyOS 1.4 Sagitta board.
We've now built a test x710 box for this, so we can test this more easily.
Viacheslav moved T3945: Add route-map for bgp aggregate-address from Need Triage to Backport Candidates on the VyOS 1.3 Equuleus board.
Viacheslav moved T3945: Add route-map for bgp aggregate-address from Open to Finished on the VyOS 1.4 Sagitta board.
PR for address-family ipv6-unicast, 1.3 https://github.com/vyos/vyatta-cfg-quagga/pull/91
Oct 26 2021
Oct 26 2021
Viacheslav changed the status of T3945: Add route-map for bgp aggregate-address from Open to Needs testing.
Viacheslav renamed T3945: Add route-map for bgp aggregate-address from Add route-map for aggregate-address to Add route-map for bgp aggregate-address.
It seems in some cases we need just "reload" to re-read configuration
Same procedure on 1.2.8, when adding new settings to master, it all remains as master.
Log after commit
PR for 1.4 https://github.com/vyos/vyos-1x/pull/1045
Unknown Object (User) added a comment to T3944: VRRP fails over when adding new group to master.
It seems to be because of the keepalived reloading at "commit".
Unknown Object (User) changed the status of T3944: VRRP fails over when adding new group to master from Open to Confirmed.
Oct 25 2021
Oct 25 2021
Viacheslav changed the status of T2627: 'system static-host-mapping' only allows one IP address per hostname, it should allow one IPv4 and one IPv6 simultaneously, a subtask of T2464: DNS bugs (parent task), from Open to Needs testing.
Viacheslav changed the status of T2627: 'system static-host-mapping' only allows one IP address per hostname, it should allow one IPv4 and one IPv6 simultaneously from Open to Needs testing.
Viacheslav changed the status of T2683: no dual stack in system static-host-mapping host-name from In progress to Needs testing.
Viacheslav changed the status of T2763: New SNMP resource request - SNMP over TCP from In progress to Needs testing.
Viacheslav changed the status of T2763: New SNMP resource request - SNMP over TCP from Open to In progress.