PR
https://github.com/vyos/vyos-1x/pull/2659
updated and extended for T5660.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed All Stories
All Stories
All Stories
Feb 28 2024
Feb 28 2024
jestabro added a comment to T5839: Remove trivial redundancies in calls to config dependency scripts.
natali-rs1985 changed the status of T5504: Make it possible to set more than one peer-address in unicast VRRP from Open to In progress.
Viacheslav moved T6065: Duplicate lines in build-vyos-image script cause sagitta build to fail from Need Triage to Finished on the VyOS 1.4 Sagitta board.
SrividyaA added a comment to T6055: PKI error: "failed to install x value" when executed the command from conf mode.
Tested in VyOS 1.5-rolling-202402280022 and it works now :
Feb 27 2024
Feb 27 2024
hcuk94 closed T6065: Duplicate lines in build-vyos-image script cause sagitta build to fail as Resolved.
This was resolved by merged PR. Build process now succeeds.
sarthurdev moved T6073: Conntrack/NAT not being disabled when VRFs are defined from Need Triage to In Progress on the VyOS 1.4 Sagitta board.
sarthurdev changed the status of T6073: Conntrack/NAT not being disabled when VRFs are defined from In progress to Needs testing.
c-po changed Difficulty level from unknown to easy on T4270: When "ignore-hosts-file" is unset, local hostname of the router resolves to 127.0.1.1 in the DNS forwarding service.
c-po added a comment to T4270: When "ignore-hosts-file" is unset, local hostname of the router resolves to 127.0.1.1 in the DNS forwarding service.
We should keep this behavior in 1.3.7 but change it for 1.4 and onwards
c-po added a comment to T6074: container: do not allow deleting images which have a container running.
c-po changed the status of T6074: container: do not allow deleting images which have a container running from Open to In progress.
c-po changed the status of T6074: container: do not allow deleting images which have a container running, a subtask of T6060: op-mode: container: support removing all container images at once, from Open to In progress.
sarthurdev renamed T6073: Conntrack/NAT not being disabled when VRFs are defined from Conntrack/NAT not being disabled to Conntrack/NAT not being disabled when VRFs are defined.
sarthurdev closed T5080: Disable conntrack by default, a subtask of T5160: Firewall refactor, as Resolved.
Not a regression as far as this task is concerned. Will update T6073
Full configuration:
Reopened on @Apachez request
Viacheslav triaged T6073: Conntrack/NAT not being disabled when VRFs are defined as Normal priority.
Provide please show configuration commands or attach /config/config.boot file.
How do one re-open? :-)
Similar task(s):
Aldemaro updated the task description for T6073: Conntrack/NAT not being disabled when VRFs are defined.
Yes, this is only used by the GraphQL API.
adestis added a comment to T5909: Container registry with authentication prevents config load (section container) after reboot.
Thank you very much!
vse-github edited projects for T6072: https api cors allow-origin not applied, added: VyOS 1.4 Sagitta; removed VyOS 1.4 Sagitta (1.4.0).
vse-github renamed T6072: https api cors allow-origin not applied from https api cors allowed-origin not applied to https api cors allow-origin not applied.
Apachez added a comment to T6071: firewall: CLI description limit of 256 characters cause config upgrade issues.
While at it having a description for a firewall rule within the firewall itself thats longer than 256 is just "wrong" IMHO aka "you are doing it wrong".
Feb 26 2024
Feb 26 2024
dmbaturin triaged T6070: bnx2x NIC causes a commit error due to incorrect implementation of EEE status reading as High priority.
dmbaturin triaged T6069: HTTP API segfault during concurrent configuration requests as Normal priority.
dmbaturin triaged T6067: show lldp neighbors detail (detail not available) even when configured and running as Low priority.
dmbaturin triaged T6065: Duplicate lines in build-vyos-image script cause sagitta build to fail as Urgent! priority.
up-n-atom updated the task description for T6070: bnx2x NIC causes a commit error due to incorrect implementation of EEE status reading.
@tjjh89017 Have a look at https://vyos.dev/T5965
In T5619#177706, @ErnyTech wrote:Unfortunately I haven't seen this before, for me this choice of using the out-of-tree driver is extremely wrong!
Most of the community's development is done on the mainline kernel driver (where among other things I'm working on sending patches to improve the ixgbe driver), if there are issues in the mainline driver they should be reported or resolved with a patch to be applied in vyos downstream and then send it to the Intel-wired-lan mailing list.
Please @samip537 can you tell me in a short list what exactly problems you encounter with the mainline Linux driver?
danhusan edited projects for T5811: static dhcp-interface routes not installed, added: VyOS 1.4 Sagitta (1.4.0-epa1); removed VyOS 1.4 Sagitta.
I hope a proper solution can be found as the current behavior of segfaulting the api server is a very unpleasant place to be while working on tooling for vyos.
Cf. the details leading to having changed this for config_op:
https://vyos.dev/T5305
I have create a pr with the required change to fix this issue if the problem described in T5305 is no longer a blocker.
@Viacheslav the problem was still solved in 1.4. (I don't know, when I will have the chance to test with 1.5.) The reason this issue exists is, that 1.4. was not declared to be stable back then. Now since 1.4 is official released as stable we can use 1.4 instead of 1.3. So I think we can close the issue.
aalmenar updated the task description for T6067: show lldp neighbors detail (detail not available) even when configured and running.
aalmenar added a comment to T6067: show lldp neighbors detail (detail not available) even when configured and running.
I even have a router with it working:
sarthurdev triaged T6068: Support active-active and active-passive high availability modes in DHCP server as Wishlist priority.
On 1.4.0-epa1, there is no longer an indication that configuration file actually has been saved.
aalmenar added a comment to T6067: show lldp neighbors detail (detail not available) even when configured and running.
This is not a feature request, this has been working until made the detail available only when the lldpd service was running or not. It was even documented:
Viacheslav closed T6067: show lldp neighbors detail (detail not available) even when configured and running as Invalid.
It is not the bug.
There is the feature request T6045
Viacheslav triaged T5083: extend interface schema to include which parameters are required as Normal priority.
Viacheslav placed T5083: extend interface schema to include which parameters are required up for grabs.
c-po moved T6064: Can not build VyOS if repository it not cloned to a branch from In Progress to Finished on the VyOS 1.4 Sagitta (1.4.0-epa1) board.
c-po moved T5754: Update to StrongSwan 5.9.11 from Need Triage to Finished on the VyOS 1.4 Sagitta (1.4.0-epa1) board.
c-po moved T5754: Update to StrongSwan 5.9.11 from Backport Candidates to Finished on the VyOS 1.5 Circinus board.
c-po moved T5754: Update to StrongSwan 5.9.11 from Need Triage to 1.4.0-epa1 on the VyOS 1.4 Sagitta board.
1.4 and 1.5 run on strongswan 5.9.11
c-po moved T6064: Can not build VyOS if repository it not cloned to a branch from In Progress to Finished on the VyOS 1.5 Circinus board.
jalen updated the task description for T6066: Unhandled exception when setting same network in a different OSPF area.
@c-po I suggest that we should reopen this issue. And I have a question is why DHCP server with VRF support works correctly in v1.4 but not in v1.5？
Feb 25 2024
Feb 25 2024
sarthurdev changed the status of T6063: Kea DHCP: Expose match-client-id setting from Open to Needs testing.
I would say this would still be useful for c-states, and also for other things, for example setting hugepages, and If I remember right, the VPP addon also requires boot arguments be added.
c-po edited projects for T2468: Passwords with special characters fail in commit-archive, added: VyOS 1.4 Sagitta (1.4.0-epa1); removed VyOS 1.4 Sagitta.
Knob is now available starting 1.4.0-rc3 to disable spectre. Is this sufficient or you still have a usecase for cstates?
c-po changed the status of T2447: Additional boot argument configuration to limit CPU C-States from Open to Needs reporter action.
I'm using a workaround. I'm running a process in a script /config/scripts/vyos-postconfig-bootup.script:
In T4733#148990, @c-po wrote:Hi @daniil and @NikolayP,
this is already implemented and working. You need to specify: set vrf bind-to-all and it will work out of the box with your configuration stated above
hcuk94 added a comment to T6065: Duplicate lines in build-vyos-image script cause sagitta build to fail.
I have created a PR to resolve this issue: https://github.com/vyos/vyos-build/pull/511
In T4733#148990, @c-po wrote:Hi @daniil and @NikolayP,
this is already implemented and working. You need to specify: set vrf bind-to-all and it will work out of the box with your configuration stated above
c-po moved T6064: Can not build VyOS if repository it not cloned to a branch from Need Triage to In Progress on the VyOS 1.4 Sagitta (1.4.0-epa1) board.
c-po moved T6064: Can not build VyOS if repository it not cloned to a branch from Need Triage to In Progress on the VyOS 1.5 Circinus board.
c-po updated the task description for T6064: Can not build VyOS if repository it not cloned to a branch.
c-po updated the task description for T6064: Can not build VyOS if repository it not cloned to a branch.
c-po updated the task description for T6064: Can not build VyOS if repository it not cloned to a branch.
c-po changed the status of T6064: Can not build VyOS if repository it not cloned to a branch from Open to In progress.