- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jun 9 2020
Jun 8 2020
@daniil that would work of course. You tested it manuslly that this works?
A Serial/IPMI interface would be much more suited for kernel debugging.
Jun 7 2020
This will move eth0 to eth7 - is there a config migrator? Or is it yet not used in "production"?
It will be in the next rolling (any rolling newer then vyos-1.3-rolling-202006070117-amd64.iso)
@njh you have been right that command can be quiet handy, but instead of using a logfile we query "journalctl" for the appropriate logs.
vyos@vmware:~$ show environment sensors VyOS running under hypervisor, no sensors available
Idea: do not generate empty node.def file if there is no <properties> statement.
Jun 6 2020
In T2551#66297, @dsummers wrote:@c-po Woops, as of vyos-1.3-rolling-202006052325 now the problem has switched.
Now the "prefix ::/56 infinity" stanza is in the configuration file, but now the other parameters are not being put in.
Jun 5 2020
Fixed in the rolling release from 20200606xx
This could raise potential new bugs if a firmware file was missed out for whatever reason. Please open a new Task if this happened to you. Running it in @kroy's lab showed no problems so far.
Jun 4 2020
@jjakob any idea?
I do not like this behavior as the config states the interface is "not disabled" but from an OS point of view it is - this is inconsistent and thus simply wrong.
Main reason would be I guess this error:
Jun 4 16:39:55 LR1 openvpn-vtun1[21166]: Could not determine IPv4/IPv6 protocol Jun 4 16:39:55 LR1 openvpn-vtun1[21166]: SIGUSR1[soft,init_instance] received, process restarting