That could als help on debugging like adding vyos-config-debug option or as I like on my hosts, vga=773 when debugging and checking for config migration issues.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
May 10 2020
May 10 2020
In regards to 1) I do not remember why I added it there as FRR seems to accept that kind of routes - but its actually a warning only no real error.
The inconsitency of the naming is b/c the default routing table naming is inconsitent, too - thus it makes it consitent again :)
May 6 2020
May 6 2020
New commands added:
May 4 2020
May 4 2020
c-po added a comment to T951: command 'isolate-stations true/false' does not make any changes in the hostapd.conf.
Wireless AP completely rewritten. If issue reappears please reopen or file a new bug.
Forum says issue is fixed. Also WWAN underwent a major rewrite - should be all good now.
@MikeLupe Are you using a custom dyndns provider/script? It ifs compatible with the dyndns2 "API" this is already possible using the "custom" dns dynamic service.
This has been completely rewritte in Python/XML. Please reopen if this is still a problem - and if so what do you think should be the "real" rendered configuration.
I suggest adding a "validate" function to vyos.validate. We should determine the hypervisor used and if a setting is allowed on that hypervisor or not. Thus we can throw an appropriate erorr message by raise ConfigError() in the Python file changing the interface setting. This would be the cleanest way then the "false" setting never reaches the configuration backend at all.
May 3 2020
May 3 2020
Sure it can (was in the initial ifconfig.py rewrite IIRC)
c-po closed T2421: Update WireGuard to Debian release 1.0.20200429-2_bpo10+1, a subtask of T2420: Update Linux Kernel to v4.19.120, as Resolved.
May 2 2020
May 2 2020
May 1 2020
May 1 2020
vyos@vyos:~$ monitor traceroute vrf red 1.1.1.1
c-po changed the status of T2411: op-mode: make "monitor traceroute" VRF aware from Open to In progress.
The following adds support into the XML generation but I have no clue about vyatta-cfg how those files get executed.
Presumably a val_help line in the op-mode node.def, too
c-po added a comment to T2129: XML schema: tagNode not allowed on first level in new XML op-mode definition.
Tested good - migrating traceroute now
c-po changed the status of T2129: XML schema: tagNode not allowed on first level in new XML op-mode definition from Open to Blocked.
Apr 30 2020
Apr 30 2020
Apr 29 2020
Apr 29 2020
c-po changed the status of T2399: op-mode "dhcp client leases" does not return leases from Open to In progress.
c-po updated the task description for T2398: op-mode "dhcp client leases interface" completion helper misses interfaces.
Resolved with T2393
c-po closed T2394: dhcpv6 client does not start, a subtask of T2393: dhclient: migrate from SysVinit to systemd, as Resolved.
Apr 28 2020
Apr 28 2020
c-po renamed T2394: dhcpv6 client does not start from DHCPv6 broken to dhcpv6 client does not start.
c-po changed the status of T2394: dhcpv6 client does not start, a subtask of T2393: dhclient: migrate from SysVinit to systemd, from Open to In progress.
c-po changed the status of T2393: dhclient: migrate from SysVinit to systemd from Open to In progress.
c-po moved T2131: Improve syslog remote host CLI definition from Needs Triage to Finished on the VyOS 1.2 Crux (VyOS 1.2.6) board.
c-po added a project to T2131: Improve syslog remote host CLI definition: VyOS 1.2 Crux (VyOS 1.2.6).
c-po moved T2385: salt-minion: improve completion helpers from Needs Triage to Finished on the VyOS 1.2 Crux (VyOS 1.2.6) board.
Apr 27 2020
Apr 27 2020
Nice catch - I was not aware of that show command.
Nope. Before I‘ve invented vyos.ifconfig it was actually based on pyroute2. The problem with pyroute2 was that it lacked required functionality for VyOS which let me to developing our own lib.
Apr 26 2020
Apr 26 2020
@elbandi how should this approach fix the error on image upgrade?
@elbandi sure that I used as workaround.
vyos@vyos:~$ reboot cancel Reboot or poweroff is not scheduled
c-po changed Why the issue appeared? from none to design-mistake on T2010: Reboot at reports wrong time or missing timezone.
c-po closed T2386: salt: upgrade to 2019.2 packages, a subtask of T2382: salt-minion: Throws KeyError on commit, as Resolved.
c-po closed T2385: salt-minion: improve completion helpers, a subtask of T2382: salt-minion: Throws KeyError on commit, as Resolved.
c-po closed T2384: salt-minion: log to syslog and remove custom logging option, a subtask of T2382: salt-minion: Throws KeyError on commit, as Resolved.
- rename hash_type -> hash
- rename mine_interval -> interval
c-po changed the status of T2384: salt-minion: log to syslog and remove custom logging option, a subtask of T2382: salt-minion: Throws KeyError on commit, from Open to In progress.
c-po changed the status of T2384: salt-minion: log to syslog and remove custom logging option from Open to In progress.
c-po changed Why the issue appeared? from none to implementation-mistake on T2382: salt-minion: Throws KeyError on commit.