Version: 3.2.0 (using KDE 3.2.90 (CVS >= 20040117), yes) Compiler: gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7) OS: Linux (i686) release 2.4.24 Pretty simple, tcpdump shows konqueror only ever seems to lookup wpad.my.work.domain when looking for a WPAD file - even when I'm sitting in a hotel room with a completely different default domain (or search domain) defined within /etc/resolv.conf. It's as if something in konqueror hardwired "my.work.domain" during the install of KDE, and it won't stop using it. It appears to send its queries to the new DNS servers defined within /etc/resolv.conf, but it doesn't change the domain name it should be putting onto the end of "wpad." Every time WPAD is actioned on, shouldn't it re-check what all the DNS-related settings are? Jason
I've re-installed my laptop from RH8 (where this bug originally occurred) to Fedora, and have installed from the semi-official KDE-3.2.0 RPMs. This bug still occurs. I have just upgraded to 3.2.1 and it's still there. It's pretty bad actually. Many times a day (4-5 times an hour?) my entire KDE desktop freezes: the mouse moves and icons appear to hightlight correctly, but clicking on anything has no affect. I think its' related to this issue, as tcpdump shows time and time again my system doing DNS lookups for "wpad.my.work.domain" even though I BOOTED this laptop on another network (i.e. /etc/resolv.conf does *not* contain "my.work.domain"). In fact it just happened while I was writing this. Suddenly I couldn't type in this form, I managed to jump to the virtual desktop where I had tcpdump running, and I can see "wpad" lookups occurring. After 1-2 minutes of looking up all sorts of pertubations of my work domain it gave up - then the popup appeared saying "cannot automatically configure proxy settings" and konqueror became responsive again. I know I could go to manual proxy settings, but that's the whole beauty of WPAD - I don't have to reconfigure every time I go home/work. I know this is a KDE issue as it doesn't occur when I login under GNOME. It's so bad that I cannot use konqueror - nothing like starting up konqueror (or my favorite: knewticker) to trigger 1-2 mins of hanging... Is there anything I can do to diagnose where the problem lies? Thanks Jason
I got here trying to report this exact bug. Proxy autodiscovery *should* use the DNS domain given by the local DHCP server, or at least try http://wpad/wpad.dat -- but instead it uses the FQDN from /etc/hosts. This may be nominally correct, but it's effectively not what is needed for operating with an automatically discovered proxy. I found the bug when I changed branches, and my browser kept on sending queries to the proxy server at the other branch, even though I'm on a completely different DHCP server ...
I agree. Just ask for http://wpad/wpad.dat and it's done. If not found, it could try to determine the domain by /etc/hosts.
Yes. I think KDE's concept of "default domain" is the domain present when KDE was initially installed! That's certainly not a good idea. It needs to follow what "the network" is telling it - i.e. via /etc/resolv.conf, etc. http://wpad/wpad.dat might do the same thing
is this still an issue with kde 3.5.4?
Is this still an issue with kde 3.5.9 or 4.0.5?
The bug is present in KDE 3.5.9 (as per Ubuntu): # cat /etc/resolv.conf search otherdomain.net nameserver 192.168.0.1 # cat /etc/hosts 127.0.0.1 localhost 127.0.1.1 foobar.domain.org foobar # hostname foobar # hostname -f foobar.domain.org # tcpdump host 192.168.0.1 09:41:19.960172 IP 192.168.0.9.60377 > 192.168.0.1.53: 43026+ A? wpad.domain.org. (36) 09:41:19.960808 IP 192.168.0.1.53 > 192.168.0.9.60377: 43026 NXDomain 0/1/0 (102) 09:41:19.961275 IP 192.168.0.9.50162 > 192.168.0.1.53: 32664+ SOA? domain.org. (31) 09:41:19.962101 IP 192.168.0.1.53 > 192.168.0.9.50162: 32664 1/5/5 SOA (272) The domain from /etc/hosts is used, rather than the domain in /etc/resolv.conf.
Just to be sure, have you also tested your configuration with another network program, for example, telnet or ssh or another one that uses the libc function gethostbyname()? I've tested a similar configuration and kde and ssh works as expected, using the libc dns functions, which first take a look at /etc/hosts, and if the host is found there, then it is used, otherwise it continues with the remote dns configured in /etc/resolv.conf. To make it work as desired, please try to comment the line # 127.0.1.1 foobar.domain.org foobar in /etc/hosts and try again. Does it makes the desired magic?
I think thing have improve since I reported this over 4 years ago (owch!) Right now I'm at home with my FC8 laptop running kde-3.5.9. If I do "nslookup wpad" I resolve to my home WPAD server, which in turn tells browsers to use my home proxy server. When I start konqueror (set to "automatically detect proxy settings"), wireshark shows it doing a DHCP INFORM query (which fails as I don't use DHCP for this function), and then starts accessing URLs via the home proxy. I don't see a WPAD.domain lookup, nor the download of the PAC file - but it must have done that already and cached it? No other way it could have discovered it. Anyway, one little bug is that the DHCP INFORM fails, and konqueror reports via a popup that it "could not find a usable proxy configuration script" - even though it then starts talking to a proxy server (ie it did find one). Sound like the "automatic proxy" code assumes everyone uses DHCP INFORM instead of either that or WPAD PAC lookups?
How much of this is fixed with current proxy stuff, and is this actually a duplicate?
I can confirm this problem by simply looking at the code at kio/misc/kpac/discovery.cpp. Unless you completely log out of KDE and log back in the original domain/host used to retrieve the proxy configuration file will not be changed. Will see what I can do about fixing it...
*** Bug 100626 has been marked as a duplicate of this bug. ***
Git commit cb9e7b1beb31169d23dbad15717cc34b561870e8 by Dawit Alemayehu. Committed on 28/04/2011 at 20:27. Pushed by adawit into branch 'master'. - Connect to Solid::Networking::Notifier's shouldDisconnect signal and reset the current PAC settings so that a new one will be fetched on the next request. - Changed the Discovery class to use QHostInfo::localDomainName to retrieve DNS domain information instead of using the uname+gethostname+gethostbyname combination. - Use QLatin1String for literal text in script.cpp as appropriate. BUG: 73765 FIXED-IN: 4.7 M +1 -1 kio/misc/kpac/CMakeLists.txt M +26 -33 kio/misc/kpac/discovery.cpp M +3 -4 kio/misc/kpac/discovery.h M +41 -18 kio/misc/kpac/proxyscout.cpp M +1 -0 kio/misc/kpac/proxyscout.h M +22 -20 kio/misc/kpac/script.cpp http://commits.kde.org/kdelibs/cb9e7b1beb31169d23dbad15717cc34b561870e8
I'm using 4.8.3 and am seeing what appears to be this same problem. I have no proxy-related options in my DHCP configuration so I'm dependent upon the DNS. When I log into my KDE session, my local DNS server sees: Jun 17 00:29:20 named: client 192.168.1.20#36905: query: wpad.ggnet.umn.edu IN A + Jun 17 00:29:20 named: client 192.168.1.20#36905: query: wpad.ggnet.umn.edu IN AAAA + Jun 17 00:29:20 named: client 192.168.1.20#51592: query: wpad.ggnet.umn.edu.ggnet.umn.edu IN A + Jun 17 00:29:20 named: client 192.168.1.20#51592: query: wpad.ggnet.umn.edu.ggnet.umn.edu IN AAAA + Jun 17 00:29:20 named: client 192.168.1.20#33250: query: wpad.ggnet.umn.edu.nts.umn.edu IN A + Jun 17 00:29:20 named: client 192.168.1.20#33250: query: wpad.ggnet.umn.edu.nts.umn.edu IN AAAA + Jun 17 00:29:20 named: client 192.168.1.20#39662: query: wpad.ggnet.umn.edu.entropyacademy.com IN A + Jun 17 00:29:20 named: client 192.168.1.20#39662: query: wpad.ggnet.umn.edu.entropyacademy.com IN AAAA + Jun 17 00:29:20 named: client 192.168.1.20#50083: query: umn.edu IN SOA + First of all, this isn't my domain when at home on the proxy, it is only the first domain listed in my resolv.conf search path: # Generated by resolvconf search ggnet.umn.edu nts.umn.edu entropyacademy.com nameserver 192.168.1.254 and it isn't in my /etc/hosts: 127.0.0.1 ssb-lap localhost.localdomain localhost ::1 ssb-lap localhost6.localdomain6 localhost6 ::1 localhost I think I've had this problem for quite some time now (I have been seeing the popup): Could not find a usable proxy configuration script but have not taken the time to try to figure out what was happening until today. On the other hand, here's what shows up on my DNS server when I start firefox (set to automatic proxy detection): Jun 17 00:35:14 named: client 192.168.1.20#57495: query: wpad.ggnet.umn.edu IN A + Jun 17 00:35:14 named: client 192.168.1.20#57495: query: wpad.ggnet.umn.edu IN AAAA + Jun 17 00:35:14 named: client 192.168.1.20#45086: query: wpad.nts.umn.edu IN A + Jun 17 00:35:14 named: client 192.168.1.20#45086: query: wpad.nts.umn.edu IN AAAA + Jun 17 00:35:14 named: client 192.168.1.20#55384: query: wpad.entropyacademy.com IN A + Jun 17 00:35:14 named: client 192.168.1.20#55384: query: wpad.entropyacademy.com IN AAAA +