From: Thomas Munck Steenholdt <tmus@tmus.dk>
To: jt@hpl.hp.com, hermes@gibson.dropbear.id.au
Cc: netdev@oss.sgi.com, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [PATCH] 2.6.3 orinoco.c patch to support ethtool get_link
Date: Fri, 12 Mar 2004 19:49:35 +0100 [thread overview]
Message-ID: <4052063F.9020107@tmus.dk> (raw)
In-Reply-To: <404E4159.9040404@tmus.dk>
Thomas Munck Steenholdt wrote:
> Jean Tourrilhes wrote:
>
>> I hope you realise that most often link status is meaningless
>> with Wireless cards. In Ad-Hoc mode, the link is always up, regardless
>> of the number of nodes in the cell, check the discussion on the HostAP
>> mailing list. And the Orinoco card will report connected even is WEP
>> is wrong. But, if you only use managed mode without WEP, that should
>> work.
>> I just wonder if it's better to report a 'link status' that
>> may be wrong/misleading or to not report anything at all.
>
>
> Actually, if the WEP key is wrong(i guess that's what you mean) the
> link is determined as down, like it should be!
>
> For the AdHoc mode, sure the link is always determined as up, but that
> is really the best way to do it given the nature of an Ad-Hoc network,
> right!
>
> The way I see it you'll gain from this patch whenever in managed mode.
> Most people (in my experience) is using managed mode and thus would
> benefit from this functionality!
>
> Thomas
>
>
Please comment on this ?
I feel it's a really good idea that would improve things for me a lot -
I'm sure I'm not the only one!
Thomas
next prev parent reply other threads:[~2004-03-12 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 18:52 [PATCH] 2.6.3 orinoco.c patch to support ethtool get_link Jean Tourrilhes
2004-03-09 22:12 ` Thomas Munck Steenholdt
2004-03-12 18:49 ` Thomas Munck Steenholdt [this message]
2004-03-12 18:53 ` Jean Tourrilhes
2004-03-16 0:14 ` David Gibson
-- strict thread matches above, loose matches on Subject: below --
2004-03-07 1:49 Thomas Munck Steenholdt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4052063F.9020107@tmus.dk \
--to=tmus@tmus.dk \
--cc=hermes@gibson.dropbear.id.au \
--cc=jgarzik@pobox.com \
--cc=jt@hpl.hp.com \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).