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
May 23 2021
May 22 2021
May 21 2021
May 20 2021
Function get_interface_config itself not added. Needs to add it for 1.3.
[email protected]:~$ 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) [email protected]:~$
Fixed VyOS 1.4-rolling-202105192127
set protocols ospfv3 area 23 area-type stub set protocols ospfv3 area 25 area-type stub no-summary
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
As I understand it a part of zebra, not specified to any protocol.
Maybe I'm wrong and we don't need it.
May 18 2021
This is still reproducible in the FRR master branch, so I've filed an issue: https://github.com/FRRouting/frr/issues/8695
Tested on 1.4-rolling-202105170417 works correct. Propose to backport this to 1.3
There are two separate issues in this task: quoting of hw-id values (resolved in Sagitta/Equuleus); re-ordering of interfaces with respect to hw-id (Open).
@rizkidtn I don't understand exactly what wrong with the community?
Customers sent you routes, with blackhole community, on the router you mark match this community and set next hop "blackhole" IP address.
May 17 2021
I think I found a way to reproduce it:
- rename an interface that was previously included in ospfv3 configuration and then remove it in the same commit from ospfv3 in the same commit.
- get an error that interface is not found. I think that at this stage the configuration is applied only partially
- after that error configuration in frr and vyos goes out of sync and never unsynchronized unless forced (or by lucky accident :-)
show conf com | match ospfv3
Copy configuration.
Delete protocols ospfv3
commit
re-add ospf config.
Hmm, I still have it in my running-config. Is there a way to force config regeneration?
The "Time exceeded" likely means that message is sent to a black hole. There are two bfd sessions running through the same tunnel - one for OSPF and the other for OSPFv3. Timeout settings are the same and the first one is established instantly and is running happily. The OSPFv3 one is not so much:
Time Exceeded (3)
I can't reproduce it VyOS 1.3-rolling-202105011026
BFDd amybe creating those addresses automatically. In theory, it doesn't matter what they are as long as both ends have a way of learning them. I'm not sure if this is a general issue or an issue only with wireguard but right now bfd doesn't work with OSPFv3 over wireguard.
As WireGuard has bo MAC address a EUI64 link-local address is calculated artificially https://github.com/vyos/vyos-1x/blob/current/python/vyos/ifconfig/wireguard.py#L161
BTW, it appears ths fe80::... addresses used in bfd dialogue do not belong to any of the actual interfaces. It could be by design but this si something I discovered when trying to troubleshoot the session. This could also be the reason for mismatch between session ends if the other side does not know the peer address.
Attaching packet captures from both ends filered with bfd && ipv6.addr == fe80::/64 rule
I ran a packet capture on the session and It appears had been an issue with firewall settings on the provider site. It just happened that we hit a similar issue with two providers and VyOS was the common denominator but It appears to be red herring. Feel free to close.
May 15 2021
It will be enough to add a quote here?
"\`"
