Tom Chen wrote: > I found a little more clue: > OS - Nevada v68 patched with latest ON Bits(20070730). > 1.The "Network setting" menu may have some bugs > Adding a new gldv3 driver, set it to 192.168.xx.xx, reboot, then e1000g0 IP > address becomes 0.0.0.0 > 2.Try "Network setting" menu to configure e1000g0, can not enter, menu grayed > out and hangs up. > 3.Manually delete /etc/dhcp.e1000g0 and /etc/hostname.e1000g0, reboot, > "Network setting" menu can be entered and can configure e1000g0, but hangs up > after clicking "Activate" to finish. > 4.Manually re-create /etc/dhcp.e1000g0 and /etc/hostname.e1000g0 and reboot, > e1000g0 can get IP address and works fine. > 5.Re-enter "Network setting" menu, situation looks like back to stage 2,ie > can not enter, must follow step 3,4 to regain correct IP address. > > When I was testing GLDV2 driver on version 68 OS without ON bits, I never had > these problems. >
I think you're trying to debug both driver and network configuration scripts. I recommend you not do that, but focus on just one step at a time. Specifically, unplumb/unconfigure all but your default network, and don't use DHCP for that if you can help it. Then, manually configure your GLDv3 interface. I would use a different subnet if at all possible, for initial testing. I usually test static IP configurations first, and only after that works, test DHCP. For a fixed config, just use ifconfig as this: ifconfig <interface> plumb <ip> netmask <netmask> broadcast + up For a DHCP config, use ifconfig <interface> plumb ifconfig <interface> dhcp start This seems to work well for me. -- Garrett > Tom > > > This message posted from opensolaris.org > _______________________________________________ > networking-discuss mailing list > [email protected] > _______________________________________________ networking-discuss mailing list [email protected]
