- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Apr 27 2021
sa_data wrong format
vyos@r6-roll:~$ show vpn ipsec sa [[b'peer-203.0.113.2-tunnel-vti', 'up', '4m33s', '168B/168B', '2/2', '203.0.113.2', 'N/A', 'AES_CBC_256/HMAC_SHA1_96/MODP_1024'], ['peer-192.0.2.2-tunnel-vti', 'down', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A']] Connection State Uptime Bytes In/Out Packets In/Out Remote address Remote ID Proposal ------------------------------ ------- -------- -------------- ---------------- ---------------- ----------- ---------------------------------- b'peer-203.0.113.2-tunnel-vti' up 4m33s 168B/168B 2/2 203.0.113.2 N/A AES_CBC_256/HMAC_SHA1_96/MODP_1024 peer-192.0.2.2-tunnel-vti down N/A N/A N/A N/A N/A N/A vyos@r6-roll:~$
Apr 26 2021
@Yuanandyuan Can you reproduce it with vyos cli? Or it raw podman commands?
Apr 19 2021
Workaround set raw option "config /path/to/config/file"
Apr 16 2021
@jestabro Cool!!!
Apr 15 2021
Apr 14 2021
Apr 13 2021
- A̶d̶d̶ ̶c̶h̶e̶c̶k̶s̶ ̶t̶o̶ ̶p̶r̶e̶v̶e̶n̶t̶ ̶s̶e̶t̶ ̶i̶p̶ ̶a̶d̶d̶r̶e̶s̶s̶ ̶f̶o̶r̶ ̶c̶o̶n̶t̶a̶i̶n̶e̶r̶ ̶o̶u̶t̶ ̶o̶f̶ ̶r̶a̶n̶g̶e̶ ̶"̶p̶r̶e̶f̶i̶x̶" done
set container name alp02 image 'alpine' set container name alp02 network NET01 address '192.0.2.1' set container network NET01 ipv4-prefix '10.0.0.0/24
error
time="2021-04-14T00:52:03+03:00" level=error msg="Error adding network: failed to allocate all requested IPs: 192.0.2.1" time="2021-04-14T00:52:03+03:00" level=error msg="Error while adding pod to CNI network \"NET01\": failed to allocate all requested IPs: 192.0.2.1" Error: unable to start container "60f20a2b517b4f828bef5683cd8a20504aa984648a0911f7f8df5c1a064d2625": error configuring network namespace for container 60f20a2b517b4f828bef5683cd8a20504aa984648a0911f7f8df5c1a064d2625: failed to allocate all requested IPs: 192.0.2.1
Apr 12 2021
The reason these validations https://github.com/vyos/vyos-1x/blob/aca3254d96d01cc37c9e15e02e500a36f3708959/interface-definitions/vrrp.xml#L220-L224
There is no such problem in version 1.4.
Apr 9 2021
@olofl which version?
Apr 8 2021
If you add neighbor/commit and after that commit adding "set protocols bgp parameters default no-ipv4-unicast" it can not be accepted. Because neighbor was added before this command.
Re-create neighbor and commit. And check again.
Apr 7 2021
You can't/don't need to set local-as for neighbor [ if neighbor local as == your global asn ]
Can you send a code error?
Apr 5 2021
Fixed. 1.2.7, VyOS 1.3.0-rc3, VyOS 1.4-rolling-202104041918
Apr 4 2021
The same with "policy" /usr/libexec/vyos/tests/config/dialup-router-medium-vpn
To reproduce it add firewall and attach it to interface
It is a priority for configurations
When the system load, the firewall should have configuration, and after configuration is applied to the interface.
So I think we can't delete it in one commit, it tried to delete the firewall before detaching the firewall from the interface.
Apr 3 2021
We can do some workaround for that level,
It seems that "call" doesn't react to env.
'VYATTA_EDIT_LEVEL': '/system/login'
Apr 2 2021
Apr 1 2021
Chown for saved configuration file should be frr:frr
Mar 31 2021
Expect
vyos@r5-roll# set protocols ospf redistribute isis Possible completions: metric OSPF default metric metric-type OSPF metric type for default routes (default: 2) route-map Route map reference
Mar 30 2021
@dtoux show ipv6 route vrf foo
To reproduce, on clean install 1.3.-rc3
set interfaces ethernet eth1 address '2620:18:6000:aa10::2/64' set interfaces ethernet eth1 vrf 'foo' set protocols vrf foo static route6 ::/0 next-hop 2620:18:6000:aa10::1 set vrf name foo table '1050'
@dtoux vtysh -c "show run"
Also, it doesn't show a directly connected ipv6 route.
The route present in the frr
! vrf foo ipv6 route ::/0 2620:18:6000:aa10::1 exit-vrf !
Mar 29 2021
Mar 28 2021
Possible reason "> 2" in description "Ruby > 2.3"
vyos@r5:~$ echo "Package versions:"; dpkg -l | grep ruby-curse -A 2 Package versions: ii ruby-curses 1.2.4-1+b1 amd64 curses binding for Ruby ii ruby-did-you-mean 1.2.1-1 all smart error messages for Ruby > 2.3
Mar 26 2021
@trystan Can you re-check it ?
Do we need "awscli" for it?
Fixed VyOS 1.4-rolling-202103251004
Mar 25 2021
It was a broken image.