cpo@cr01-vyos:~$ show hardware storage Possible completions: nvme Show NVMe device information scsi Show SCSI device information smart Show S.M.A.R.T. device information
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
May 23 2021
May 22 2021
@fernando, this was something I was looking into adding but it'll be in 1.4 One day.....I hope soonish....maybe in a few months.
May 21 2021
I can confirm that beheivor , settings on FRR :
Before that configuration , we should add the mpls settings in our cli-vyos , it is an example:
I had a go at implementing this myself. First time ever for vyos development, using git or even python. Please be gentle!
https://github.com/vyos/vyos-1x/pull/851
May 20 2021
Function get_interface_config itself not added. Needs to add it for 1.3.
vyos@r4-1.3:~$ show int
Traceback (most recent call last):
File "/usr/libexec/vyos/op_mode/show_interfaces.py", line 26, in <module>
from vyos.ifconfig import Section
File "/usr/lib/python3/dist-packages/vyos/ifconfig/__init__.py", line 18, in <module>
from vyos.ifconfig.interface import Interface
File "/usr/lib/python3/dist-packages/vyos/ifconfig/interface.py", line 39, in <module>
from vyos.util import get_interface_config
ImportError: cannot import name 'get_interface_config' from 'vyos.util' (/usr/lib/python3/dist-packages/vyos/util.py)
vyos@r4-1.3:~$Fixed VyOS 1.4-rolling-202105192127
set protocols ospfv3 area 23 area-type stub set protocols ospfv3 area 25 area-type stub no-summary
It seems other commands like save, copy which depend on scp and tftp are also broken.
@olofl Can you re-check it? Or can we close it?
ddclient does currently not release anymore, see https://github.com/ddclient/ddclient/issues/302 , some of the integrations are already outdated in the current release like cloudflare which does not support API tokens - only the unprotected global key which grants access to everything.
May 19 2021
I just want to add that my ISP is dropping dual stack in next few months and at the end of 2021 all users will only have IPV6 networking capabilities.
For thoose who still require IPV4 traffic it will be "tunneled" via MAP-T.
As I understand it a part of zebra, not specified to any protocol.
Maybe I'm wrong and we don't need it.
Why move the protocol specific route map to a new CLI node? This makes no sense to me.
A similar problem, only for ipv4 https://phabricator.vyos.net/T1053
As we can see ipv6 address before normalization without prefix
DEBUG: 2001:db8::191 before normalize
https://github.com/vyos/vyatta-cfg-system/blob/165e56e88763c40f13e6ef77f5df1c888fdfb899/scripts/vyatta-address#L38