we've added this ability to configure the topology on isis :
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed Search
May 29 2024
May 29 2024
fernando added a comment to T6332: IPv6-only ISIS (or, in general, dual topology) is not working with other devices running frr.
fernando changed the subtype of T6332: IPv6-only ISIS (or, in general, dual topology) is not working with other devices running frr from "Bug" to "Feature Request".
fernando changed the status of T6332: IPv6-only ISIS (or, in general, dual topology) is not working with other devices running frr from Open to Needs testing.
fernando added a comment to T6332: IPv6-only ISIS (or, in general, dual topology) is not working with other devices running frr.
agree ,it's more a feature than a bug : PR https://github.com/vyos/vyos-1x/pull/3537
Viacheslav closed T6411: CGNAT does not rely on seq number, a subtask of T5169: Add CGNAT Carrier-Grade NAT based on nftables, as Resolved.
Viacheslav added a comment to T6332: IPv6-only ISIS (or, in general, dual topology) is not working with other devices running frr.
More a feature request than a bug
fernando added a comment to T6332: IPv6-only ISIS (or, in general, dual topology) is not working with other devices running frr.
the problem here is that MT options is enable by default when the RIB has ipv4, if not not-MT is enable by default on IPv4 .So, you need to add additional topologies (ipv6-unicast , ipv6-multicast,etc)
May 28 2024
May 28 2024
Viacheslav changed the status of T6411: CGNAT does not rely on seq number, a subtask of T5169: Add CGNAT Carrier-Grade NAT based on nftables, from Open to In progress.
jestabro moved T6404: Include constraintGroup element in reference tree from Open to Finished on the VyOS 1.5 Circinus board.
ssasso added a comment to T6332: IPv6-only ISIS (or, in general, dual topology) is not working with other devices running frr.
@Viacheslav here you go:
Viacheslav added a comment to T6332: IPv6-only ISIS (or, in general, dual topology) is not working with other devices running frr.
Can you provide set of commands instead? Bug-report-guidelines
Viacheslav triaged T6412: CGNAT allocation calculation may sometimes be incorrect as Normal priority.
mersl added a comment to T6332: IPv6-only ISIS (or, in general, dual topology) is not working with other devices running frr.
@ssasso - thanks for this good catch! Coming from a Junos world, I was a bit surprised at the first place when I enabled ISIS and found no ipv6 isis routes and no multi-topology config option (and yes - we have multi-topology in place)
Viacheslav renamed T6411: CGNAT does not rely on seq number from CGNAt does not rely on seq number to CGNAT does not rely on seq number.
Viacheslav added a parent task for T6411: CGNAT does not rely on seq number: T5169: Add CGNAT Carrier-Grade NAT based on nftables.
The charon identifier also shows IKE name of the SA; this way, we can identify peers in the logs https://github.com/vyos/vyos-build/blob/b809886538eaad66b8756be8f5e758584f88e6a6/data/live-build-config/hooks/live/30-strongswan-configs.chroot#L41-L54
The current show log vpn does https://github.com/vyos/vyos-1x/blob/48e5266e2bca8d1d7a2ee4bacbe0e6628de3fa66/op-mode-definitions/show-log.xml.in#L710
May 27 2024
May 27 2024
tested new cli structure, it combine the new mach-group and old syntax :
PR opened: https://github.com/vyos/vyos-1x/pull/3532
zsdc moved T6395: Enable VFIO No-IOMMU support in kernel config from Need Triage to Finished on the VyOS 1.4 Sagitta (1.4.0) board.
zsdc added a project to T6395: Enable VFIO No-IOMMU support in kernel config: VyOS 1.4 Sagitta (1.4.0).
Viacheslav added a comment to T6398: Missing the package kpartx for the container vyos-build:current-arm64.
The dependency allowed for 386/amd64 only https://github.com/vyos/vyos-build/blob/b809886538eaad66b8756be8f5e758584f88e6a6/docker/Dockerfile#L281
Though the package is available for ARM
Embezzle changed the status of T6409: Remove unused parameter node from reverse-proxy backend from Open to In progress.
As several CA were allowed some time ago it is a bug with op-mode generator.
There is a list of CA's https://github.com/vyos/vyos-1x/blob/48e5266e2bca8d1d7a2ee4bacbe0e6628de3fa66/src/op_mode/ikev2_profile_generator.py#L147
The template https://github.com/vyos/vyos-1x/blob/current/data/templates/ipsec/windows_profile.j2
I made a PR that uses an implementation with a separate function: https://github.com/vyos/vyatta-cfg/pull/79
dmbaturin edited projects for T6402: Invalid variables referenced in reverse proxy validation, added: VyOS 1.4 Sagitta (1.4.0-GA); removed VyOS 1.4 Sagitta (1.4.0).
dmbaturin triaged T6401: Attempts to delete vlan-to-vni option causes an unhandled exception as High priority.
natali-rs1985 changed the status of T6389: Check architecture and flavor compatibility on upgrade attempts from Open to In progress.
drw_08 triaged T6405: Add disk_setup and mounts in vyos cloud-init config under cloud_init_modules as Normal priority.
drw_08 updated the task description for T6405: Add disk_setup and mounts in vyos cloud-init config under cloud_init_modules .
May 26 2024
May 26 2024
alainlamar changed the status of T6320: WiFi: Enable support for 6GHz AccesPoints from Open to Needs testing.
c-po closed T6377: PermissionError on /config/auth/letsencrypt/live/ when running show pki as Resolved.
c-po moved T6377: PermissionError on /config/auth/letsencrypt/live/ when running show pki from Need Triage to Finished on the VyOS 1.4 Sagitta (1.4.0-GA) board.
c-po moved T6400: pki: unable to generate fingerprint for ACME issued certificates from Need Triage to Finished on the VyOS 1.4 Sagitta (1.4.0-GA) board.
Embezzle closed T6370: Add option to set custom HTTP headers in reverse-proxy responses as Resolved.
Tested as working in: 1.5-rolling-202405240020
May 25 2024
May 25 2024
c-po moved T6377: PermissionError on /config/auth/letsencrypt/live/ when running show pki from Open to Finished on the VyOS 1.5 Circinus board.
c-po moved T6400: pki: unable to generate fingerprint for ACME issued certificates from Open to Finished on the VyOS 1.5 Circinus board.
c-po changed the status of T6400: pki: unable to generate fingerprint for ACME issued certificates from Open to In progress.
c-po changed the status of T6377: PermissionError on /config/auth/letsencrypt/live/ when running show pki from Open to In progress.
Is this meant to be possible this way?
Viacheslav triaged T6398: Missing the package kpartx for the container vyos-build:current-arm64 as Normal priority.
talmakion added a comment to T6157: Can not create two GRE tunnels to the same DST but from different SRC addresses.
As far as I can tell the test will always error if the remote matches and neither source-interface and source-address are configured differently, including the case where they're both blank (source-interface == None on both tunnels triggers this particular case).
c-po moved T6345: Source NAT Port Mapping setting of Fully-Random is superfluous in Kernels 5.0 onwards from Open to 1.4.0-GA on the VyOS 1.4 Sagitta board.
c-po moved T6345: Source NAT Port Mapping setting of Fully-Random is superfluous in Kernels 5.0 onwards from Open to Finished on the VyOS 1.5 Circinus board.
Only recently moved from 1.3 to 1.5 and noticed rollback-soft immediately (great stuff), the completion message was annoying me too.
May 24 2024
May 24 2024
zsdc moved T6395: Enable VFIO No-IOMMU support in kernel config from Open to In Progress on the VyOS 1.5 Circinus board.
PR for 1.5: https://github.com/vyos/vyos-build/pull/638