Renee, I'm hoping you can help me understand this bug, a bit more. Recall that I can't get NWAM to work in office (wired), as it won't fill in /etc/resolv.conf. The bug states it was fixed in SNV_b94. I recently upgraded to build 103, and am still having issues with it.
What can we do to get this fixed? Thanks, Jim Renee Danson wrote: > Hi Jim, > > On Thu, Jun 26, 2008 at 09:16:23AM -0700, Jim Nissen wrote: > >> All, >> I'm trying to get nwam configured, and having troubles with one >> location/interface (office). At home, it works fine. >> >> At the office, I rely on wired network interface e1000g0, and at home I used >> wireless wpi0. Here's a copy of my llp file... >> >> e1000g0 dhcp >> wpi0 dhcp >> >> The problem I am having is that, at the office, I don't get DNS >> /etc/resolv.conf populated, on boot. Therefore, no name resolution works. >> However, if I bring e1000g0 down, and restart nwamd service, it comes up >> with /etc/resolv.conf populated. >> >> Any clues? >> > > It sounds like you're running into CR 6584967[1]. It's a race condition > that occurs on boot, and is more likely to occur with wired interfaces > than with wireless (as it generally takes a bit longer to bring up a > wireless interface, the timing is sufficiently different to avoid the > problem); restarting the nwam service should be sufficient to fix things > up. > > I'm working on a fix right now; in fact, I had a webrev out for review > last week, but found some last minute issues. I expect to get a revised > webrev out today; integration into nevada (and subsequent push to the > opensolaris repo) should follow in the near future. I will update this > list with my progress. > > -renee > > [1]http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6584967 > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/nwam-discuss/attachments/20081124/3ff3eae5/attachment.html>
