Skip to content
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.

Sign up for GitHub

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

Jump to bottom

arp flux when multiple nics are in the same segment #237

Open
gerhardqux opened this issue Apr 7, 2015 · 0 comments · May be fixed by #239
Open

arp flux when multiple nics are in the same segment #237

gerhardqux opened this issue Apr 7, 2015 · 0 comments · May be fixed by #239

Comments

@gerhardqux
Copy link

We have multiple NICS on the same segment that are going to be bonded. eDeploy runs dhclient on all interfaces and receives different ip addresses for each NIC. This works as expected.

After a while dhclient tries to refresh its ipaddresses and contacts the dhcp server with its lease. The dhcp server tells the dhclients that they can still use their ip addresses. Dhclient then verifies that noone on the same network segment has this particular ip adress configured using an arp request. It gets a response, and dhclient removes the ipaddress from the interface.

The problem is that it gets a response from itself. eth0 receives an arp response from eth1.

I suggest setting arp_filter to 1 during deployment.
gerhardqux pushed a commit to gerhardqux/edeploy that referenced this issue Apr 14, 2015
build/init.common: prevent arp responses on the wrong nic.
1220f8d 
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
@gerhardqux gerhardqux linked a pull request Apr 14, 2015 that will close this issue
Open
gerhardqux pushed a commit to gerhardqux/edeploy that referenced this issue Apr 15, 2015
@gerhardqux
build/init.common: prevent arp responses on the wrong nic.
99deb6f 
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
gerhardqux pushed a commit to gerhardqux/edeploy that referenced this issue Apr 20, 2015
@gerhardqux
build/init.common: prevent arp responses on the wrong nic.
c29cb46 
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
gerhardqux pushed a commit to gerhardqux/edeploy that referenced this issue Apr 28, 2015
@gerhardqux
build/init.common: prevent arp responses on the wrong nic.
9415299 
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
gerhardqux pushed a commit to gerhardqux/edeploy that referenced this issue May 5, 2015
@gerhardqux
build/init.common: prevent arp responses on the wrong nic.
f8682b4 
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
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

build/init.common: prevent arp responses on the wrong nic. gerhardqux/edeploy
1 participant
@gerhardqux