On Wed, Mar 08, 2006 at 01:54:43PM +0000, Jeremy Harris wrote:
> - You mention upcoming wireless technologies (e.g. WiMAX).
> Is it wise to nail the explicit word "wifi" into the subcommand
> names {scan,connect,show,disconnect}-wifi?
>
> Could the project be used, e.g. for access to data-networking on
> cable?
I'm not fond of the -wifi thing -- scanning, connecting, disconnecting
and displaying current status are all fairly generic sounding tasks. I
could see connect/disconnect/show being applicable to point-to-point
interfaces, for example, but also for some future wired technology that
requires login to the network at the link-layer, through EAP, say.
> - It seems that you're conflating the concepts of the device used
> to access the channel, and the data-link channel itself, by
> modeling the selection of the channel (wifi channel number plus
> ESSID) as properties attached to the major identifier used by
> dladm (the link name).
>
> I'm concerned that the implied semantics of "a data link" which in
> the wifi case, to me, means the channel defined by [frequency, ESSID]
> are being obscured. The labeling confusion might give rise
> to higher support costs. There are potentially multiple data-links
> available at one time.
>
> (Nit) can any extant wifi hardware talk to multiple ESSIDs (or, indeed
> frequencies)?
If so, couldn't/shouldn't multiple ESSIDs be modelled as virtual
interfaces?
Nico
--
_______________________________________________
networking-discuss mailing list
[email protected]
