You can create /use your own images
vyos@r4:~$ generate container image foo path Possible completions: <filename> Path to Dockerfile
You can create /use your own images
vyos@r4:~$ generate container image foo path Possible completions: <filename> Path to Dockerfile
Backport to 1.3 is not worth the trouble since the issue is low-impact.
1.4 is very reasonably clean from that Vyatta cruft, as much as it's possible. We'll create tasks for specific dead code discoveries in the future as needed.
Blowfish support was removed in 1.4, so its key size is no longer an issue.
Now that the subtasks are closed and none of the old validators exist in the image, it's time to call this meta-task done.
The implementation was changed to chrony.
https://forum.vyos.io/t/ospf-not-forming-neigborship-after-upgrading-from-1-3-3-to-1-4/14187 may also be related...
@matthewr Thanks for confirming!
Closing it as resolved now. Feel free to reopen or create a new one if this bug remains again.
Just in case it helps, after a migration from 1.3 to 1.4.0-epa2, the migrated config ends up as:-
Is this related to the long commit and boot times when one have more than a handful routes or firewall rules as described in https://vyos.dev/T5388 ?
In T6116#179637, @sarthurdev wrote:Interfaces aren't added on boot because mac address is locally administered: https://github.com/vyos/vyos-1x/blob/current/src/helpers/vyos-interface-rescan.py#L60
Raised this issue before with @jestabro as also seen with VyOS as VM.
Can we let local-route support group options both in destination and source ?
set policy local-route rule 10 destination Possible completions: + address IPv4 address or prefix port Port number used by connection
Interfaces aren't added on boot because mac address is locally administered: https://github.com/vyos/vyos-1x/blob/current/src/helpers/vyos-interface-rescan.py#L60
There are no old-style CLI definitions anymore, and thus no default: tags either, so this shouldn't be an issue anymore.
Pretty sure this is the offending migrator. I briefly discussed this with @c-po
Just wanted to follow up: I have now tested this and can confirm that everything is working as expected.
PR for 1.4 https://github.com/vyos/vyos-1x/pull/3118
Working on 1.4-rolling. Thanks for the awesome work.
Just to observe that this is not added on every occasion - see for example my update today in https://vyos.dev/T6076 where it was not added when the migration succeeded.
much appreciated, thank you!
could you provide us with a documentational like answer how you would implement the requested thing?
We have not yet found a good solution/idea internally and wanted to loop you in on this.
While at it, whats the configured response time in nginx?
This will be resolved after merging the PR for T6104.
Create the PR without smoketest. This case is not tested.
The regex should be [-_a-zA-Z0-9.\s]+ instead of [-_a-zA-Z0-9\s]+