David Helm writes: > I don't think that there is a duplex issue...as version 1.13 works. > Also, dhcp negotiates both the ip address and the duplex.
No, it doesn't. DHCP is an IP mechanism. Duplex negotiation occurs at the link layer -- meaning IEEE 802 standards. If duplex (or link layer) negotiation fails, then everything above is likely to fail. That includes DHCP as well as other network layer and above protocols. In other words, I don't think DHCP is involved in this failure case. It's just another victim of whatever the underlying problem might be. > Is there a way to be sure? Again even manually plumbing the nge0 interface > with the 1.14 driver doesn't work (ie the interface is not able to see > anything on the net) The driver kstats should reveal almost everything that's knowable about the link. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 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]
