On Tue, May 13, 2008 at 10:18:43AM -0400, James Carlson wrote: > Michal Bachorik writes: > > I believe that my nsswtich.conf is correct and also my resolv.conf is ok > > (well, i work in sun and I am using solaris daily;) ). what I do not > > understand, why there is no device set for default route. > > That's not necessarily a problem. You'll see a device there only if > the caller that installed the route specified a particular output. > The route will work either way. > > I didn't see anything particularly wrong with the 'netstat -nr' output > you've posted. > > > To me, the problem seems more similar to bug > > 6584967<http://bugs.opensolaris.org/view_bug.do?bug_id=6584967>- which > > would be that to successfully switch from nwam to static wired > > connection it is not enough to disable "nwam" and enable "network/physical", > > but some step is missing. > > If it is that bug, do you have some evidence that this is happening? > > I'd suggest that if restarting physical:nwam doesn't fix the problem, > then this bug likely has nothing to do with it.
Agreed. Evidence that you were hitting CR 6584967 would be hosts entries in /etc/nsswitch.conf that did not include "dns", or server and domain entries missing from /etc/resolv.conf. And restarting nwam would resolve the problem. If your files look fine, then I don't think this is the problem you're seeing. When you have nwam enabled, it will automatically bring up interfaces without any configuration on your part; it uses dhcp to do this. There's some information about using static addressing with nwam in step 4 of the nwam troubleshooting guide found at http://opensolaris.org/os/project/nwam/phase0/troubleshooting/. If you switch to network/physical:default, you must do some configuration first. You should create /etc/hostname.<intf>, containing the static ip address if that's your preference, or empty if you want to use dhcp. If you're using dhcp, you must also create /etc/dhcp.<intf>. After enabling network/phsyical:default, you'll need to manually create /etc/resolv.conf and update /etc/nsswitch.conf if you're not using dhcp; or restart network/service, in order to update those files, in the dhcp case. You may also need to create your default route if you're not using dhcp. I'm not sure which of these steps you've done; but if your resolv.conf and nsswitch.conf files look okay, and your route is set as shown in the netstat output you sent, I don't see where the problem might be. In the case where the first nslookup works, but subsequent ones do not, were you using dhcp? Is it possible you lost your lease? -renee _______________________________________________ networking-discuss mailing list [email protected]
