Bug#537271: closed by Matthew Palmer <firstname.lastname@example.org> (This is done, regardless of the reason)
tag 537271 +help +wontfix # Need a 'cantfix' tag
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 more productive just to close random bugs than to spend
several hours investigating, testing, and talking to the maintainers of the
relevant parts of the kernel.
The initial bug merge was incorrect, I will admit that; given the number of
closes and merges I did to cleanup the bug list, I wouldn't be surprised if
it was the only mistake I made. Beyond that, though, what is your problem?
> 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
> answer ARP requests or it cannot route packets.
Emphasis on "IPv4" and "router", neither of which are required items.
> > the improved DHCP configuration, whereby DHCP DISCOVER packets are
> > sent every second, is the best possible fix for this (coupled with the
> > ability to preseed whatever length of DHCP timeout you want).
> irrelevant for statically configured networks. i.e., servers.
You are correct. I'm not exactly in a mood to fix this for you, though, so