On Sun, May 11, 2008 at 08:34:02PM +0200, Michal Bachorik wrote:
> Hi all,
> 
> (if I write to bad alias, let me know please).
> 
> I have quite a strange problem with Opensolaris 2008.05 LiveCD - when I use
> it as a LiveCD, my network is working without any problem (nwam is enabled),
> but when I install the LiveCD image on my harddrive, network is not working
> regardless I use nwam or switch to static wired network ("physical").
> 
> My HW setup is:
> 
> AMD Athlon FX64 x2, 2Gb RAM, RealTek 1Gb LAN (integrated on a motherboard)
> 
> The problem is the name resolution...

I'm not sure of the details on how the network admin gui works and makes
configuration persist, but I can give you a few suggestions about nwam vs.
network/physical:default.

My guess is that the problem is that your /etc/resolv.conf and/or
/etc/nsswitch.conf files are not getting set up properly; the DHCP server
usually provides the name of the dns server and optionally the dns domain,
but there are additional steps that need to be taken to load that information
into /etc/resolv.conf so that your dns client can find it, and to update
/etc/nsswitch.conf so that the name services library knows to use dns in
the first place.

When you use network/physical:default for your network configuration, it
relies on svc:/network/service to edit /etc/resolv.conf and /etc/nsswitch.conf
as needed; so if network/physical:default is enabled after boot, the file
won't be updated.

NWAM should ensure that the files are updated whenever a DHCP lease is
acquired, but there's an open bug with that that seems to be popping up
quite frequently in the latest opensolaris builds that you might be running
into.  Have you tried simply restarting the nwam service?  That should
help; the bug seems to be timing related and usually only happens during
boot.  See http://defect.opensolaris.org/bz/show_bug.cgi?id=1293 or
http://bugs.opensolaris.org/view_bug.do?bug_id=6584967.

-renee
_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to