- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed All Stories
All Stories
All Stories
May 26 2024
May 26 2024
alainlamar changed the status of T6320: WiFi: Enable support for 6GHz AccesPoints from Open to Needs testing.
Vijayakumar changed the status of T6397: Triger action on merge, a subtask of T6309: Check code quality with CodeQL, from Open to In progress.
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.
GitHub <[email protected]> committed rVYOSONEXb35188de4f87: Merge pull request #3520 from vyos/mergify/bp/sagitta/pr-3518 (authored by c-po).
GitHub <[email protected]> committed rVYOSONEX6b3ec33cb381: Merge pull request #3521 from vyos/mergify/bp/sagitta/pr-3517 (authored by c-po).
Mergify <37929162+mergify[bot]@users.noreply.github.com> committed rVYOSONEXb0c2698aeff5: op-mode: T6400: pki: unable to generate fingerprint for ACME issued certificates (authored by c-po).
Mergify <37929162+mergify[bot]@users.noreply.github.com> committed rVYOSONEX9f02740f063b: op-mode: T6377: must call pki.py helper as root to work with ACME certificates (authored by c-po).
GitHub <[email protected]> committed rVYOSONEX22dae74ef603: Merge pull request #3517 from c-po/pki-t6377 (authored by c-po).
GitHub <[email protected]> committed rVYOSONEXb9cbf6cf35d1: Merge pull request #3518 from c-po/pki-t6400 (authored by c-po).
GitHub <[email protected]> committed rVYOSONEX4a9befb92550: Merge pull request #3519 from c-po/dhcpv6-T3493 (authored by c-po).
Embezzle closed T6370: Add option to set custom HTTP headers in reverse-proxy responses as Resolved.
Tested as working in: 1.5-rolling-202405240020
This is actually a "wrong" error, or a real error with a wrong fix.
May 25 2024
May 25 2024
GitHub <[email protected]> committed rVYOSONEX9301c507f91e: T6399: added reusable workflows codeowners file to sagitta (#3515) (authored by Vijayakumar A <[email protected]>).
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.
Vijayakumar closed T6399: add reusable workflows and codeowners to vyos-1x sagitta and equuleus, a subtask of T6309: Check code quality with CodeQL, as Resolved.
c-po changed the status of T6377: PermissionError on /config/auth/letsencrypt/live/ when running show pki from Open to In progress.
c-po added a comment to T6377: PermissionError on /config/auth/letsencrypt/live/ when running show pki.
[email protected]:~$ show configuration commands | match pki set pki ca STAGING-PEM certificate 'MIIFWzCCA0OgAwIBAgIQTfQrldHumzpMLrM7jRBd1jANBgkqhkiG9w0BAQsFADBmMQswCQYDVQQGEwJVUzEzMDEGA1UEChMqKFNUQUdJTkcpIEludGVybmV0IFNlY3VyaXR5IFJlc2VhcmNoIEdyb3VwMSIwIAYDVQQDExkoU1RBR0lORykgUHJldGVuZCBQZWFyIFgxMB4XDTIwMDkwNDAwMDAwMFoXDTI1MDkxNTE2MDAwMFowWTELMAkGA1UEBhMCVVMxIDAeBgNVBAoTFyhTVEFHSU5HKSBMZXQncyBFbmNyeXB0MSgwJgYDVQQDEx8oU1RBR0lORykgQXJ0aWZpY2lhbCBBcHJpY290IFIzMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAu6TR8+74b46mOE1FUwBrvxzEYLck3iasmKrcQkb+gy/z9Jy7QNIAl0B9pVKp4YU76JwxF5DOZZhi7vK7SbCkK6FbHlyU5BiDYIxbbfvOL/jVGqdsSjNaJQTg3C3XrJja/HA4WCFEMVoT2wDZm8ABC1N+IQe7Q6FEqc8NwmTSnmmRQm4TQvr06DP+zgFK/MNubxWWDSbSKKTH5im5j2fZfg+j/tM1bGaczFWw8/lSnukyn5J2L+NJYnclzkXoh9nMFnyPmVbfyDPOc4Y25aTzVoeBKXa/cZ5MM+WddjdLbiWvm19f1sYn1aRaAIrkppv7kkn83vcth8XCG39qC2ZvaQIDAQABo4IBEDCCAQwwDgYDVR0PAQH/BAQDAgGGMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDATASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBTecnpI3zHDplDfn4Uj31c3S10uZTAfBgNVHSMEGDAWgBS182Xy/rAKkh/7PH3zRKCsYyXDFDA2BggrBgEFBQcBAQQqMCgwJgYIKwYBBQUHMAKGGmh0dHA6Ly9zdGcteDEuaS5sZW5jci5vcmcvMCsGA1UdHwQkMCIwIKAeoByGGmh0dHA6Ly9zdGcteDEuYy5sZW5jci5vcmcvMCIGA1UdIAQbMBkwCAYGZ4EMAQIBMA0GCysGAQQBgt8TAQEBMA0GCSqGSIb3DQEBCwUAA4ICAQCNDLam9yN0EFxxn/3p+ruWO6n/9goCAM5PT6cC6fkjMs4uas6UGXJjr5j7PoTQf3C1vuxiIGRJC6qxV7yc6U0X+w0Mj85sHI5DnQVWN5+D1er7mp13JJA0xbAbHa3Rlczny2Q82XKui8WHuWra0gb2KLpfboYj1Ghgkhr3gau83pC/WQ8HfkwcvSwhIYqTqxoZUq8HIf3M82qS9aKOZE0CEmSyR1zZqQxJUT7emOUapkUN9poJ9zGc+FgRZvdro0XByphWXDaqMYph0DxW/10ig5j4xmmNDjCRmqIKsKoWA52wBTKKXK1na2ty/lW5dhtAxkz5rVZFd4sgS4J0O+zm6d5GRkWsNJ4knotGXl8vtS3X40KXeb3A5+/3p0qaD215Xq8oSNORfB2oI1kQuyEAJ5xvPTdfwRlyRG3lFYodrRg6poUBD/8fNTXMtzydpRgyzUQZh/18F6B/iW6cbiRN9r2Hkh05Om+q0/6w0DdZe+8YrNpfhSObr/1eVZbKGMIYqKmyZbBNu5ysENIK5MPc14mUeKmFjpN840VR5zunoU52lqpLDua/qIM8idk86xGWxx2ml43DO/Ya/tVZVok0mO0TUjzJIfPqyvr455IsIut4RlCR9Iq0EDTve2/ZwCuGhSjpTUFGSiQrR2JK2Evp+o6AETUkBCO1aw0PpQBPDQ==' set pki certificate vyos acme domain-name 'lr5.wue4.mybll.net' set pki certificate vyos acme email '[email protected]' set pki certificate vyos acme url 'https://acme-staging-v02.api.letsencrypt.org/directory'
Viacheslav triaged T6396: MINOR Typo: set system conntrack timeout custom ipv4 rule X as Normal priority.
Is this meant to be possible this way?
Vijayakumar changed the status of T6399: add reusable workflows and codeowners to vyos-1x sagitta and equuleus, a subtask of T6309: Check code quality with CodeQL, from Open to In progress.
Vijayakumar changed the status of T6399: add reusable workflows and codeowners to vyos-1x sagitta and equuleus from Open to In progress.
New source release, not in Debian yet: https://github.com/acassen/keepalived/releases/tag/v2.3.1
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).
Vijayakumar closed T6392: validate backport with reusable action, a subtask of T6309: Check code quality with CodeQL, as Resolved.
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
zsdc changed the status of T6395: Enable VFIO No-IOMMU support in kernel config from Open to In progress.
talmakion added a comment to T5049: Configure GRE over IPsec tunnel when source port is in VRF, OSPF causes GRE tunnel broken..
I've just been picking at this one tonight because it's close to some areas of interest (DMVPNs in VRFs), so hopefully this input is useful and appropriate:
Viacheslav moved T6391: load-balancing reverse-proxy: typo in timeout help from Need Triage to Finished on the VyOS 1.4 Sagitta (1.4.0-GA) board.
GitHub <[email protected]> committed rVYOSONEXb8d844027482: load-balancing haproxy: T6391: fix typo in timeout help (#3513) (#3514) (authored by mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>).
yes, that would be a very good solution/implementation
GitHub <[email protected]> committed rVYOSONEX9cde20b45783: Merge pull request #3512 from vyos/mergify/bp/sagitta/pr-3487 (authored by dmbaturin).
n.fort changed the status of T6394: Migrate conntrack timeout sysctl parameter to firewall from Open to In progress.
alainlamar added a comment to T6318: vyos-1x: WiFi Regulatory Domain should be set system-wide instead of per-device.
Is there already something in the works? As for now, there seem to be issues with regdom settings in VyOS 1.5 anyways (see https://vyos.dev/T6320 "Quirks and Workarounds").
Probably the best way will be moving the config to the vrf section (not implemented)
For example:
set vrf name foo service dhcp-server shared-network-name eth1 option default-router '192.168.1.1' set vrf name foo service dhcp-server shared-network-name eth1 subnet 192.168.1.0/24 lease '300' set vrf name foo service dhcp-server shared-network-name eth1 subnet 192.168.1.0/24 range default start '192.168.1.10' set vrf name foo service dhcp-server shared-network-name eth1 subnet 192.168.1.0/24 range default stop '192.168.1.100' set vrf name foo service dhcp-server shared-network-name eth1 subnet 192.168.1.0/24 subnet-id '1'
And start several instances, each with its configuration.
you have to adapt a few more things, if absolutely necessary it also works with several VRFs - but it is very ugly...
Mergify <37929162+mergify[bot]@users.noreply.github.com> committed rVYOSONEXf9363fb00b80: load-balancing haproxy: T6391: fix typo in timeout help (#3513) (authored by hirnpfirsich).
GitHub <[email protected]> committed rVYOSONEX609563d6acfe: load-balancing haproxy: T6391: fix typo in timeout help (#3513) (authored by hirnpfirsich).
FYI: The configuration is valid and works. It just fails during boot.
The similar task for redirect T260
I assume that workaround would only work for a single VRF or can one do something like this?
The following can be configured as a quick and dirty workaround:
May 23 2024
May 23 2024
I am already working on the PR :)