Some updated notes: James Carlson writes: > I've put each one of these fixes through unit testing on a Tecra > laptop with "wpi0" and "e1000g0" interfaces. I have full SPARC and > x86 nightly builds running now, and an updated nwamd has been sent to > the submitter of CR 6834140 for verification.
The submitter reports that the new nwamd solves his wireless problems (and in fact works better than expected; setting e1000g0 to a high priority still falls back to wireless after DHCP failure). > I still have to: > > - run the DHCP client test suite; results should be unchanged from > Nevada. I've run both the DAD and DHCP client test suites on unmodified Nevada and on the fixed code. All tests pass in both cases. I've put the test results here: http://cr.opensolaris.org/~carlsonj/testing-4783123/ http://zhadum.east/ws/carlsonj/4783123-fix/testing/ (If looking at the journal files, note that the DHCP test suite logs the uname information on the server [the test driver] rather than information on the client [the system under test].) -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
