iputils use flag for arping #1572

Closed
themicster opened this Issue Sep 13, 2016 · 5 comments

Comments

Projects
None yet
5 participants
@themicster

I would like to see arping included in CoreOS as I used it to make sure my gateway knew of ip addresses that have moved to a new machine so my containers can float around my cluster. It used to be included because of a bug in iputils but since has been fixed and the USE flag needs to be set to get it included now.

@crawford

This comment has been minimized.

Show comment
Hide comment
@crawford

crawford Sep 15, 2016

Member

Do you know which version of CoreOS used to include this?

Member

crawford commented Sep 15, 2016

Do you know which version of CoreOS used to include this?

@johan-adriaans

This comment has been minimized.

Show comment
Hide comment
@johan-adriaans

johan-adriaans Sep 16, 2016

I'm not sure if it helps, but 1010.6.0 used to have arping. I have the same problem.

I'm not sure if it helps, but 1010.6.0 used to have arping. I have the same problem.

@johan-adriaans

This comment has been minimized.

Show comment
Hide comment
@johan-adriaans

johan-adriaans Sep 16, 2016

BTW, this is a reasonable workaround:

docker run --net=host --entrypoint /usr/sbin/arping --rm alpine:3.4 -c 10 -U -I eth0 123.123.123.123

BTW, this is a reasonable workaround:

docker run --net=host --entrypoint /usr/sbin/arping --rm alpine:3.4 -c 10 -U -I eth0 123.123.123.123
@themicster

This comment has been minimized.

Show comment
Hide comment
@themicster

themicster Sep 16, 2016

It was in 1010.6.0. That looks like a good work around. But it is a bit slower.

It was in 1010.6.0. That looks like a good work around. But it is a bit slower.

@coresolve

This comment has been minimized.

Show comment
Hide comment
@coresolve

coresolve Mar 8, 2017

Another point on this.
When deploying to aws we have public and private subnets. If you are troubleshooting connectivity on a private subnet and have managed to blackhole your traffic. It's useful to have tracepath available without the need to start a toolbox. Since starting a toolbox expects that you have network connectivity.

Another point on this.
When deploying to aws we have public and private subnets. If you are troubleshooting connectivity on a private subnet and have managed to blackhole your traffic. It's useful to have tracepath available without the need to start a toolbox. Since starting a toolbox expects that you have network connectivity.

@dm0- dm0- self-assigned this Mar 8, 2017

@dm0- dm0- referenced this issue in coreos/coreos-overlay Mar 8, 2017

Merged

Install traceroute and arping #2468

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment