Bug 134722

Summary: DNS queries take a long time after reconfiguring the network
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Michael Stather <kontakt>
Component: YaST2Assignee: Christian Zoz <zoz>
Status: RESOLVED INVALID QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: YaST2 logs
one config file
the w-lan card config file

Description Michael Stather 2005-11-21 18:05:00 UTC 
I´ve a notebook with an integrated NIC which worked fine. Then I added a wireless network card over USB which is not always present. So I set it to "start when hotplugged" in YaST2. Now it takes a very long time when the computer queries the DNS, e.g. when visiting a webpage. When the initial request is done the subsequent pages load fast. Direct connections with an IP work immediately.
This wasn´t like before I added the wireless card.
I´ve no idea what the reason could be. hwinfo --network returns:
hwinfr098089:/home/michael # hwinfo --network
19: None 00.0: 10701 Ethernet
  [Created at net.111]
  Unique ID: T2Fp.ndpeucax6V1
  SysFS ID: /class/net/cipsec0
  Hardware Class: network interface
  Model: "Ethernet network interface"
  Device File: cipsec0
  HW Address: 00:0b:fc:f8:01:8f
  Config Status: cfg=new, avail=yes, need=no, active=unknown

20: None 00.0: 10701 Ethernet
  [Created at net.111]
  UDI: /org/freedesktop/Hal/devices/net_00_02_a5_b8_1b_0f
  Unique ID: usDW.ndpeucax6V1
  Parent ID: rBUF.SPbcKWAadaA
  SysFS ID: /class/net/eth0
  SysFS Device Link: /devices/pci0000:00/0000:00:1e.0/0000:02:08.0
  Hardware Class: network interface
  Model: "Ethernet network interface"
  Driver: "e100"
  Device File: eth0
  HW Address: 00:02:a5:b8:1b:0f
  Link detected: yes
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #13 (Ethernet controller)

21: None 00.0: 10700 Loopback
  [Created at net.111]
  Unique ID: ZsBS.GQNx7L4uPNA
  SysFS ID: /class/net/lo
  Hardware Class: network interface
  Model: "Loopback network interface"
  Device File: lo
  Link detected: yes
  Config Status: cfg=new, avail=yes, need=no, active=unknown

22: None 00.0: 10781 Network Interface
  [Created at net.111]
  Unique ID: wl2P.nfEXJulusj6
  SysFS ID: /class/net/sit0
  Hardware Class: network interface
  Model: "Network Interface"
  Device File: sit0
  Config Status: cfg=new, avail=yes, need=no, active=unknown

I also attached the YaST logs, perhaps they´re interesting.
Comment 1 Michael Stather 2005-11-21 18:06:06 UTC 
Created attachment 57926 [details]
YaST2 logs
Comment 2 Michael Gross 2005-11-22 11:03:59 UTC 
Please provide the output of `ifconfig', `route -n' and your /etc/resolv.conf (both things if plugged and unplugged would be helpful).
Comment 3 Michael Stather 2005-11-22 16:00:26 UTC 
Without WLAn adapter:
r098089:/home/michael # ifconfig
eth0      Protokoll:Ethernet  Hardware Adresse 00:02:A5:B8:1B:0F
          inet Adresse:10.150.98.89  Bcast:10.150.98.255  Maske:255.255.255.0
          inet6 Adresse: fe80::202:a5ff:feb8:1b0f/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1753 errors:0 dropped:0 overruns:0 frame:0
          TX packets:623 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 Sendewarteschlangenlänge:1000
          RX bytes:592421 (578.5 Kb)  TX bytes:132431 (129.3 Kb)

lo        Protokoll:Lokale Schleife
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:218 errors:0 dropped:0 overruns:0 frame:0
          TX packets:218 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 Sendewarteschlangenlänge:0
          RX bytes:16012 (15.6 Kb)  TX bytes:16012 (15.6 Kb)

r098089:/home/michael # route -n
Kernel IP Routentabelle
Ziel            Router          Genmask         Flags Metric Ref    Use Iface
10.150.98.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         10.150.98.254   0.0.0.0         UG    0      0        0 eth0

r098089:/home/michael # cat /etc/resolv.conf
nameserver 10.150.126.2
nameserver 10.150.127.2
search stusta.mhn.de
Comment 4 Michael Stather 2005-11-22 16:03:08 UTC 
With WLAN plugged, but not in a network (don´t have one here) but the problems are also without a WLAN network:

r098089:/home/michael # ifconfig
eth0      Protokoll:Ethernet  Hardware Adresse 00:02:A5:B8:1B:0F
          inet Adresse:10.150.98.89  Bcast:10.150.98.255  Maske:255.255.255.0
          inet6 Adresse: fe80::202:a5ff:feb8:1b0f/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1989 errors:0 dropped:0 overruns:0 frame:0
          TX packets:738 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 Sendewarteschlangenlänge:1000
          RX bytes:689648 (673.4 Kb)  TX bytes:148608 (145.1 Kb)

lo        Protokoll:Lokale Schleife
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:218 errors:0 dropped:0 overruns:0 frame:0
          TX packets:218 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 Sendewarteschlangenlänge:0
          RX bytes:16012 (15.6 Kb)  TX bytes:16012 (15.6 Kb)

wlan0     Protokoll:Ethernet  Hardware Adresse 00:01:24:B0:5C:B3
          inet6 Adresse: fe80::201:24ff:feb0:5cb3/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST NOTRAILERS MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 Sendewarteschlangenlänge:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

r098089:/home/michael # route -n
Kernel IP Routentabelle
Ziel            Router          Genmask         Flags Metric Ref    Use Iface
10.150.98.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         10.150.98.254   0.0.0.0         UG    0      0        0 eth0

r098089:/home/michael # cat /etc/resolv.conf
nameserver 10.150.126.2
nameserver 10.150.127.2
search stusta.mhn.de
Comment 5 Michael Gross 2005-11-23 14:02:06 UTC 
We need help from the kernel maintainers here.
Comment 6 Hannes Reinecke 2005-11-23 14:09:52 UTC 
Nothing to do with us (initially). Suspect network misconfiguration.
Christian, please reassign if you don't think its the fault of someone else.
Networkmanager comes to mind.
Comment 7 Christian Zoz 2005-11-25 11:34:21 UTC 
Is name resolution slow in the case that you describe in comment 4? That means wlan device plugged but not connected to an access point?

Or is it slow as soon as you get a wlan connection?

Please attach all /etc/sysconfig/network/ifcfg-*
Comment 8 Michael Stather 2005-11-25 13:39:22 UTC 
The problem occurs without the W-LAN adapter attached. Sorry, perhaps I should have written this before.
Comment 9 Michael Stather 2005-11-25 13:40:36 UTC 
Created attachment 58744 [details]
one config file
Comment 10 Michael Stather 2005-11-25 13:45:46 UTC 
Created attachment 58747 [details]
the w-lan card config file
Comment 11 Michael Stather 2005-11-25 13:46:41 UTC 
I attached the config files.
What I noticed, the file for the W-LAN interface is readable only by root. I don´t know if this is intended (perhaps it is because of the WEP key in it) but I just noticed it.
Comment 12 Christian Zoz 2005-11-25 15:23:05 UTC 
I have no idea up to now. Your setup looks sane so far.

The name resolution is slow if the wlan device is not attached.
And is it fast as soon as the wlan device 
- is attached?
- is attached and has a working connection to an access point?

Did you enable the firewall?
Comment 13 Michael Stather 2005-11-25 18:44:10 UTC 
Plugging in the W-LAN adapter without a network doesn´t help. If I´m in a WLAN the name resolution works instantly, it´s only the problem here within my network. And before I set up the WLAN-interface everything worked fine.
Comment 14 Christian Zoz 2005-11-29 15:27:38 UTC 
Did you enable the firewall?

Does it work if you call 'rcnascd restart' after you removed the wlan device?

Also please provide the information like in comment 3 and 4 but when the wlan interface has a working connection.
Comment 15 Michael Stather 2006-02-04 23:32:24 UTC 
I changed my network settings and now I can´t reproduce this any more. I think you can close the bug, if it happens again I´ll reopen.
Comment 16 Christian Zoz 2006-02-06 10:07:45 UTC 
cannot see a bug here