Skip to content

Conversation

@gerhardqux
Copy link

Having multiple NICs in the same segment that are going to be bonded
is a common scenario in modern datacenters. The kernel should not
respond to arp requests for ip addresses that are not for the
specific NIC it arrives on.

This patch prevents dhclient from dropping its ip address while
renewing its dhcp lease. Closes #237

@gerhardqux gerhardqux force-pushed the arp-flux branch 2 times, most recently from 99deb6f to c29cb46 Compare April 20, 2015 13:50
@cedlecomte
Copy link
Member

We didn't face the problem yet but we have the same configuration with multiple interface on the same medium. But we locked dhcp on one interface during the installation with a /etc/ethers file. Maybe the problem appear when all interface are running a dhclient. The pxe's initrd is also configure to launch dhcp on a specific interface via : IP=eth0:dhcp,other:none option in pxelinux.cfg/default.

Can you try theses configuration ?

Changing the arp_filter can alter certain check done during the installation (loop detection and other stuff) and we have to verify every involvement. So I would like to find an acceptable workaround for you before going with the arp_filter solution.

Having multiple NICs in the same segment that are going to be bonded
is a common scenario in modern datacenters. The kernel should not
respond to arp requests for ip addresses that are not for the
specific NIC it arrives on.

This patch prevents dhclient from dropping its ip address while
renewing its dhcp lease. Closes redhat-cip#237
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

arp flux when multiple nics are in the same segment

2 participants