Re: [Cooker] Broken localhost resolution, zeroconf and drakconnect
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Frederic Lepied wrote: The only hack to achieve something like choosing a hostname that will be valid on your network, is to use zeroconf by setting a hostname in .local. What about if your server supports Dynamic DNS (ie DHCP server makes entries in your DNS server)? And what about if the DHCP server is set to assign IPs according to MAC address and the DNS server has static mappings for IP to hostname (effectively mapping a name to a MAC address)? Yes it's supported but I wanted to say that without network infrastructure you can't choose your hostname. I still think there is a problem here, since the only way to set your hostname would be by not using the hostname from dhcp (ie setting it in /etc/sysconfig/...), and the only way to resolve the name is with tmdns. But, this does not mean that the name needs to be hardcoded in /etc/tmdns.conf, since tmdns will always use `hostname`.local, which should be right by the time tmdns starts up. The advantage is that the user does not have to worry about the tmdns config if something else changes? Regards, Buchan - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+Z2qYrJK6UGDSBKcRAgFeAJ9kYS+Ogp7B4V5PtaZ9KV93uD1tugCfZrHd y+SlhfVydD9TnBQKwRNcOuo= =7Z2w -END PGP SIGNATURE-
Re: [Cooker] Broken localhost resolution, zeroconf and drakconnect
On Mon, Mar 03, 2003 at 07:43:15PM +0200, Buchan Milne wrote: Sorry, just a query here, did you run 'host `localhost`', or 'host `hostname`'. If 'host `hostname`' resolves, GNOME should work. If it does not, GNOME should complain. That's not really true. Again the host command *ONLY* queries nameservers. It does not pay any attention to the /etc/hosts file. So more accurately if: getent hosts `hostname` spits out an IP then GNOME will work. -- Ben Reser [EMAIL PROTECTED] http://ben.reser.org America does not go abroad in search of monsters to destroy. She is the well-wisher to the freedom and independence of all. She is the champion only of her own. -- John Quincy Adams, July 4th, 1821
Re: [Cooker] Broken localhost resolution, zeroconf and drakconnect
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ben Reser wrote: On Mon, Mar 03, 2003 at 07:43:15PM +0200, Buchan Milne wrote: Sorry, just a query here, did you run 'host `localhost`', or 'host `hostname`'. If 'host `hostname`' resolves, GNOME should work. If it does not, GNOME should complain. That's not really true. Again the host command *ONLY* queries nameservers. It does not pay any attention to the /etc/hosts file. So more accurately if: getent hosts `hostname` spits out an IP then GNOME will work. I think I asked Greg to test both of those. The thing I wanted to confirm here was whether he was using `hostname` or `localhost` as the name to attempt to resolve. D'Oh, looking at my mail, that was the one I forgot :-(. Greg, do you have a working (ie broken) setup at present you can test this on? Regards, Buchan - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+ZHCurJK6UGDSBKcRAuX+AJ9anzq126uFaPzkyuL/zf/4y6mTzQCeLbS7 mMhZzHGQVCPzMMapu0RqJgc= =ZUv4 -END PGP SIGNATURE-
Re: [Cooker] Broken localhost resolution, zeroconf and drakconnect
On Tuesday 04 March 2003 04:23 am, Buchan Milne wrote: Ben Reser wrote: On Mon, Mar 03, 2003 at 07:43:15PM +0200, Buchan Milne wrote: Sorry, just a query here, did you run 'host `localhost`', or 'host `hostname`'. If 'host `hostname`' resolves, GNOME should work. If it does not, GNOME should complain. That's not really true. Again the host command *ONLY* queries nameservers. It does not pay any attention to the /etc/hosts file. So more accurately if: getent hosts `hostname` spits out an IP then GNOME will work. I think I asked Greg to test both of those. The thing I wanted to confirm here was whether he was using `hostname` or `localhost` as the name to attempt to resolve. D'Oh, looking at my mail, that was the one I forgot :-(. Greg, do you have a working (ie broken) setup at present you can test this on? Yes, I have a machine to test, but, unfortuantely, I am a little short on time until later this evening, if you can respond right away, I might be abler to get it done this morning, I am UTC -5:00. What specifically do you want tested. I will reiterate that I have already found that with default network settings accepted during install, host `hostname` does not resolve but GNOME does not complain. Only after running drakconnect does GNOME start complaining, and host `hostname` still does not resolve. I don't think I tested host `localhost` -- Greg
Re: [Cooker] Broken localhost resolution, zeroconf and drakconnect
On Tuesday 04 March 2003 04:23 am, Buchan Milne wrote: Ben Reser wrote: On Mon, Mar 03, 2003 at 07:43:15PM +0200, Buchan Milne wrote: Sorry, just a query here, did you run 'host `localhost`', or 'host `hostname`'. If 'host `hostname`' resolves, GNOME should work. If it does not, GNOME should complain. That's not really true. Again the host command *ONLY* queries nameservers. It does not pay any attention to the /etc/hosts file. So more accurately if: getent hosts `hostname` spits out an IP then GNOME will work. I think I asked Greg to test both of those. The thing I wanted to confirm here was whether he was using `hostname` or `localhost` as the name to attempt to resolve. D'Oh, looking at my mail, that was the one I forgot :-(. Greg, do you have a working (ie broken) setup at present you can test this on? Okay, I just confirmed that in a stock 9.1 install accepting the network defaults in a dhcp environment GNOME starts without error. [EMAIL PROTECTED] greg]$ host `hostname` ;; Got SERVFAIL reply from 127.0.0.1, trying next server ;; Got SERVFAIL reply from 127.0.0.1, trying next server Host dhcppc5 not found: 3(NXDOMAIN) [EMAIL PROTECTED] greg]$ host localhost ;; Got SERVFAIL reply from 127.0.0.1, trying next server ;; Got SERVFAIL reply from 127.0.0.1, trying next server localhost has address 127.0.0.1 If I run drakconnect to attempt to set a hostname and then reboot, GNOME pukes. [EMAIL PROTECTED] greg]$ host `hostname` ;; Got SERVFAIL reply from 127.0.0.1, trying next server ;; Got SERVFAIL reply from 127.0.0.1, trying next server Host dhcppc5 not found: 3(NXDOMAIN) [EMAIL PROTECTED] greg]$ host localhost ;; Got SERVFAIL reply from 127.0.0.1, trying next server ;; Got SERVFAIL reply from 127.0.0.1, trying next server localhost has address 127.0.0.1 [EMAIL PROTECTED] greg]$ getent hosts `hostname` #no output is returned [EMAIL PROTECTED] greg]$ cat /etc/hosts 127.0.0.1 localhost 192.168.0.6 cooker Somehow, running drakconnect changes a setting somewhere, that I cannot (or have not been able to) find, that breaks localhost resolution. You'll note that an entry has been made to /etc/hosts for the hostname I chose when I ran drakconnect, yet that name has not been set. Could this be causing the GNOME problem. The ip address assigned to this machine has one name in /etc/hosts, yet the machine hostname is different (dhcppc5). Hold on.. I edited /etc/hosts and rebooted. Nope, GNOME still pukes. Anything specific you want tested more I'll have to do after work tonight, so let me know. -- Greg
Re: [Cooker] Broken localhost resolution, zeroconf and drakconnect
On Tuesday 04 March 2003 09:01 am, Greg Meyer wrote: Somehow, running drakconnect changes a setting somewhere, that I cannot (or have not been able to) find, that breaks localhost resolution. You'll note that an entry has been made to /etc/hosts for the hostname I chose when I ran drakconnect, yet that name has not been set. Could this be causing the GNOME problem. The ip address assigned to this machine has one name in /etc/hosts, yet the machine hostname is different (dhcppc5). Hold on.. I edited /etc/hosts and rebooted. Nope, GNOME still pukes. Anything specific you want tested more I'll have to do after work tonight, so let me know. I just added an entry to /etc/hosts so it looks like this 127.0.0.1 localhost 192.168.0.5 dhcppc5 GNOME now starts without error. So GNOME is definitely looking at teh /etc/hosts file for resolution, while the problems with host`localhost` not resolving are coming from somewhere else. Why wouldn;t GNOME have a problem with default settings before drakconnect is run. Am I dense by missing something obvious? -- Greg
Re: [Cooker] Broken localhost resolution, zeroconf and drakconnect
Greg Meyer [EMAIL PROTECTED] writes: With all the discussion on Cooker about broken localhost resolution and the new zeroconf setup, I took it upon myself to install Friday night's Cooker about 14 times to test various scenarios. Since Buchan has been in the center of this discussion, I conferred with him and he suggested I spam Frederic and Florin with this. So guys, if you are not the right people, blame Buchan, and then please forward this on to the appropriate individual. I started looking into this when I noticed that I could not reset my hostname. When accepting the defaults during installation, I get an assigned hostname that is pretty dumb (dhcppc[x]). I know many home users will want to be able to set the hostname to something fun, like Jock or Trusty, and will run drakconnect to try and change it. Well, running drakconnect not only does not change it, it breaks localhost resolution for GNOME. I therefore set out on my quest. I have attached two files (also provided links in case you guys get attachments stripped for some reason). One is a summary of my experiments, the other is a tarball of the output files created during the process. I hope you guys can use this to fix whatever the problem is. I obviously cannot test all network configurations, but mine is typical of many home users. I don't know enough to really be helpful in actually fixing anything, but I hope my investigation gives enough evidence to lead you to the problem quickly. Some quick observations 1) On my network with dhcp, running drakconnect broke localhost resolution for GNOME. GNOME started without error usnig default settings. As soon as I ran drakconnect, the next time GNOME started, it could not resolve localhost. 2) The only times that host `localhost` resolved successfully was when static addressing was used. Let me know if you need anything else. I'd be happy to run the test again on a specific setup to provide more info if necessary, although I obviously don't want to do all of them again. First that's the normal behaviour to be able to set the hostname only in static IP mode. You can't choose by yourself a name and have it known by the other hosts on the network if the IP is given by DHCP. The only hack to achieve something like choosing a hostname that will be valid on your network, is to use zeroconf by setting a hostname in .local. -- Fred - May the source be with you
Re: [Cooker] Broken localhost resolution, zeroconf and drakconnect
On Monday 03 March 2003 12:17 pm, Frederic Lepied wrote: First that's the normal behaviour to be able to set the hostname only in static IP mode. You can't choose by yourself a name and have it known by the other hosts on the network if the IP is given by DHCP. The only hack to achieve something like choosing a hostname that will be valid on your network, is to use zeroconf by setting a hostname in .local. Why is this possible in prior releases then? I could always set the host name and still obtain a dhcp address. I am making a big issue about this because a lot of people on samll/home networks that don't have dns are going to be upset that they cannot set the hostname of their machine. The other OS allows this and previous versions of Mandrake did too. Since zeroconf is a alternative to UPnP, isn't the feature set supposed to be comparable? Also, what about drakconnect breaking localhost resolution for GNOME? -- Greg
Re: [Cooker] Broken localhost resolution, zeroconf and drakconnect
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Greg Meyer wrote: 2) The only times that host `localhost` resolved successfully was when static addressing was used. Sorry, just a query here, did you run 'host `localhost`', or 'host `hostname`'. If 'host `hostname`' resolves, GNOME should work. If it does not, GNOME should complain. Buchan - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+Y5QyrJK6UGDSBKcRAu07AJ9mKhnDYY1t5JmV4IyhXoXphSLYdwCgmEWm sH6efvPTAOKGKb+FPm6LMAk= =zx7o -END PGP SIGNATURE-
Re: [Cooker] Broken localhost resolution, zeroconf and drakconnect
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Frederic Lepied wrote: Greg Meyer [EMAIL PROTECTED] writes: First that's the normal behaviour to be able to set the hostname only in static IP mode. You can't choose by yourself a name and have it known by the other hosts on the network if the IP is given by DHCP. Why not? The dhcp request includes the hostname requested. The only hack to achieve something like choosing a hostname that will be valid on your network, is to use zeroconf by setting a hostname in .local. What about if your server supports Dynamic DNS (ie DHCP server makes entries in your DNS server)? And what about if the DHCP server is set to assign IPs according to MAC address and the DNS server has static mappings for IP to hostname (effectively mapping a name to a MAC address)? Regards, Buchan - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+Y5VErJK6UGDSBKcRAsLfAKCFOidQ8ea73qymojJBSuN9jDwdZACfWuAA HBghvqUHfwOHwKzH+wyGIHg= =cwi+ -END PGP SIGNATURE-
Re: [Cooker] Broken localhost resolution, zeroconf and drakconnect
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Greg Meyer wrote: On Monday 03 March 2003 12:17 pm, Frederic Lepied wrote: Why is this possible in prior releases then? I could always set the host name and still obtain a dhcp address. I am making a big issue about this because a lot of people on samll/home networks that don't have dns are going to be upset that they cannot set the hostname of their machine. The other OS allows this and previous versions of Mandrake did too. Since zeroconf is a alternative to UPnP, isn't the feature set supposed to be comparable? Well, that only really worked because people added entries to /etc/hosts Also, what about drakconnect breaking localhost resolution for GNOME? I think Fred may have fixed it in the latest initscripts, you may want to test. Regards, Buchan - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+Y5XarJK6UGDSBKcRApXPAJ9vRm4H+JooZQWjyw1GFkcEQ1pLiACgq4jY tWX51umIAHAc7t4gwMtt6Tc= =WlDa -END PGP SIGNATURE-
Re: [Cooker] Broken localhost resolution, zeroconf and drakconnect
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Buchan Milne wrote: Also, what about drakconnect breaking localhost resolution for GNOME? I think Fred may have fixed it in the latest initscripts, you may want to test. Make that dhcp ... - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+Y5lHrJK6UGDSBKcRAmgQAJwK3jRzI/aqo5D4j/xaexoxll+wEQCfXv9f pHtwscXJ/0C2RO2CXZMx6oI= =aylb -END PGP SIGNATURE-
Re: [Cooker] Broken localhost resolution, zeroconf and drakconnect
Buchan Milne [EMAIL PROTECTED] writes: Frederic Lepied wrote: Greg Meyer [EMAIL PROTECTED] writes: First that's the normal behaviour to be able to set the hostname only in static IP mode. You can't choose by yourself a name and have it known by the other hosts on the network if the IP is given by DHCP. Why not? The dhcp request includes the hostname requested. The only hack to achieve something like choosing a hostname that will be valid on your network, is to use zeroconf by setting a hostname in .local. What about if your server supports Dynamic DNS (ie DHCP server makes entries in your DNS server)? And what about if the DHCP server is set to assign IPs according to MAC address and the DNS server has static mappings for IP to hostname (effectively mapping a name to a MAC address)? Yes it's supported but I wanted to say that without network infrastructure you can't choose your hostname. -- Fred - May the source be with you
Re: [Cooker] Broken localhost resolution, zeroconf and drakconnect
On Monday 03 March 2003 12:43 pm, Buchan Milne wrote: Greg Meyer wrote: 2) The only times that host `localhost` resolved successfully was when static addressing was used. Sorry, just a query here, did you run 'host `localhost`', or 'host `hostname`'. If 'host `hostname`' resolves, GNOME should work. If it does not, GNOME should complain. There were times when host `hostname` did not resolve, yet GNOME did not complain. This only occurred if the network defaults were accepted on install and drakconnect WAS NOT run. As soon as drakconnect was run, whther fromt eh summary screen or post install, GNOME would complain. -- Greg
Re: [Cooker] Broken localhost resolution, zeroconf and drakconnect
On Sunday 02 March 2003 08:43 am, Greg Meyer wrote: Somehow, I missed the output for step 10. I added it to output.tgz and reposted. http://cybercfo.gkmweb.com/network-test.summary http://cybercfo.gkmweb.com/output.tgz -- Greg
