| |||||||||||||
|
| |||||||||||||
So, which hardware is it?So, which hardware is it?Posted Oct 29, 2008 17:10 UTC (Wed) by jake (editor, #205)In reply to: So, which hardware is it? by jspaleta Parent article: Networking change causes distribution headaches
> There is a specific router mentioned in the kernel and ubuntu bug reports.
> > That's the biggest problem with this issue, we don't know how widespread it is.
Hmm, I thought another dimension of the problem was that it is not clear that it is only home routers that are problematic. If there is gear installed at the ISPs that is affected by this problem, it doesn't much matter what gear we buy. Which is not to say that it would not be worth knowing, just that no matter how much testing is done and how many new home routers are bought, we may still be routed through bad hardware.
jake
(Log in to post comments)
So, which hardware is it? Posted Oct 29, 2008 18:51 UTC (Wed) by ncm (subscriber, #165) [Link]
After seven years, routers that discard ECN packets remain common. The routers' owners don't care, and why should they? The only people affected are, y'know, us.
So, which hardware is it? Posted Oct 30, 2008 15:27 UTC (Thu) by AJWM (guest, #15888) [Link]
Well, those of us who work for ISPs or at companies with major data centers may care (and have influence) over more than just home-based gear. And those of us who work for vendors of such gear can raise their voices towards getting it fixed going forward.
(Minor rant mode: I don't know if it's just me noticing it more, or the problem is getting worse, but lately I'm seeing a lot of messages (posts and emails) complaining about problems without providing any specifics that would allow me (or someone) to investigate/fix the problem. Maybe it's the run-up to the election: all these zero-real-content political messages are causing widespread brain damage. Minor rant mode off.)
So, which hardware is it? Posted Oct 30, 2008 15:59 UTC (Thu) by jake (editor, #205) [Link]
> Well, those of us who work for ISPs or at companies with major data centers
> may care (and have influence) over more than just home-based gear. And those > of us who work for vendors of such gear can raise their voices towards > getting it fixed going forward.
Which would be great of course. It is just not clear to me how Linux users who are experiencing problems with their TCP connectivity will be able to even determine what hardware is causing the problem. They may be able to switch to a known-good home router, but if they still have the problem, it is not obvious (at least to me) how to diagnose it from there. ISPs, at least in my experience, are not very interested in discussing their networking gear with their customers. Alerting them to the problem might help, at least in some cases, but it really isn't ever going to allow Linux to put the options in any arbitrary order.
jake
|
|
||||||||||||