User Details
- User Since
- May 11 2021, 12:36 PM (189 w, 5 d)
Nov 21 2024
@sarthurdev i think it can be good idea to those case , what do you think ? @dmbaturin @jestabro
Nov 1 2024
Oct 23 2024
Oct 5 2024
tested with the fixed done by @natali-rs1985 : , works with ports as well :
Sep 30 2024
Sep 16 2024
we've added this new feature called Server bridge , it's available in 1.5 and backported 1.4:
merge and tested in both version .
Sep 12 2024
Aug 29 2024
Aug 22 2024
Aug 20 2024
Aug 19 2024
I think it has a interesting option `ethtool -K ethX ntuple [on|offwhich is interesting has the knowledge , we can keep it as a part the main task .
this task is already created, it involved many offload/NIC tunning which are described on this :
Aug 9 2024
Documentation :
https://github.com/vyos/vyos-documentation/pull/1521
Aug 8 2024
new structure was added :
Jul 31 2024
Jul 25 2024
tested and resolved : VyOS 1.5-rolling-202407251105
tested and resolved, we've added this change in our cli to fix this deprecate option in opnvpn :
[edit] vyos@vyos-ser-win# set interfaces openvpn vtun10 server topology Possible completions: subnet Subnet topology (recommended) (default) point-to-point Point-to-point topology net30 net30 topology (deprecated)
Jul 13 2024
I've tested in the new version , the problem with default net30 , it is already there .however , when the new version started show a warning message that migrating from net30 to subnet because is going to be deprecated :
Jul 5 2024
Jul 4 2024
task related : https://vyos.dev/T4025
Jul 3 2024
I've checked this bug , it's still present the vesion 1.4./1.5 and the 1.3.x , this problem is related to the update of the new version (openvpn) where the syntax to create a tunnel tap (layer2) is changed , this command allow to transport frame and it's needed when you want to bridge a vtun :
Jul 1 2024
I've created the FRR bug report :
Jun 27 2024
confirm that it works as well , spoke to spoke connection adding authentication. :
@volodymyr.huti I've checked a hub & spoke with Cisco nhrp and opennhrp , it works ,although, it has some issues related to establish spoke to spoke tunnel or when removing the password , here is my environment (it was merged for the master branch, not backport to stable) .
Jun 25 2024
Jun 13 2024
here we can add some prevention to raise error, to avoid that someone uses in EBGP a profile to IBGP, because, the problem is under FRR which syntax brakes the frr-cli.
I've tested it, the problem here is because you change a wrong local role , in your configuration is a rs-client ( IBGP relationship) but when you move to rs-server ( only works with EBGP , this attribute reflect EBGP routes to bgp router clients ) , so, that it's reason why you are not allowed to change :
VyOS :
vyos@vyos# run show configuration commands | match bgp set protocols bgp neighbor 10.88.88.255 address-family ipv4-unicast set protocols bgp neighbor 10.88.88.255 peer-group 'FAST' set protocols bgp peer-group FAST capability dynamic set protocols bgp peer-group FAST graceful-restart 'enable' set protocols bgp peer-group FAST local-role rs-client set protocols bgp peer-group FAST password 'F@st123!' set protocols bgp peer-group FAST remote-as '211186' set protocols bgp peer-group FAST update-source '10.88.88.2' set protocols bgp system-as '211186' [edit] vyos@vyos# delete protocols bgp peer-group FAST local-role rs-client [edit] vyos@vyos# commit [edit]
Jun 12 2024
documentation : https://github.com/vyos/vyos-documentation/pull/1479
Jun 8 2024
please , Could you share configuration on how to replicate it ? it's also here the guideline about report a bug :
Jun 5 2024
Jun 3 2024
please, read the guidelines that I shared, the point here if it works with our system , is not error in cli structure o functionality you should open a forum topic or support case (in case you have an active subscription), before opening a task here that is not clear.(without configuration ,debug attached or packet capture)
please , read the guidelines on this post . it doesn't see a bug if not a support task:
May 31 2024
May 29 2024
@mersl thanks for confirm.
we've added this ability to configure the topology on isis :
agree ,it's more a feature than a bug : PR https://github.com/vyos/vyos-1x/pull/3537
the problem here is that MT options is enable by default when the RIB has ipv4, if not not-MT is enable by default on IPv4 .So, you need to add additional topologies (ipv6-unicast , ipv6-multicast,etc)
May 28 2024
May 27 2024
tested new cli structure, it combine the new mach-group and old syntax :
May 12 2024
May 11 2024
I've tested and now is working correctly :
add documentation : https://github.com/vyos/vyos-documentation/pull/1444
May 4 2024
May 3 2024
Apr 20 2024
Apr 19 2024
Apr 2 2024
this new command was merge in order to solved this problem :
vyos@vrf-test:~$ show configuration commands | match disable set protocols bgp parameters disable-ebgp-connected-route-check
Mar 29 2024
Mar 21 2024
Feb 22 2024
Jan 31 2024
it think that we can use also something similar to what we use ocserv to generate ssl certificates:
Jan 30 2024
it makes seens , agree with add a Config Error to do not allow both options simultaneously ,.
Jan 29 2024
as I mentioned , it was added in 9.1 as default behavior :