keepalived: Generate the proper route for the interface IP configured…#605
keepalived: Generate the proper route for the interface IP configured…#605andrewhit wants to merge 1 commit intoiqiyi:develfrom
Conversation
… within
static_ipaddress{}.
- With this patch, we can get the below two expected result with the below
configuration example.
static_ipaddress {
dpvs-wan-ip/30 dev eth1
}
a) "dpvs-wan-ip" related route is generated.
inet dpvs-wan-ip/30 scope global eth1
valid_lft forever preferred_lft forever
...
b) "dpvs-wan-ip" is configured on the related interface for arp request.
inet dpvs-wan-network-ip/30 via 0.0.0.0 src dpvs-wan-ip dev eth1 mtu 1500 tos 0 scope link metric 0 proto auto
...
|
Test failed for the keepalived config file. logs: problems:
|
|
I just tested the config within static_ipaddress{} without the config within vrrp_instance{}, for vrrp_instance{} is not used in our deployment. |
|
I tested the patch without vrrp. The first problem still exists. Keepalived process exit abnormally immediately after startup. |
Have you tried use eth1 instead of dpdk1? Here I do not use the name, dpdk1 or dpdk0, but eth1 or eth0. And for kni interface, we use eth1_kni or eth0_kni for mlx nic. static_ipaddress { |
|
The dpdk interface name doesn't matter. I followed the flow of the static address parser: |
The reason is that when dpvs is started, we need to use And the below lines are observed above. |
|
Please test the case where ifnames of dpvs and kni are different. |
… within
static_ipaddress{}.
configuration example.
static_ipaddress {
/30 dev eth1
}
a) "dpvs-wan-ip" related route is generated.
inet /30 scope global eth1
valid_lft forever preferred_lft forever
...
b) "dpvs-wan-ip" is configured on the related interface for arp request.
inet /32 via 0.0.0.0 src dev eth1 mtu 1500 tos 0 scope link metric 0 proto auto
...