Ross Becker writes: > After a reboot, neither e1000g0 nor e1000g1 showed up with ifconfig -a, and > nwam appeared to get wedged; from that point forward, on all reboots it gave > me a message that nwam failed to stop correctly and it had to send a hard > terminate to nwam.
It would have been good to get debug information following this failure (using the troubleshooting guide from the NWAM project web page), but ok; no problem with falling back to something else. > I further determined that nwam does not support sending a hostname to the > DHCP server so that it's dhcp address is registered in DNS. That's correct; the current prototype for nwam doesn't do that. It *assumes* that the DHCP server assigns the name (not that the client requests one), and that DNS (if necessary) is properly configured. > So, I set out to configure the network manually. The opensolaris > documentation suggests that I should use the GUI tool "network-admin". I run > that tool, and unfortunately, it shows me no devices. Also, all > documentation for it shows an "add" button at the top for presumably adding > interfaces, but there is no add button on the GUI. You'd need to talk to the Desktop community if you need support for that tool (it's part of GNOME, not part of the networking stack), but I suspect that "no devices" here means that you've got a serious problem with that hardware. (Disabled in the BIOS, perhaps?) > The next documentation I locate suggests that sys-unconfig should rip out > existing network configuration and prompt me for it on the next boot. Not > so. I run "sys-unconfig", my system reboots, and it prompts me for hostname, > locale settings, root password, and time configuration, but it doesn't ask me > a single question about network configuration. That utility does trigger network reconfiguration for traditional Solaris (such as SXCE). I'm not sure what it does on the OpenSolaris distribution; that's a bit of a different animal. I suggest talking with the Indiana project team about your problems with sys-unconfig. > Now I'm down to manual command line configuration. > > According to the documentation here: > http://opensolaris.org/os/community/documentation/newbie_faq/ > > I should "touch /etc/dhcp.e1000g0", and "echo myhostname > > /etc/dhcp.e1000g0", but when I do that, the network/physical:default service > fails to start, complaining about an invalid configuration. For one thing, you're missing this (at least by the commands you list above): touch /etc/hostname.e1000g0 For another, using the hostname-request feature means putting this in /etc/hostname.e1000g0: inet myhostname Note the "inet" keyword there. That doesn't go in /etc/dhcp.e1000g0. > For the dhcp name transmission, I know I'm supposed to edit > /etc/default/dhcpagent and make sure it has a line reading > REQUEST_HOSTNAME=yes, which I've done, but it doesnt appear that my system is > getting there yet. See above; this goes in the /etc/hostname.e1000g0 file. See dhcpagent(1M) for more information. > Right now, the only time my network comes up is if I remove > /etc/hostname.e1000g0 and /etc/dhcp.e1000g0, let the system come up, and > issue the following commands: ifconfig e1000g0 plumb, ifconfig e1000g0 dhcp. > > At this point I am REALLY frustrated with the documentation. At every turn, > the documentation is missing, highly obscure, or flat-out incorrect. When a service fails, run "svcs -x" to find out what the system says about the service. Usually, it'll refer to a log file. Examine that log file to see what the errors are. In this case, I _suspect_ that you have only 'myhostname' specified in /etc/hostname.e1000g0 and you don't have that name in your /etc/hosts file, so the system doesn't know how to interpret it, and it's failing out the network/physical:default service. Just a guess, though. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> 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 _______________________________________________ networking-discuss mailing list [email protected]
