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. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
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
Ben, Thanks for the response. I must be doing something different than you because my system still invokes diald before completing local telnets. Basically, diald makes working locally >>>>useless<<<<. When I turned diald off, all is okay... Here's my /etc/resolv.conf after I made your change. domain SciFi.com order hosts, 192.168.136.1 nameserver 192.168.136.1 See anything that I need to change to get diald to work right? Finally, how do you get a man page on resolv.conf under SuSE? man resolv.conf does not do it, neither does info resolv.conf... BTW, man resolv.conf under FreeBSD 2.2.7 does work!?! Thanks. Steve. On Sun, 29 Nov 1998, Ben Messinger wrote:
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.
The problem is in /etc/resolv.conf
[ ...]
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.
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
I've been running diald under both SuSE 5.2 and SuSE 5.3 since July and I'm not seeing this sort of problem. When I telnet to another machine on my local network I don't see diald being started up. Here's my resolv.conf file: earch home.lan nameserver NNN.NNN.NNN.NNN nameserver NNN.NNN.NNN.NNN The two name servers are the primary and secondary nameservers for my ISP respectively. My small home LAN consists of 4 system which are in a domain I call "home.lan". I'm using Linux's built-in firewalling and IP masquerading capabilities as well on my server so my home network can share a dialup PPP connection to my ISP. Steve Pauly wrote:
Ben,
Thanks for the response.
I must be doing something different than you because my system still invokes diald before completing local telnets. Basically, diald makes working locally >>>>useless<<<<. When I turned diald off, all is okay...
Here's my /etc/resolv.conf after I made your change.
domain SciFi.com order hosts, 192.168.136.1 nameserver 192.168.136.1
See anything that I need to change to get diald to work right?
Finally, how do you get a man page on resolv.conf under SuSE? man resolv.conf does not do it, neither does info resolv.conf...
BTW, man resolv.conf under FreeBSD 2.2.7 does work!?!
Thanks.
Steve.
On Sun, 29 Nov 1998, Ben Messinger wrote:
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.
The problem is in /etc/resolv.conf
[ ...]
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.
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Tony -- Anthony.Schlemmer@gte.net - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (3)
-
Anthony.Schlemmer＠gte.net -
bmessin＠3-cities.com -
stevep＠brokersys.com