Not actual for 1.5/1.4
@mrlocke Can you re-check the 1.3?
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Apr 25 2024
Apr 24 2024
Apr 23 2024
Apr 22 2024
Any news about this issue @SrividyaA and @c-po ?
Apr 19 2024
Apr 18 2024
Test addresses have to be different
Provide the set of the commands to reproduce
@SquirePug re-check please with the latest rolling image.
@jmaslak can you check the latest rolling image?
@kroy can you re-test this case?
Apr 17 2024
Apr 16 2024
Apr 12 2024
Apr 11 2024
Can't edit this task to add a relation, but - https://vyos.dev/T6230
Propose to add names for the interfaces:
set interfaces ethernet eth2 vif-s 100 vif-c 300 name if9999
An additional found old dhcp-client issue, does not properly support interface names with length > 13
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858580
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704072
You can use the next type of configuration
set protocols bgp 4200010000 neighbor 2001:db8::2 address-family ipv6-unicast peer-group 'CUST_CR_IPV6' set protocols bgp 4200010000 parameters default no-ipv4-unicast set protocols bgp 4200010000 peer-group CUST_CR_IPV6 address-family ipv6-unicast set protocols bgp 4200010000 peer-group CUST_CR_IPV6 remote-as '65500'
But we recommend to check the result in FRR configuration.
Trying to fix it is too risky because it may stop other not-quite-valid configuration from loading and we don't know how big the impact is going to be. 1.4 doesn't have the issue, and 1.3 is in the maintenance phase.
I thought the fix was merged post-2.2.8 and that we were waiting for next upstream release, or is my understanding of the build process wrong?
https://github.com/vyos/vyos-build/blob/a9cc581827e9a0ba1646b16ed07170e4ec2ca34e/packages/keepalived/Jenkinsfile#L27
Can someone re-check it in 1.5/1.3.6?
Apr 10 2024
set policy local-route rule 101 destination '0.0.0.0/0' set policy local-route rule 101 set table 'local' set policy local-route rule 102 destination '0.0.0.0/0' set policy local-route rule 102 set table 'main' set policy local-route rule 104 destination '0.0.0.0/0' set policy local-route rule 104 set table '170'
Confirmed this is now fixed.
Sorry guys - I'm on 1.4-epa2 these days but aren't doing VRRP/Conntrack sync anymore.
Apr 9 2024
@MattK Could you re-check and close it?
@tjh Any updates?
By the way there is a new option
vyos@r4# set service conntrack-sync disable-syslog [edit] vyos@r4#
Apr 8 2024
Rechecked - The issue exists.
Apr 7 2024
Apr 6 2024
Apr 5 2024
@a.apostoliuk Recheck reconfguration, not new configuration
I do not see this issue in 1.3.6
Apr 4 2024
It is in the AWS flavor now.
1.3 equuleus https://github.com/vyos/vyos-1x/pull/3250
Apr 3 2024
Apr 2 2024
Apr 1 2024
After the fix
Mar 28 2024
We need to implement https://manpages.debian.org/testing/wide-dhcpv6-client/dhcp6c.conf.5.en.html#script like in ipv4 dhcp client