@penetal please confirm that this is resolved.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 7 2024
Resolved in my tests using above reproducer; waiting for confirmation from submitter.
While at it, whats the configured response time in nginx?
@paigeadelethompson I've noticed that issue some weeks ago too. @n.fort is already trying to fix it - so VyOS team is working on it.
Mar 6 2024
SPINE-1 BGP config(JunOS):
set protocols bgp group UNDERLAY mtu-discovery set protocols bgp group UNDERLAY export FROM-UNDERLAY set protocols bgp group UNDERLAY local-as 4200020001 set protocols bgp group UNDERLAY graceful-restart disable set protocols bgp group UNDERLAY multipath multiple-as set protocols bgp group UNDERLAY bfd-liveness-detection minimum-interval 350 set protocols bgp group UNDERLAY bfd-liveness-detection multiplier 3 set protocols bgp group UNDERLAY neighbor 10.177.77.2 peer-as 4200030001 set protocols bgp group UNDERLAY neighbor 10.177.77.10 peer-as 4200030002 set protocols bgp group OVERLAY type internal set protocols bgp group OVERLAY local-address 10.177.75.1 set protocols bgp group OVERLAY family evpn signaling set protocols bgp group OVERLAY cluster 10.216.255.255 set protocols bgp group OVERLAY peer-as 64542 set protocols bgp group OVERLAY local-as 64542 set protocols bgp group OVERLAY multipath set protocols bgp group OVERLAY neighbor 10.177.75.3 description LEAF-1 set protocols bgp group OVERLAY neighbor 10.177.75.4 set protocols bgp group OVERLAY neighbor 10.176.75.1 set protocols bgp group OVERLAY neighbor 10.176.75.2 set protocols bgp group OVERLAY neighbor 10.177.75.5 description VyOS set protocols bgp group OVERLAY neighbor 10.176.75.3 description HV205 set protocols bgp log-updown
This is working frr configuration:
No, this is not correct for my set up. Configuration commited without error but lost peering
- Peer-group UNDERLAY - eBGP(directly connected peers)
- Peer-group OVERLAY - iBGP
This will be resolved after merging the PR for T6104.
Tested in different possibilities:
There is the task for the bug with "backslashes" T5996
Yes, boot\x86\wdsnbp.com is a proper filename, and this further correctly translates to double backslash in the dhcp.conf file at /run/dhcp-server/dhcpd.conf, as I noted. Why it is so, explained for example here: https://www.linkedin.com/pulse/quit-thinking-look-matthew-topper
And with such a setting network boot works just fine.
The problem is that after each reboot the vyos configuration scripts, I guess, double the number of backslashes in the config, that further leads to doubling them in the dhcp.conf. And on, and on. This actually breaks the network boot, and manual intervention is required after each router reboot.
Is "\" really a valid path for bootfile?
The 1.3.x behaviour,
- VTI interfaces without IPsec is not created
# 1.3 set interfaces vti vti10 address '10.0.0.1/30' commit
Create the PR without smoketest. This case is not tested.
@c-po, while I don't wish to put words in the mouths of others, I believe the belief is that the interface should stay oper-down.