-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ipv6 static route ignored state, except if address interface configured in FRR ( interface renamed in between) #2626
Comments
Hello, |
@jfloret I will look at this today and get back to you |
@jfloret, still working on this, I will post updates as soon as the issue is identified |
Hi, |
When "iproute2" command applied, did zebra know the interface with its ipv6 address? Can you show the logs with the following flags set?
also, the output of:
|
Hello @Jafaral , sorry for the delay. In fact, I missed that before but it seems that the bug occurs when an interface is renamed.
Zebra sees the new ipv6 address and the subsequent rename, but does not seem to make the relation between the address and the interface. Please find attached the logs with 'debug zebra kernel' and 'debug zebra rib detail'. dut-vm# show interface ntfp2 |
@jfloret sorry I missed you reply as well. I will continue working on this issue and let you know |
Hi, The issue is not reproducible on latest 5.1. Please find the logs as given below. root@dev:~/frr_new# ifconfig ens160 Link encap:Ethernet HWaddr 00:50:56:96:44:81 lo Link encap:Local Loopback root@dev:~/frr_new# vtysh Hello, this is FRRouting (version 5.1-dev-MyOwnFRRVersion-g46a9c3a-dirty). This is a git build of frr-5.1-dev-390-g46a9c3a-dirty dev# show version configured with: ens160 Link encap:Ethernet HWaddr 00:50:56:96:44:81 ens192 Link encap:Ethernet HWaddr 00:50:56:96:da:b0 lo Link encap:Local Loopback root@dev:~/frr_new# vtysh Hello, this is FRRouting (version 5.1-dev-MyOwnFRRVersion-g46a9c3a-dirty). This is a git build of frr-5.1-dev-390-g46a9c3a-dirty dev# configure terminal Current configuration: C>* 2001::/64 is directly connected, ens192, 00:00:57 ens160 Link encap:Ethernet HWaddr 00:50:56:96:44:81 ens192 Link encap:Ethernet HWaddr 00:50:56:96:da:b0 lo Link encap:Local Loopback root@dev: ens160 Link encap:Ethernet HWaddr 00:50:56:96:44:81 ens888 Link encap:Ethernet HWaddr 00:50:56:96:da:b0 lo Link encap:Local Loopback root@dev: ens160 Link encap:Ethernet HWaddr 00:50:56:96:44:81 ens888 Link encap:Ethernet HWaddr 00:50:56:96:da:b0 lo Link encap:Local Loopback root@dev:~/frr_new# vtysh Hello, this is FRRouting (version 5.1-dev-MyOwnFRRVersion-g46a9c3a-dirty). This is a git build of frr-5.1-dev-390-g46a9c3a-dirty dev# show running-config Current configuration: C>* 2001::/64 is directly connected, ens888, 00:00:14 |
Issue is reproduced by doing the renaming procedure from jfloret. So when the interface is going back, it looks like its contexts have not been refreshed. |
this ticket : #2393 |
not related to 2393 ( despite it could help). actually, what happens is that IP messages are ignored on zebra side.
|
#2943 may help |
I also observed that if I do the link flap on interface in kernel, the IPv6 address is getting deleted in FRR . I had to reconfigure the IPv6 address on the interface to get it programmed back to kernel. Hopefully it is the same issue |
initial state
iproute2 has configured an interface ntfp2 with fd00:125::1/64.
interface is up.
and the neighboring discovery has been done ( ping with fd00:125::2 has been done).
zebra has started, and I want to create a static route
result is that route is inactive
extract of zebra debug rib detailed
flush address of ntfp2, and create it from zebra.
remark
If I apply the same initial step with IPv4, it works.
so that is why I think there is an issue with IPv6 static configuration.
this has been observed in 5.0 branch
The text was updated successfully, but these errors were encountered: