Tony Cleal writes: > root at x4nex1:/export/home/tc# ifconfig -a > > lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 > index 1 > inet 127.0.0.1 netmask ff000000 > > vfe0: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu 1500 > index 2 > inet 10.0.0.184 netmask ffffff00 broadcast 10.0.0.255 > ether 0:30:1b:44:d6:b
At least by that, it looks like DHCP is working fine. > How can I set it such that it picks up vfe0 and not lo0? I don't think I understand that question. "lo0" is a normal internal loopback interface, and it'll be used when necessary. Can you share these things to help narrow down the problems you're seeing? - output of "netstat -nr" - contents of "/etc/nsswitch.conf" - contents of "/etc/resolv.conf" - result of "ping -n www.sun.com" and "traceroute -n www.sun.com" - output of "svcs network/physical" At a guess, you're running into problems that are unrelated to those GUI tools and are instead a basic problem with network configuration. > Accessing network manager either through the front end or via root shows > nothing under location, the connections tab is empty and the buttons all > greyed out, the General tab correctly shows the host name, DNS is showing the > IP address of the router and the hosts tab is showing the IP address attached > to lo0 (127.0.0.1)...? None of that sounds particularly wrong to me. -- 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
