Scot ... Things quit working again. I did a reboot with the ethernet disconnected and the wireless card unplugged. After booting, I plugged in the wireless card and was able to ping locally, but not to the internet. A netstat command showed no gateway. I finally went to YaST and deleted the eth0 connection completely. I also blanked the gateway information. After exiting from YaST, everything works OK. There's apparently a lot more to working with two nic cards than I can understand right now, however, this gives me the workaround I need, since most of the use of this laptop will be wireless. Is it standard for the DHCP server to also supply the gateway address, as well as DNS information?
"Scot L. Harris"
5/27/04 9:09:51 AM >>> On Thu, 2004-05-27 at 00:32, Jim Poteet wrote:
Scot ...
Thanks for your help.
The gateway was set correctly for both NICs. However, I noticed when running the netstat that both interfaces were reporting, even with the ethernet cable pulled and even after an ifdown command. I tried cycling through YaST, with the cable pulled, before ifstatus and netstat recognized that the interface was not there. After this, everything seems to be working. I'm still trying to figure out exactly what transpired and why this would let the local stuff work, but not the remote.
I'm going to mark this one as closed for now, since things are working, but I will go through the steps in an orderly fashion to see if I can understand it.
Thanks again.
.... Jim
hmmm, so there was a default gateway for both NICs at the same time?
Could the problem be that the system was sending off LAN traffic to the
wrong gateway? Would explain why you could hit local stuff but not
things off LAN.
Glad you are up and running.
--
Scot L. Harris