- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Dec 4 2022
Dec 3 2022
Dec 2 2022
We can do it the same way
vyos@r1# set service snmp oid-enable Possible completions: route-table Enable routing table OIDs (ipCidrRouteTable inetCidrRouteTable)
so by default they should be disabled
Verify if you are trying to add a new vethX to exists pair (veth12 link to veth0 should be RaiseConfigerror)
set interfaces virtual-ethernet veth0 peer-name 'veth1' set interfaces virtual-ethernet veth1 peer-name 'veth0' set interfaces virtual-ethernet veth12 peer-name 'veth0' commit
commit
vyos@r1# commit
[ interfaces virtual-ethernet veth12 ]
{'ifname': 'veth12',
'other_interfaces': {'veth0': {'peer_name': 'veth1'},
'veth1': {'peer_name': 'veth0'},
'veth12': {'peer_name': 'veth0'}},
'peer_name': 'veth0'}
VyOS had an issue completing a command.Dec 1 2022
Nov 30 2022
No, just try the latest rolling
There were a lot of changes/ bug fixed: etc since 2021
Outdated image 2021
Nov 28 2022
@ordex Could you check the latest rolling release? Fancontrol should be there.
Nov 26 2022
It will be enough next config to reproduce:
set protocols mpls interface 'eth1' commit set protocols bgp system-as 65001 commit
Nov 25 2022
Verify check, PR https://github.com/vyos/vyos-1x/pull/1678
It must be RaiseConfigError if we delete one of the peers which related on the other veth interface
set interfaces virtual-ethernet veth0 peer-name 'veth1' set interfaces virtual-ethernet veth1 peer-name 'veth0'
Nov 24 2022
Fixed in T4660
Nov 23 2022
Nov 22 2022
In T4823#138040, @chesskuo wrote:Hello sir,
In vyos-1.4-rolling-202211220318-amd64.iso, the broken syntax was fixed, but I notice a wired behavior on connection.<conn>.remote.id.
The default value on swanctl.conf will be <name> when I don't set site-to-site -> peer <name> -> authentication -> remote-id.
Nov 21 2022
Could you provide config from several items?
How many nodes do we need to reproduce it?
Nov 20 2022
ipsec site-to-site peer <name> - it is just a connection name and is not related to the IP address
I'll take a look at TS
vyos@r14# set policy route-map FOO rule 100 action permit [edit] vyos@r14# set policy route-map FOO rule 50 action 'deny' [edit] vyos@r14# set policy route-map FOO rule 50 continue '100' [edit] vyos@r14# [edit] vyos@r14# commit [ policy ] rule 50 "continue" cannot be used with action deny!
Nov 19 2022
Thanks
Don’t think that there should be a migration
As new keys were added several days ago.
Nov 18 2022
In T973#137840, @elico wrote:@Viacheslav I want to test this, what should be done?
@Arc771 Thanks, Could you check it in the next rolling release after 20221118?
@DerEnderKeks Could you check it in the next rolling release after 20221118?
set policy route-map MAP-ISP1-AS1001-EXPORT rule 50 action 'deny' set policy route-map MAP-ISP1-AS1001-EXPORT rule 50 continue '100'
Nov 17 2022
I guess it was implemented in the T4750
Should be easy to fix
Nov 14 2022
PR https://github.com/vyos/vyos-1x/pull/1657
vyos@r14:~$ show vpn ipsec connections Connection State Type Remote address Local TS Remote TS Proposal ----------------- ----------- ------ ---------------- -------------- ----------- --------------------------------------- OFFICE-B established IKEv1 192.0.2.2 - - AES_CBC/256/HMAC_SHA2_256_128/MODP_1024 OFFICE-B-tunnel-0 up IPsec 192.0.2.2 192.168.0.0/24 10.0.0.0/21 AES_CBC/256/HMAC_SHA2_256_128/MODP_1024 OFFICE-B-tunnel-1 down IPsec 192.0.2.2 192.168.1.0/24 10.0.0.0/21 - OFFICE-B-tunnel-2 down IPsec 192.0.2.2 192.168.2.0/24 10.0.0.0/21 - OFFICE-C down IKEv1 192.0.2.2 - - - OFFICE-C-tunnel-0 down IPsec 192.0.2.2 192.168.5.0/24 10.0.0.0/21 - vyos@r14:~$