Steve Pauly wrote:
Greetings,
I have a problem involving the diald as installed by Yast on my 5.3 system, and >>>>local net<<<<.
Before diald, when I made a telnet connection to one of my local ethernet boxes, the telnet connection was made instantaneously.
Now, diald must start and connect before telnet can complete, even though no internet telnet host was involved.
My /etc/hosts file has the local net boxes in it. /etc/host.conf looks okay too. So, I don't think dns is/should be involved...
Anyone know how to let telnet work locally without diald kicking on?
Thanks.
Steve.
Ok Steve, (listen up S.u.S.E. !!!!!!!!!!!!) here is the problem which has caused myself much loss of hair. I only solved this problem as of yesterday morning - after more than a week of reading/testing/posting/pleading for an answer. The problem is in /etc/resolv.conf If you use the default configuration of SuSE you will have the problem you describe because DNS look-ups will poll listed DNS servers _BEFORE_ polling /etc/hosts This will cause diald to connect for everything, and I mean everything. Even if you are just using ip's instead of names it will cause diald to start a ppp link even for local traffic. Here is the fix. In /etc/resolv.conf add the following line (please correct me if my syntax is wrong, but I have no documentation on this -- anyway it works) order hosts, 204.203.235.3, 192.220.251.1 #<-- replace with your DNS Of course you will need to have your nameservers and domain listed in subsequent lines. Adding this line immediately solved my problem. I hope this is your solution as well. Maybe SuSE will add this in the next dist. As a side note I found this answer in "Linux System Administration Handbook" by Mark F. Komarinski and Cary Collet. My sweet wife gave me this book as a birthday gift yesterday. :-) -- Ben Messinger Linux user #79,342 (Better late than never!) - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e