PR https://github.com/vyos/vyos-1x/pull/1601
set service ssh hostkey-algorithm 'sk-ssh-ed25519@openssh.com' set service ssh hostkey-algorithm 'ssh-rsa'
PR https://github.com/vyos/vyos-1x/pull/1601
set service ssh hostkey-algorithm 'sk-ssh-ed25519@openssh.com' set service ssh hostkey-algorithm 'ssh-rsa'
Added more bgpd/ospfd events to the log. The VRF Id seem to be correct. But the events look curious. After session start the interface is first created in vrf default (vrf default, id:0) followed by bgpd/ospfd events, then accel-ppp process moves it to destination vrf (vrf client, id:5) which is follwed by the bgpd/ospfd errors.
Finally, with more or less than 5000 sessions bgpd accidentally becomes unresponsive and utilizes 200% cpu (8 cores are used on VM). Accel-pppd process having all network destinations unreachable also goes unresponsive a bit later.
After that we have to reboot.
@CuBiC3D There is a comment of the commit https://github.com/vyos/vyos-1x/commit/373227e717fac82af5ea8d71e611a3df1c59054e
I am finding out, it seems OSPF SR doesn't work properly :(
Here is ISIS segment routing working:
Basically,
all commercial hooks need to be implemented
I have been thinking about this over the weekend and looked into your failover implementation, there's nothing wrong with it and should serve most peoples needs. That said I am not too good with python so it was more straight forward to start from scratch.
I confirm this is still an issue in 1.4-rolling-202207250217 trying to download 1.4-rolling-202210150526:
@SrividyaA
The documentation at https://docs.vyos.io/en/latest/configuration/firewall/zone.html currently contains the following regarding local-zone:
Why does the image has to be added manually and can not be pulled from the registry if not locally available?
@adaker
Could you describe the check/test procedure, how to test that all works as you expected?
Ah, yea that is true.
They are enabled by default.
I mean Linux man https://man7.org/linux/man-pages/man5/sshd_config.5.html
HostKeyAlgorithms
Specifies the host key signature algorithms that the server
offers. The default for this option is:What do you mean by "enable by default"?
The issue is that, right now, we are unable to add these kind of ssh keys because the cli won't let you define the type.
Also, it should be enabled by default (at least in ssh documentation)
Could you check it?
My fault. Sorry.
We already have task T4720
PR https://github.com/vyos/vyos-1x/pull/1596
vyos@r14:~$ show vpn ipsec sa
Connection State Uptime Bytes In/Out Packets In/Out Remote address Remote ID Proposal
----------------- ------- -------- -------------- ---------------- ---------------- ----------- ---------------------------------------
OFFICE-B-tunnel-0 up 4s 0B/0B 0/0 192.0.2.2 192.0.2.2 AES_CBC_256/HMAC_SHA2_256_128/MODP_1024
vyos@r14:~$
vyos@r14:~$
vyos@r14:~$ reset vpn ipsec-peer OFFICE-B
closing CHILD_SA OFFICE-B-tunnel-0{16} with SPIs cc364877_i (0 bytes) c521f540_o (0 bytes) and TS 192.168.0.0/24 === 10.0.0.0/21
CHILD_SA {16} closed successfully
generating QUICK_MODE request 1449430238 [ HASH SA No KE ID ID ]
sending packet: from 192.0.2.1[500] to 192.0.2.2[500] (332 bytes)
received packet: from 192.0.2.2[500] to 192.0.2.1[500] (332 bytes)
parsed QUICK_MODE response 1449430238 [ HASH SA No KE ID ID ]
selected proposal: ESP:AES_CBC_256/HMAC_SHA2_256_128/MODP_1024/NO_EXT_SEQ
CHILD_SA OFFICE-B-tunnel-0{17} established with SPIs cd451e27_i cfb63c3c_o and TS 192.168.0.0/24 === 10.0.0.0/21
generating QUICK_MODE request 1449430238 [ HASH ]
sending packet: from 192.0.2.1[500] to 192.0.2.2[500] (76 bytes)
connection 'OFFICE-B-tunnel-0' established successfully
Peer reset result: success
vyos@r14:~$Put in hopefully the last PR for this here, https://github.com/vyos/vyos-1x/pull/1595
I can't reproduce this bug with the latest rolling
vyos@r14# run show conf com | match bgp set protocols bgp address-family ipv4-unicast redistribute connected set protocols bgp neighbor eth1 interface remote-as '65001' set protocols bgp neighbor eth1 interface v6only peer-group 'SPING' set protocols bgp peer-group SPING address-family ipv4-unicast set protocols bgp peer-group SPING address-family ipv6-unicast set protocols bgp peer-group SPING capability extended-nexthop set protocols bgp peer-group SPING password 'foo' set protocols bgp system-as '65001'
@ernstjo Can you reproduce it again?