If memory serves me right, Doug Ambrisko wrote:
> Brooks Davis writes:
> | On Mon, Apr 02, 2001 at 12:28:38PM -0700, Doug Ambrisko wrote:
> | > Well I can't see that since it's not an array and the values come
> | > from iterating through Cisco's API and a direct query for the
> | > transmit key.
Brooks Davis writes:
| On Mon, Apr 02, 2001 at 12:28:38PM -0700, Doug Ambrisko wrote:
| > Well I can't see that since it's not an array and the values come
| > from iterating through Cisco's API and a direct query for the
| > transmit key. Look at ancontrol for the ugly & secret details!
|
| I'
On Mon, Apr 02, 2001 at 12:28:38PM -0700, Doug Ambrisko wrote:
> Well I can't see that since it's not an array and the values come
> from iterating through Cisco's API and a direct query for the
> transmit key. Look at ancontrol for the ugly & secret details!
I'm pretty sure I've also managed t
If memory serves me right, Doug Ambrisko wrote:
> Bruce A. Mah writes:
> | 1. Seems like I needed to ifconfig the interface up before my other
> | commands would take effect. I don't recall needing to do any such
> | thing with the old driver before I could do ancontrol. Is this a
> | change
Bruce A. Mah writes:
| 1. Seems like I needed to ifconfig the interface up before my other
| commands would take effect. I don't recall needing to do any such
| thing with the old driver before I could do ancontrol. Is this a
| change in behavior or did I miss something?
I fixed this and Ar
If memory serves me right, Brooks Davis wrote:
> If anyone wants to try it one -stable, there's a patch against it at:
>
> http://www.one-eyed-alien.net/~brooks/FreeBSD/ifconfig.diff-stable
Cool, thanks for making this available.
> The fact that wi hasn't been repo-copied in to sys/dev in stab
I stupidly wrote:
> it is not immediately obvious to me how to
> set ad-hoc mode using ifconfig(8)).
Please disregard...I see it now.
Must be my allergy meds, yeah, that's it... :-)
Bruce.
PGP signature
If memory serves me right, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Jordan Hubbard writes:
> >Cool. Does this mean that any of the foocontrol programs can go away?
>
> As far as I can see, anything short of firmware updates can be
> done by ifconfig and therefore, presumably, f
On Sat, Mar 31, 2001 at 10:16:44AM +0100, Duncan Barclay wrote:
> Can I suggest you add a DS22 for DS 22Mb/s which is going through final
> approvals at the IEEE.
I've added it and updated the diff for -current. I'll mess with the
-stable diff Thursday when I get back from my short vacation.
>
Hi Brooks,
Can I suggest you add a DS22 for DS 22Mb/s which is going through final
approvals at the IEEE.
I'll wait for these patches to settle down and merge the functionality into the
raylink driver.
Are you planning on making a unified interface for things like the signal
strenght cache?
Du
On Fri, Mar 30, 2001 at 04:42:48PM -0800, David Wolfskill wrote:
> I'll try to spend some more time with it over the weekend, but I
> certainly see no objection to committing it as it stands presently.
> I *may* try it out on -STABLE (not entirely altruism on my part; it
> would make my life simpl
>Date: Fri, 30 Mar 2001 16:35:30 -0800
>From: Brooks Davis <[EMAIL PROTECTED]>
>> Or am I just being rather denser than usual?
>No, you're entirely correct. However, this isn't my fault. ;-)
OK; fair enough (and thanks for the reality check). :-}
So far, it (the patchset) seems to not br
On Fri, Mar 30, 2001 at 03:51:27PM -0800, David Wolfskill wrote:
> One concern, and this may well affect other NIC flavors, is the list of
> media types is a little annoying to parse. Hmmm... speaking Perl, I
> suppose it could be characterized as
>
> /^\s+supported media:(\s[\S+(\s)?)+$/
>From: Poul-Henning Kamp <[EMAIL PROTECTED]>
>Date: Fri, 30 Mar 2001 23:07:08 +0200
>Any comments/reviews before we commit the patch to PR25577 ?
OK; I've built today's -CURRENT (this time, after applying Brooks'
patchset; I had built -CURRENT earlier today).
Here's a (slightly sanitized) ifcon
On Fri, Mar 30, 2001 at 01:14:13PM -0800, Jordan Hubbard wrote:
> Cool. Does this mean that any of the foocontrol programs can go away?
> I've long wished that we could have some of the wireless control stuff
> go directly into ifconfig rather than having to run an external
> program before bring
In message <[EMAIL PROTECTED]>, Jordan Hubbard writes:
>Cool. Does this mean that any of the foocontrol programs can go away?
As far as I can see, anything short of firmware updates can be
done by ifconfig and therefore, presumably, foocontrol can die
for 802.11-valued foo.
--
Poul-Henning Kamp
In message <[EMAIL PROTECTED]> Jordan Hubbard writes:
: Cool. Does this mean that any of the foocontrol programs can go away?
: I've long wished that we could have some of the wireless control stuff
: go directly into ifconfig rather than having to run an external
: program before bringing up the
Cool. Does this mean that any of the foocontrol programs can go away?
I've long wished that we could have some of the wireless control stuff
go directly into ifconfig rather than having to run an external
program before bringing up the interface.
- Jordan
To Unsubscribe: send mail to [EMAIL PRO
Any comments/reviews before we commit the patch to PR25577 ?
Get the up to date version here:
http://www.one-eyed-alien.net/~brooks/FreeBSD/ifconfig.diff
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since
19 matches
Mail list logo
