http://defect.opensolaris.org/bz/show_bug.cgi?id=5460
Summary: connecting by ESSID or ESSID/BSSID
Classification: Development
Product: nwam
Version: unspecified
Platform: ANY/Generic
OS/Version: OpenSolaris
Status: NEW
Severity: major
Priority: P3
Component: ON daemon
AssignedTo: nwam-dev at opensolaris.org
ReportedBy: Anurag.Maskey at Sun.COM
QAContact: nwam-dev at opensolaris.org
As seen in this [1] discussion, libdladm ignores the BSSID when connecting to
networks. But NWAM Phase 0 and 0.5 went to great lengths to use both ESSID and
BSSID in connecting to networks and creating secure object names. Since Phase 1
is rewriting nwamd, we can rewrite how connections are made, whether just ESSID
is used or both ESSID and BSSID.
CR 6773627 [2] introduces a nwamd/strict_bssid flag (which will go away with
Phase 1), but a similar idea can be used if there is need to give an option to
the user.
Also, a way of generating secure object names need to be figured out. ESSID's
can have any characters, but secure object names use limited characters with
the fix of CR 6766937 [3]. Some suggestions in [1] include MD5 or SHA1 hash,
CRC-32, base64 encoding.
[1] http://www.opensolaris.org/jive/thread.jspa?threadID=83358&tstart=0
[2] http://bugs.opensolaris.org/view_bug.do?bug_id=6773627
[3] http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6766937
--
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
