Re: [SLE] Wireless, DHCP, Firewall Issues [SOLVED, sort of ...]
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
On Friday, 28 of May 2004 23:40, Jim Poteet wrote:
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.
eth0 and wlan0 both ask dhcp server for config. have you check your logs. does not show there that resolve file can not be replaced? you can not ask twice for routing information at boot.
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.
use profiles and scmp
Is it standard for the DHCP server to also supply the gateway address, as well as DNS information?
it can proved such info but it depends on configuration -- Marek Chlopek
I setup my laptop with SCP. (YAST->SYSTEM->Profile manager) It "remembers" changes to your configuration and switches back and forth between them. I use it for exactly this purpose: First confguration: For standard work: Dual Screen, eth dhcp setup for my home network. Second configuration: For office work: Only LCD, eth fixed address, for office. Third configuration: for wireless: Only LCD, wireless with DHCP accept any... Maybe you can use something similar? Jerry On Fri, 2004-05-28 at 23:40, Jim Poteet wrote:
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
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Fri, 2004-05-28 at 17:40, Jim Poteet wrote:
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?
Yes, DHCP can supply not only the IP address but the default gateway and
the DNS information. That is fairly standard but configurations can be
changed to supply any or all of those items.
The fact that you get an IP address but no gateway means that either the
gateway is not being provided or when it is your system is not taking it
for some reason. You will need to examine the log files carefully for
an indication that something failed when the DHCP setup occurred.
Check the /etc/resolv.conf file for DNS entrys. You may want to double
check that you don't have two DHCP servers running on the network.
--
Scot L. Harris
participants (4)
-
Jerome R. Westrick
-
Jim Poteet
-
Marek Chlopek
-
Scot L. Harris