| |||||||||||||
|
| |||||||||||||
So, which hardware is it?So, which hardware is it?Posted Oct 30, 2008 15:59 UTC (Thu) by jake (editor, #205)In reply to: So, which hardware is it? by AJWM Parent article: Networking change causes distribution headaches
> 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
(Log in to post comments)
|
|
||||||||||||