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.

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

Macvlan arp proxy #177

Merged
merged 3 commits into from
Apr 8, 2016
Merged

Macvlan arp proxy #177

merged 3 commits into from
Apr 8, 2016

Conversation

steveej
Copy link
Member

@steveej steveej commented Apr 7, 2016

Closes #149.

jellonek added 2 commits April 7, 2016 21:40
Resolves CNI part of rkt/rkt#1765
Second part would be adding similar lines into kvm flavored macvlan
support (in time of creating macvtap device).
@steveej steveej merged commit 41ee449 into containernetworking:v0.3.0 Apr 8, 2016
@steveej steveej deleted the macvlan-arp-proxy branch May 10, 2016 15:43
jellonek added a commit to containernetworking/plugins that referenced this pull request Feb 21, 2021
The original issue was: containernetworking/cni#84
I've added "a fix" for it in
containernetworking/cni#149 which then was
merged in containernetworking/cni#177

The thing is that "the fix" was incorrect as it was setting 1 on
arp_proxy (I really don't recall why) instead of setting it on
arp_notify - which was my original suggestion in:
rkt/rkt#1765 (comment)
Setting apr_proxy can be harmfull and we have already support for
sending GratuitousArpOverIface after setting an IP address, so setting
any sysctl should not be needed.

Signed-off-by: Piotr Skamruk <[email protected]>
michaelbarrington pushed a commit to michaelbarrington/plugins that referenced this pull request Jun 21, 2021
The original issue was: containernetworking/cni#84
I've added "a fix" for it in
containernetworking/cni#149 which then was
merged in containernetworking/cni#177

The thing is that "the fix" was incorrect as it was setting 1 on
arp_proxy (I really don't recall why) instead of setting it on
arp_notify - which was my original suggestion in:
rkt/rkt#1765 (comment)
Setting apr_proxy can be harmfull and we have already support for
sending GratuitousArpOverIface after setting an IP address, so setting
any sysctl should not be needed.

Signed-off-by: Piotr Skamruk <[email protected]>
apreuavar6 added a commit to apreuavar6/cni-plugins that referenced this pull request Aug 11, 2024
The original issue was: containernetworking/cni#84
I've added "a fix" for it in
containernetworking/cni#149 which then was
merged in containernetworking/cni#177

The thing is that "the fix" was incorrect as it was setting 1 on
arp_proxy (I really don't recall why) instead of setting it on
arp_notify - which was my original suggestion in:
rkt/rkt#1765 (comment)
Setting apr_proxy can be harmfull and we have already support for
sending GratuitousArpOverIface after setting an IP address, so setting
any sysctl should not be needed.

Signed-off-by: Piotr Skamruk <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants