- User Since
- Jul 14 2020, 6:18 PM (39 w, 5 d)
Version: VyOS 1.4-rolling-202104151445
Sun, Apr 11
Submitted following PR:
Wed, Mar 31
Parent task: https://phabricator.vyos.net/T3356
Tue, Mar 30
The workaround for save command does not seem to work, have you tried for commit-archive option ?
Mon, Mar 29
This command is used to generate the ssh fingerprint of your host when vyos cannot verify the legitimacy of the remote server
Sat, Mar 27
Tue, Mar 23
Fixed in the latest version:1.4-rolling-202103230217
Mon, Mar 22
Post the migration of the script from /opt/vyatta/bin/vyos-strip-config.pl to /usr/libexec/vyos/strip-private.py, the strip-private seems to be not working when the ipv6 address is configured to an interface.
Mar 8 2021
Mar 5 2021
Submitted this PR to fix the issue:
Mar 4 2021
Feb 20 2021
Hi, I have tried these set of configuration and the openvpn connection was up and working fine.
Feb 17 2021
This issue has been fixed in this commit: https://github.com/vyos/vyos-1x/commit/0fb5cc02c6c16ef410c1b1f746c1fbfbc40a0da0
Feb 16 2021
The translation is working properly now but it is not showing in the command output:
Feb 6 2021
The pull request is created to fix this issue:
Feb 3 2021
@Viacheslav , I tested in the 1.4 version, it seems that the neighborship is stuck in ExStart state with basic config. This behavior is not seen in 1.2.5 and 1.3
And also no frr.log is created.
Feb 1 2021
@Viacheslav , working on it and update you soon.
Dec 18 2020
Dec 14 2020
Pull request submitted to change the permissions:
Dec 4 2020
Nov 7 2020
Issue is fixed in the latest rolling release. The IPv4 remote-host hostname in client mode works without adding the option '--proto udp4'.
Tested in VyOS 1.3-rolling-202011060217
Nov 5 2020
Nov 4 2020
Oct 30 2020
Can you please share the entire configuration and version of the VyOS to reproduce the issue in the lab.
Oct 27 2020
Resolved in T2985
I have tested on this rolling release VyOS 1.3-rolling-202010231135 and created a lab setup similar to the reporter's setup.
Oct 19 2020
Oct 13 2020
Oct 2 2020
Reproduced the issue in the rolling release VyOS 1.3-rolling-202009300117 and the route-map configuration wiped out after the reboot with the error as mentioned in the problem description and happens only when the bridge address is added for src and not for other interface types.
Sep 22 2020
Sep 18 2020
Tested in LTS 1.2.5 and latest rolling release, where it is not allowing to add the AA:NN along with Additive
Sep 13 2020
Tested in the latest rolling release and observed that after deleting the member interface, the assigned interface is remained in the admin down state.
Sep 10 2020
Aug 17 2020
In addition to the workaround provided in the task T2747, the following configuration could also be added to the existing configuration:
Aug 6 2020
The commit fails when the local-ip option is included only with the 6RD prefix options (without 6RD option, 6in4 tunnel is created). In the tunnel.py script, local value is not defined as result stack trace is received
Jul 29 2020
The issue did not reproduce neither in 1.2.5 nor in 1.3 version.
Try in the new release and re-open the ticket if any new information appeared.
Jul 24 2020
I have tested the steps as mentioned in the description in VyOS 1.3-rolling-202007220117 and the issue did not reproduce.
Please try to create a new user in the latest version and share your feedback.
Jul 21 2020
I have tried the above scenario in the VyOS 1.3-rolling-202007200117 which is the latest version and the issue did not reproduce. So I would request you to try in the latest version and share your feedback.
Jul 20 2020
Even after restart of the server, the local ip does reflect in the in the interface tunnel status.
I could see that your OS version is 1.3-rolling-202005051136, could you please check in the latest version.
Jul 17 2020
The issue did not reproduce in the VyOS 1.3-rolling-202007140117 version. Also commit fails if the local-ip is missing
Reproduced in VyOS 1.3-rolling-202007140117 version
When the mac address is added to the interface manually, the interface is marked down.
A PR #502 is created to fix the issue:
Jul 16 2020
This is issue is reproduced in the VyOS 1.3-rolling-202007140117 version.
While changing the mode of the pseudo-ethernet interface, the error "RTNETLINK answers: Invalid argument" is received
@thomas-mangin please fix it
Jul 15 2020
This is issue is reproduced in the VyOS 1.3-rolling-202007140117 version. The interface description is showing up-to 23 characters in the "show interface output" only.
It shows correctly in the command output of 'sudo ip l" Tested for different interface types.