clone 537271 -1
reassign -1 busybox
block 537271 by -1
thanks
Quoting Matthew Palmer (mpal...@debian.org):
As you have identified:
On Sun, Feb 06, 2011 at 10:15:48PM -0500, Robert Edmonds wrote:
(this should probably
actually be a loop that repeatedly invokes arping with a short
On Monday, February 07, 2011 06:00:40 am Matthew Palmer wrote:
Also, busybox patches should be put into a separate bug report which blocks
this one, to keep things clear.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606654 - Busybox should
include arping applet
Regarding IPv6:
I see
reopen 537271
thanks
Debian Bug Tracking System wrote:
Given that there is no possible way to detect that the network link is up
but unuseable,
did you even read #537271? the simple, 100% effective fix for the
situation where your port has link up but the bridge port has not
entered the
tag 537271 +help +wontfix # Need a 'cantfix' tag
thanks
On Sun, Feb 06, 2011 at 05:51:06PM -0500, Robert Edmonds wrote:
Debian Bug Tracking System wrote:
Given that there is no possible way to detect that the network link is up
but unuseable,
did you even read #537271?
No, I find it far
tag 537271 +patch
thanks
Matthew Palmer wrote:
the simple, 100% effective fix for the
situation where your port has link up but the bridge port has not
entered the forwarding state is to send ARP requests for the default
gateway's IP address until they are answered. an IPv4 router must
As you have identified:
On Sun, Feb 06, 2011 at 10:15:48PM -0500, Robert Edmonds wrote:
(this should probably
actually be a loop that repeatedly invokes arping with a short
timeout in order to update the progress bar.)
This really needs to be implemented. Leaving users hanging
Matthew Palmer wrote:
On Sun, Feb 06, 2011 at 10:15:48PM -0500, Robert Edmonds wrote:
(this should probably
actually be a loop that repeatedly invokes arping with a short
timeout in order to update the progress bar.)
This really needs to be implemented. Leaving users hanging
7 matches
Mail list logo
