Hi, I’d be happy to take this on.

PR: https://github.com/vyos/vyos-1x/pull/3778

@Viacheslav found the issue which I've documented below.

Will investigate!

Should this ticket be closed? I see the PRs were merged more than a month ago.

PR for 1 and 3: https://github.com/vyos/vyos-1x/pull/3700

PR: https://github.com/vyos/vyos-1x/pull/3700

Consideration: adding this new command to the show tech-support report op command when available.

Documenting what I've found regarding Bug #2:

Updated task description to denote two issues (Bug 1 and Bug 2) with show tech-support report.

Can this be assigned to me please, will give it a go.

PR opened here: https://github.com/vyos/vyos-1x/pull/3563/

PR opened: https://github.com/vyos/vyos-1x/pull/3532

Resolved, merged PR: https://github.com/vyos/vyos-1x/pull/3508

Follow up, I was able to make nat.py throw the error below.

@Viacheslav, same behaviour exists for epa3, I numbered mine 999 so as not to interfere with existing rules.

@Viacheslav
Happy to dig into this if can assign it to me.

In T3493#189273, @Viacheslav wrote:

Does 1.5 has the same bug?

PR merged: https://github.com/vyos/vyos-1x/pull/3499/

Question as I don’t know the projects’ history: the Python ipaddress library seems to offer the features of ipaddrcheck plus some additional nice to haves. Is a migration from ipaddrcheck to ipaddress being considered?

Believe this task can be closed the PRs for Sagitta and Current were merged:
Merged PR in Current: https://github.com/vyos/vyos-1x/pull/3307
Merged PR in Sagitta: https://github.com/vyos/vyos-1x/pull/3395

Can I claim this? will submit a Draft PR for review, I have it resolved (see test output below)

Related https://vyos.dev/T921

More info related to PowerDNS DNSdist: https://powerdns.org/dnsdist-md/dnsdist-diagrams.md.html

@adestis did your previous solution account for non-IP address characters in a given blocklist? For example the https://www.spamhaus.org/drop/dropv6.txt list has a bunch of stuff that would need to be ignored.

PR: https://github.com/vyos/vyos-1x/pull/3347

@Viacheslav or another of the Maintainers:

From initial PR these two feedback points are now implemented. PR has been amended see https://github.com/vyos/vyos-1x/pull/3307

@dmbaturin, @sever
Would love your input regarding the lack of headers when using the -c option. I've created a PoC around "chronyc -c activity" as it was the most straight forward command to start with.

Status update:

• "Like for like" functionality between .sh script and .py script is complete and working (can be viewed in PR)
• Raw output capability -> in progress

@Viacheslav concur that it looks to be resolved. The last log entry was at 9:10 and nothing telegraph-related has been logged in almost 30 minutes since. I will close ticket. Thank your help and insight.

@dmbaturin PR is here https://github.com/vyos/vyos-1x/pull/3307

@dmbaturin hope you don't mind but this looked like a good task for a beginner and with it being low priority thought I'd give it a go.

Editing config.boot.default has addressed this. Pull request opened for comments/integration here: https://github.com/vyos/vyos-build/pull/559

Editing config.boot.default has addressed this. Pull request opened for comments/integration here: https://github.com/vyos/vyos-build/pull/559

Editing config.boot.default has addressed this. Pull request opened for comments/integration here: https://github.com/vyos/vyos-build/pull/559

https://vyos.dev/T3771 was resolved should this one be closed as well given your comment @sever ?

I gave it a go due to similarities between this and https://vyos.dev/T6123.

In T6099#182627, @Viacheslav wrote:

@Giggum Can you check it in 1.5?

Yeah sure thing I can do that. Will I be able to roll back from the latest 1.5 to the version of 1.4 rolling I’m on after testing is complete or will the config mess up?

Related to https://vyos.dev/T6080

Have installed 1.5-rolling-202403200018 in a VM as a clean install (no prior configs) to dig at this but have hit a block.

Sample config files here: https://github.com/networkupstools/nut/tree/master/conf

In T5247#166517, @SrividyaA wrote:

Now we receive this error in 1.5-rolling-202312060024 when the command is executed:

vyos@R1:~$ show interfaces system
-vbash: /opt/vyatta/bin/vyatta-show-interfaces: No such file or directory

Just wanted to add that this error is also present in V1.4 RC1