Sorted out the WARNING: terminal is not fully functional message with adding the following export command: -
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Sep 29 2022
Sep 29 2022
Yeah, that new nightly release has fixed the issue, thanks. Strangely now getting some weird message in my show commands (WARNING: terminal is not fully functional). This message wasn't there on the previous nightly.
Aug 14 2022
Aug 14 2022
Jun 4 2022
Jun 4 2022
May 31 2022
May 31 2022
egoistdream added a comment to T3976: Missing prefix-list and access-list option from ipv6 route-map.
Yes on this version it is available the requested options for ipv6:
yes, it was added on this version vyos-1.4-rolling-202205311706, please check again
egoistdream added a comment to T3976: Missing prefix-list and access-list option from ipv6 route-map.
I just check and on version: vyos-1.4-rolling-202205310217 is still missing :(
We've added this feature in our latest nightly building release, could you check it ?
fernando changed the status of T3976: Missing prefix-list and access-list option from ipv6 route-map from Open to Needs testing.
May 27 2022
May 27 2022
PR for 1.4 Sagitta branch https://github.com/vyos/vyos-1x/pull/1337
Mar 16 2022
Mar 16 2022
egoistdream added a comment to T3976: Missing prefix-list and access-list option from ipv6 route-map.
FRRouting Release 8.2.2 was relased, when we will see this implemented?
Mar 6 2022
Mar 6 2022
zsdc changed the status of T4002: firewall group network-group long names restriction incorrect behavior from Confirmed to In progress.
Should be fixed by https://github.com/vyos/vyatta-cfg-firewall/pull/32
Feb 25 2022
Feb 25 2022
n.fort added a comment to T4002: firewall group network-group long names restriction incorrect behavior.
This situation is worst, since ipset exposed the error, but vyos cli accepts it, and remains in the running configuration:
Feb 20 2022
Feb 20 2022
Viacheslav changed the subtype of T4001: Feature Request: IPsec transport mode. VyOS can not use local-subnet or remote-subnet when using transport mode from "Task" to "Feature Request".
Jan 3 2022
Jan 3 2022
Viacheslav added a comment to T3976: Missing prefix-list and access-list option from ipv6 route-map.
@egoistdream Just check when this feature was merged. It was implemented in FRR 24th of November, but the latest FRR release was 9th of November
https://frrouting.org/release/8.1/
Jan 2 2022
Jan 2 2022
egoistdream added a comment to T3976: Missing prefix-list and access-list option from ipv6 route-map.
Still the same on vyos-1.4-rolling-202201020317-amd64.iso
Dec 9 2021
Dec 9 2021
Unknown Object (User) changed the status of T4002: firewall group network-group long names restriction incorrect behavior from Open to Confirmed.
Dec 5 2021
Dec 5 2021
As both PRs have been merged now, I'm resolving this issue.
Dec 3 2021
Dec 3 2021
fetzerms added a project to T4034: "make xcp-ng-iso" still includes vyos-xe-guest-utilities: VyOS 1.2 Crux.
Ok. I just found out, that I had an error, when porting my changes to github.
Dec 2 2021
Dec 2 2021
I hope I can find some time tomorrow to also test with crux. My current build job only builds the 1.3.x branch, but should be easy to adjust.
@fetzerms Thanks, Could you test the crux build?
I think I found the issue. Please see https://github.com/vyos/vyos-build/pull/207/
Update: If I run
@sever To me it seems it's not even present in the iso and according to the dpkg logs it seems to install vyos-xe-version.
@fetzerms Is xe-guest-utilities is present in iso image?
I'll look at it soon.
@sever I think you implemented that feature. Am I using it wrong?
Nov 28 2021
Nov 28 2021
egoistdream added a comment to T3976: Missing prefix-list and access-list option from ipv6 route-map.
I have tested with vyos-1.4-rolling-202111281249 and is still missing, I can confirm that the frr version is 8.1.
Nov 25 2021
Nov 25 2021
egoistdream added a comment to T3976: Missing prefix-list and access-list option from ipv6 route-map.
In T3976#112210, @Viacheslav wrote:Already implemented in FRR 8.x, so for first, we should migrate to FRR 8.x if it is possible T3753
Viacheslav added a comment to T3976: Missing prefix-list and access-list option from ipv6 route-map.
Already implemented in FRR 8.x, so for first, we should migrate to FRR 8.x if it is possible T3753
Viacheslav moved T4005: Feature Request: IPsec IKEv1 + IKEv2 for one peer from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa3) board.
Nov 24 2021
Nov 24 2021
marc_s added a comment to T3990: WATCHFRR: crashlog and per-thread log buffering unavailable (due to files left behind in /var/tmp/frr/ after reboot).
Brilliant, thanks @c-po!
c-po moved T4004: IPsec ike-group parameters are not saved correctly (after reboot) from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa3) board.
c-po added a comment to T3990: WATCHFRR: crashlog and per-thread log buffering unavailable (due to files left behind in /var/tmp/frr/ after reboot).
@marc_s I ensure that there is always a volatile folder used for those PIDs
marc_s added a comment to T3990: WATCHFRR: crashlog and per-thread log buffering unavailable (due to files left behind in /var/tmp/frr/ after reboot).
@c-po I see that you've marked this as resolved, but I don't see any comments (maybe I'm doing something wrong). I'd appreciate some feedback.
Is it resolved as in: will be fixed as soon as third-party code is fixed? Or have you made changes to the code to mitigate?
Nov 23 2021
Nov 23 2021
Nov 22 2021
Nov 22 2021
Viacheslav changed the subtype of T4005: Feature Request: IPsec IKEv1 + IKEv2 for one peer from "Task" to "Feature Request".
Unknown Object (User) assigned T4005: Feature Request: IPsec IKEv1 + IKEv2 for one peer to Unknown Object (User).
Nov 21 2021
Nov 21 2021
marc_s renamed T3990: WATCHFRR: crashlog and per-thread log buffering unavailable (due to files left behind in /var/tmp/frr/ after reboot) from Files left behind in /var/tmp/frr/ after reboot to WATCHFRR: crashlog and per-thread log buffering unavailable (due to files left behind in /var/tmp/frr/ after reboot).
marc_s updated the task description for T3990: WATCHFRR: crashlog and per-thread log buffering unavailable (due to files left behind in /var/tmp/frr/ after reboot).
Nov 20 2021
Nov 20 2021
Unknown Object (User) closed T4004: IPsec ike-group parameters are not saved correctly (after reboot) as Resolved.
Unknown Object (User) added a comment to T4004: IPsec ike-group parameters are not saved correctly (after reboot).
A feature request was made with a change in behavior:
https://phabricator.vyos.net/T4005
(Feature Request: IPsec IKEv1 + IKEv2 for one peer)
Unknown Object (User) added a comment to T4005: Feature Request: IPsec IKEv1 + IKEv2 for one peer.
pool request:
https://github.com/vyos/vyatta-cfg-vpn/pull/51
Create an Ike-group without a command "key-exchange" (like in VyOS 1.4):
Nov 19 2021
Nov 19 2021
c-po renamed T3318: Update Linux Kernel to v5.4.208 / 5.10.142 from Update Linux Kernel to v5.4.155 / 5.10.75 to Update Linux Kernel to v5.4.160 / 5.10.80.
Nov 18 2021
Nov 18 2021
Viacheslav added a comment to T4004: IPsec ike-group parameters are not saved correctly (after reboot).
I don't think that it is a bug.
If you don't set any value, it gets default value ikev1
https://github.com/vyos/vyatta-cfg-vpn/blob/d2d4361bffaa0b99c85c7fbf46ddd760ae6512f0/templates/vpn/ipsec/ike-group/node.tag/key-exchange/node.def#L3
Unknown Object (User) created T4005: Feature Request: IPsec IKEv1 + IKEv2 for one peer.
Unknown Object (User) created T4004: IPsec ike-group parameters are not saved correctly (after reboot).
Nov 17 2021
Nov 17 2021
Unknown Object (User) created T4002: firewall group network-group long names restriction incorrect behavior.
Unknown Object (User) created T4001: Feature Request: IPsec transport mode. VyOS can not use local-subnet or remote-subnet when using transport mode.
Nov 15 2021
Nov 15 2021
Viacheslav added a comment to T3988: Feature Request: IPsec Multiple local/remote prefix for the tunnel.
For 1.4 it was implemented in T645
IPSec was completely rewritten in 1.4
Nov 13 2021
Nov 13 2021
Unknown Object (User) renamed T3988: Feature Request: IPsec Multiple local/remote prefix for the tunnel from Feature Request: IPsec Multiple local prefix for the tunnel to Feature Request: IPsec Multiple local/remote prefix for the tunnel.
Unknown Object (User) created T3988: Feature Request: IPsec Multiple local/remote prefix for the tunnel.
Nov 9 2021
Nov 9 2021
Viacheslav added a comment to T3976: Missing prefix-list and access-list option from ipv6 route-map.
FRR doesn't support it.
Nov 8 2021
Nov 8 2021
Viacheslav changed the subtype of T3976: Missing prefix-list and access-list option from ipv6 route-map from "Task" to "Feature Request".
Nov 7 2021
Nov 7 2021
Nov 3 2021
Nov 3 2021
Nov 2 2021
Nov 2 2021
syncer updated the image for VyOS 1.3 Equuleus (1.3.0-epa3) from F1983296: profile to F2021087: profile.
Nov 1 2021
Nov 1 2021
syncer moved T3912: Use a more informative default post-login banner from 1.3.0-epa2 to 1.3.0-epa3 on the VyOS 1.3 Equuleus board.
syncer moved T3913: VRF traffic fails after upgrade from 1.3.0-RC6 to 1.3.0-EPA1/2 from 1.3.0-epa2 to 1.3.0-epa3 on the VyOS 1.3 Equuleus board.
syncer moved T3914: VRRP rfc3768-compatibility doesn't work with unicast peers from 1.3.0-epa2 to 1.3.0-epa3 on the VyOS 1.3 Equuleus board.
syncer moved T3933: The firewall does not filter incoming traffic on the interface with vrf. from 1.3.0-epa2 to 1.3.0-epa3 on the VyOS 1.3 Equuleus board.
syncer moved T3045: Changes to Conntrack-Sync don't apply correctly (Mutlicast->UDP) from 1.3.0-epa1 to 1.3.0-epa3 on the VyOS 1.3 Equuleus board.
To enable IPv6 only it is required some new options in CLI, which are not presented in 1.3 yet
c-po moved T3846: dmvpn configuration not reapllied after "restart vpn" from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa3) board.
c-po edited projects for T3846: dmvpn configuration not reapllied after "restart vpn", added: VyOS 1.3 Equuleus (1.3.0-epa3); removed VyOS 1.3 Equuleus (1.3.0-epa1).
c-po moved T3956: GRE tunnel - unable to move from source-interface to source-address, commit error from Need Triage to Finished on the VyOS 1.4 Sagitta board.
Viacheslav changed the status of T3940: DHCP client does not remove IP address when stopped by the 02-vyos-stopdhclient hook from Open to Needs testing.
Oct 31 2021
Oct 31 2021
c-po changed the status of T3956: GRE tunnel - unable to move from source-interface to source-address, commit error from Open to In progress.
c-po renamed T3943: "netflow source-ip" prevents image upgrades if IP address does not exist locally from VyOS 1.2.7 upgrade to 1.3.0-epa2 config error if flow-accounting is set to "netflow source-ip" prevents image upgrades if IP address does not exist locally.
c-po moved T3943: "netflow source-ip" prevents image upgrades if IP address does not exist locally from Need Triage to Finished on the VyOS 1.4 Sagitta board.
Viacheslav closed T3341: Wrong behavior of the "reset vpn ipsec-peer XXX tunnel XXX" command as Resolved.
Viacheslav added a comment to T3341: Wrong behavior of the "reset vpn ipsec-peer XXX tunnel XXX" command.
PR for crux https://github.com/vyos/vyatta-op-vpn/pull/29
Oct 30 2021
Oct 30 2021
PR for crux https://github.com/vyos/vyos-1x/pull/1056
Oct 29 2021
Oct 29 2021
c-po changed the status of T3943: "netflow source-ip" prevents image upgrades if IP address does not exist locally from Open to In progress.
After some investigation, we figured out several ways how to solve or at least mitigate the problem. From my point of view, the optimal for both developers and customers is the next one.
Viacheslav moved T3942: Generate IPSec debug archive from op-mode from Backport Candidates to Finished on the VyOS 1.3 Equuleus (1.3.0-epa3) board.