Re: [SLE] (Revisited) Works in Windoze, NOT in SuSE!?!?!?!?!?!?
----- Original Message ----- From: Basil Chupin Sent: 9/28/2003 4:56:34 AM
bernd@covenantmail.net wrote:
HELP!!! <snip>
Here's what I think is going on. I am now getting errors from the output of wvdial (using the tried and true -saved- copy of wvdial.conf). I am told that there are errors with the name servers and www.suse.de can't be found!?! So now I can't use wvdial or kinternet to connect. <snip> PLEASE Save Me!!! <snip>
I'm going to cut to the chase here, because I am using windoze and my ISP's webmail. Basil, I have already done everything, several times, that you stated in your e-mail that I am now replying. I sincerely appreciate the suggestions you and others have provided in the past. I have used, and referred to them often. This problem is entirely new, and has nothing to do with my length of connection problem. I can't connect at all! ****Problem is as stated in my previous e-mail above. I can't use -anything- to connect to my ISP from linux. I get the errors regarding my name servers, and can't access anything!!! No e-mail, no web, ftp, ...!!! Regarding the name servers, all I have ever done is yast/modem (for use with kinternet), wvdial.conf (for use with wvdial), options (used by pppd), and kppp. My dns settings are always auto, as my ISP provides them during the connect sequence. I have not messed with dhcp as John suggested that I do. I wouldn't know what to do there. I have dumped all my yast modem settings, wvdial.conf, and started fresh with system defaults (which has worked in the past, except for connection length problems). Yet the dns problem still remains. What on earth have I screwed with to mess up the auto dns settings outside of wvdial.conf and yast/modem??? I'm about ready to backup /home, toast it all, and reinstall SuSE from scratch!!!!! Maybe that would take care of everything!?! Sorry! Bernd
On Sunday 28 September 2003 19:35 pm, wrote:
----- Original Message ----- From: Basil Chupin Sent: 9/28/2003 4:56:34 AM
bernd@covenantmail.net wrote:
HELP!!!
<snip>
Here's what I think is going on. I am now getting errors from the output of wvdial (using the tried and true -saved- copy of wvdial.conf). I am told that there are errors with the name servers and www.suse.de can't be found!?! So now I can't use wvdial or kinternet to connect.
<snip>
PLEASE Save Me!!!
<snip>
I'm going to cut to the chase here, because I am using windoze and my ISP's webmail.
Basil, I have already done everything, several times, that you stated in your e-mail that I am now replying. I sincerely appreciate the suggestions you and others have provided in the past. I have used, and referred to them often. This problem is entirely new, and has nothing to do with my length of connection problem. I can't connect at all!
****Problem is as stated in my previous e-mail above. I can't use -anything- to connect to my ISP from linux. I get the errors regarding my name servers, and can't access anything!!! No e-mail, no web, ftp, ...!!!
Could you clarify the above? Can you 'connect' to your ISP (the act of getting the modem to connect and then login to your ISP) ?? So maybe you can connect but then nothing seems to work? Your statement above about no email, no web, to ftp etc... smacks of an ifconfig problem (network setup) rather than any problem with the modem. It's not clear from what you have stated. You say you 'can't connect at all'... If the modem doesn't connect, then you can't expect ftp,web, etc... which leads me to believe that you *are* connecting but not getting much after that.
Regarding the name servers, all I have ever done is yast/modem (for use with kinternet), wvdial.conf (for use with wvdial), options (used by pppd), and kppp. My dns settings are always auto, as my ISP provides them during the connect sequence. I have not messed with dhcp as John suggested that I do. I wouldn't know what to do there.
I have dumped all my yast modem settings, wvdial.conf, and started fresh with system defaults (which has worked in the past, except for connection length problems). Yet the dns problem still remains.
What on earth have I screwed with to mess up the auto dns settings outside of wvdial.conf and yast/modem???
I'm about ready to backup /home, toast it all, and reinstall SuSE from scratch!!!!! Maybe that would take care of everything!?!
Sorry!
Bernd
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 09/28/03 19:54 + +----------------------------------------------------------------------------+ "Make yourself into a sheep, and you'll meet a wolf nearby. -- Russian proverb"
bernd@covenantmail.net wrote:
----- Original Message ----- From: Basil Chupin Sent: 9/28/2003 4:56:34 AM
bernd@covenantmail.net wrote:
HELP!!!
<snip>
Here's what I think is going on. I am now getting errors from the output of wvdial (using the tried and true -saved- copy of wvdial.conf). I am told that there are errors with the name servers and www.suse.de can't be found!?! So now I can't use wvdial or kinternet to connect.
<snip>
PLEASE Save Me!!!
<snip>
I'm going to cut to the chase here, because I am using windoze and my ISP's webmail.
Basil, I have already done everything, several times, that you stated in your e-mail that I am now replying. I sincerely appreciate the suggestions you and others have provided in the past. I have used, and referred to them often. This problem is entirely new, and has nothing to do with my length of connection problem. I can't connect at all!
****Problem is as stated in my previous e-mail above. I can't use -anything- to connect to my ISP from linux. I get the errors regarding my name servers, and can't access anything!!! No e-mail, no web, ftp, ...!!!
Regarding the name servers, all I have ever done is yast/modem (for use with kinternet), wvdial.conf (for use with wvdial), options (used by pppd), and kppp. My dns settings are always auto, as my ISP provides them during the connect sequence. I have not messed with dhcp as John suggested that I do. I wouldn't know what to do there.
I have dumped all my yast modem settings, wvdial.conf, and started fresh with system defaults (which has worked in the past, except for connection length problems). Yet the dns problem still remains.
What on earth have I screwed with to mess up the auto dns settings outside of wvdial.conf and yast/modem???
I'm about ready to backup /home, toast it all, and reinstall SuSE from scratch!!!!! Maybe that would take care of everything!?!
Sorry!
Bernd
Well, I have to agree with Bruce also that it is not really your modem that is causing you all the hassles; nad have to agree with Joe Morris as well that you need a break from all of this - we can't have you going around the twist on us :-). And I have to also agree with your what you say in your penultimate paragraph: re-install SuSE. I think this is the only way out because you will then get back to a known (and fresh) starting point. Re-install SuSE bearing in mind what I said about configuring your modem during installation. Also, I suggest that you only use kppp to access your ISP. Again, this way thre is only one 'variable' to fiddle with to get you going. Forget about wvdial unless there are compelling reasons for you to use it. If kppp cannot be made to work for you we can then try wvdial - but we don't want to have both being used to confuse the issue. If it makes you feel any better, not being able to get past 50+ minutes connected to your ISP is only a small inconvenience :-) - I just spent the whole day re-installing my SuSE after it had a FATAL "crash", the first one in some 5 years of using Linux; there was no way I could get into SuSE to recover :-( so a complete re-install was the order of the day. Fortunately all of my downloads and HOME are copied on the second HD so I only lost 2 days' worth of e-mails. Such is life. Cheers. -- Hire teenagers while they still know everything.
THANKS SO VERY VERY MUCH TO EVERYONE!!!!!!!!! Your help and dedication in following this thread, and its variants, since the beginning of August, is so GREATLY appreciated!!! I now know considerably more about my system than I ever could have without such a peevish problem. In a way I'm glad I didn't 'go around the bend' earlier. I certainly wouldn't have learned as much. Yet, going around the bend is exactly what solved the problem. Unfortunately, we'll never know what the 'real' cause of the problem was. As you could tell with my last few e-mails, I just lost it. I hate working in windoze with such a passion, that 2 days without my SuSE was extremely toooo much. I formatted and repartitioned the entire drive(which was a good thing to do anyway, because I was in need of changing partition sizes). I then reinstalled fresh from cd's(apparently you too, Basil!), and tried my modem. Oh gad!!! I was still having dns problems. I then took a look at the preprogrammed init string my modem was using. Wow, how screwy! It was preprogrammed to use something extremely foreign. I then tried a very simple init I had tried before, init1: ATZ, init2: AT&F1. That got me back to the point where I could properly connect. On my first test I was expecting to be dropped at the usual max time of 59.4 minutes. As I reached 60 minutes, I started celebrating. As my connection time continued, I started downloading KDE updates. I was able to stay connected for 5 hours!!!!!!!!!!!!!!!!!!!!!! Just like I had been in 'that other os'. Ran another test and kept downloading. Again, 5 whole hours, before my ISP dropped me!!!!!!!!!!!! (I'll deal with them later, he says with an evil grin!) 5 hours!!!!!!! WOW!!!!!!!!!! Well, now you know what I've been doing ALL this week!! I've been making use of my new found connection time. It has taken me a while to set up all that I wanted of the kde updates, so kmail was out until this evening. I surely wasn't going to go through windoze to e-mail you guys back. 941 e-mails later, I'm finally able to respond. ************************************************** YOU GUYS ARE SUPER!!! NOWHERE ELSE ON EARTH COULD I FIND TECH SUPPORT THIS GOOD, AND SOOOO DEDICATED AT HELPING OUT, AT ANY PRICE!!! THANK YOU ALL!!! ************************************************** Yours so very sincerely, Bernd -- "If you want to build a ship, don't drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea." Antoine de St. Exupery
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 03 October 2003 00:46, Bernd Koepsell wrote:
THANKS SO VERY VERY MUCH TO EVERYONE!!!!!!!!!
Your help and dedication in following this thread, and its variants, since the beginning of August, is so GREATLY appreciated!!!
<snip>
YOU GUYS ARE SUPER!!!
NOWHERE ELSE ON EARTH COULD I FIND TECH SUPPORT THIS GOOD, AND SOOOO DEDICATED AT HELPING OUT, AT ANY PRICE!!!
THANK YOU ALL!!!
**************************************************
Yours so very sincerely,
Bernd
I didn't help any with your problem (it was beyond my skills), but I watched it off and on, and it really makes me feel good seeing a letter like this. You're right...the gang in here who helps us folks out, really *are* some of the best and nicest I've ever had the priveledge of knowing/reading/asking for help, in about 7 years of computing. So, in case I haven't made a letter similar to Bernd's in a while, let me use his and convey the same sentiments to all the gang in here who helps out all the time. John -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3rc2 (GNU/Linux) iD8DBQE/fdXzH5oDXyLKXKQRAs4bAJ42wbTGCxSdMarqZKO5V7sXPBId5QCcCpEd xIsUQ3iEUiYT4x5QZy1tHXE= =2eCe -----END PGP SIGNATURE-----
Bernd Koepsell wrote:
THANKS SO VERY VERY MUCH TO EVERYONE!!!!!!!!!
Your help and dedication in following this thread, and its variants, since the beginning of August, is so GREATLY appreciated!!!
I now know considerably more about my system than I ever could have without such a peevish problem. In a way I'm glad I didn't 'go around the bend' earlier. I certainly wouldn't have learned as much. Yet, going around the bend is exactly what solved the problem. Unfortunately, we'll never know what the 'real' cause of the problem was.
As you could tell with my last few e-mails, I just lost it. I hate working in windoze with such a passion, that 2 days without my SuSE was extremely toooo much.
I formatted and repartitioned the entire drive(which was a good thing to do anyway, because I was in need of changing partition sizes). I then reinstalled fresh from cd's(apparently you too, Basil!), and tried my modem. Oh gad!!! I was still having dns problems. I then took a look at the preprogrammed init string my modem was using. Wow, how screwy! It was preprogrammed to use something extremely foreign. I then tried a very simple init I had tried before, init1: ATZ, init2: AT&F1. That got me back to the point where I could properly connect.
On my first test I was expecting to be dropped at the usual max time of 59.4 minutes. As I reached 60 minutes, I started celebrating. As my connection time continued, I started downloading KDE updates. I was able to stay connected for 5 hours!!!!!!!!!!!!!!!!!!!!!! Just like I had been in 'that other os'.
Ran another test and kept downloading. Again, 5 whole hours, before my ISP dropped me!!!!!!!!!!!! (I'll deal with them later, he says with an evil grin!) 5 hours!!!!!!! WOW!!!!!!!!!!
Well, now you know what I've been doing ALL this week!! I've been making use of my new found connection time. It has taken me a while to set up all that I wanted of the kde updates, so kmail was out until this evening. I surely wasn't going to go through windoze to e-mail you guys back. 941 e-mails later, I'm finally able to respond.
**************************************************
YOU GUYS ARE SUPER!!!
NOWHERE ELSE ON EARTH COULD I FIND TECH SUPPORT THIS GOOD, AND SOOOO DEDICATED AT HELPING OUT, AT ANY PRICE!!!
THANK YOU ALL!!!
**************************************************
Yours so very sincerely,
Bernd
Congratulations! Double congratulations in fact: not only are you staying on-line for 5 hours but you haven't lost your marbles! :-). I am going to try and get a copy of the manual for your modem from the Robotics site because I still don't like the init string(s) you are feeding the modem (ATZ and AT&F1, in this order) simply because as far as I am concerned there is a contradiction between ATZ (=ATZ0) and AT&F1. However, if it ain't broke don't fix it --until, that is, I look at the manual (if I can download it) :-). Cheers. -- If logic ruled the World, men would ride side-saddle.
On Saturday 04 October 2003 04:09, Basil Chupin wrote: <snip>
Congratulations! Double congratulations in fact: not only are you staying on-line for 5 hours but you haven't lost your marbles! :-).
Who says I haven't???
I am going to try and get a copy of the manual for your modem from the Robotics site because I still don't like the init string(s) you are feeding the modem (ATZ and AT&F1, in this order) simply because as far as I am concerned there is a contradiction between ATZ (=ATZ0) and AT&F1.
I saw the same thing in the manual. It is a contradiction! Z = reset to Y command, which I am not issuing directly, but may be programmed within the 'current' configuration. I'm so afraid to touch anything right now, to even find out. Although I'm 'successfully' using kinternet now, I have no terminal program to allow direct keyboard input to the modem. The way that I have executed my ATI commands, was to modify wvdial.conf, save it, then execute wvdial in the shell and view the output. The manual says that I should be using Z4, which resets to default profile 1 (&F1). Things went screwy in the modem (probably my fault, even though I swear I didn't program anything into the profiles) which caused the dns not to function properly. Because of this, I don't think the Z commands point to the right profile, or maybe &F commands don't, or both. When I tried just AT as my init 1, like in windoze, I got an 'ok' back, but the next init string wasn't liked all too well. &F is to a Generic template, &F1 to the Hardware template, and &F2 to the Software template. Yes, ATZ is a contradiction with AT&F1. But then again... - Z could be ignored because no Y command is issued. - Z could be used because there is a properly issued Y in the 'current' programmed profile. Anyhow, I have a not-so-healthy respect and fear for my modem's "mysterious" operations. I would like to be able to input some appropriate S-registers for line noise and drop delays, etc., but I'm afraid they may conflict with what is behind door number '&F1'. It is working at present. Although, I would like to have control of my modem.
However, if it ain't broke don't fix it --until, that is, I look at the manual (if I can download it) :-).
I have it, obviously. It's a 301Kb pdf file. If you'd like I could attach it to an e-mail direct to you. Again, Thanks to Everyone!!!!! Bernd -- "If you want to build a ship, don't drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea." Antoine de St. Exupery
On 10/05/2003 03:46 AM, Bernd Koepsell wrote:
Although I'm 'successfully' using kinternet now, I have no terminal program to allow direct keyboard input to the modem.
Install minicom. It is a great terminal program. It shouldn't mess up the status quo to install and use it. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
-----Original Message-----
From: "Joe Morris (NTM)"
On 10/05/2003 03:46 AM, Bernd Koepsell wrote:
Although I'm 'successfully' using kinternet now, I have no terminal program to allow direct keyboard input to the modem.
Install minicom. It is a great terminal program. It shouldn't mess up the status quo to install and use it.
Another good progran is seyon. Works fantastic and has many options for the settings. Ken
Joe Morris (NTM) wrote:
On 10/05/2003 03:46 AM, Bernd Koepsell wrote:
Although I'm 'successfully' using kinternet now, I have no terminal program to allow direct keyboard input to the modem.
Install minicom. It is a great terminal program. It shouldn't mess up the status quo to install and use it.
Thanks for this. Been looking for a program like minicom (didn't know I had it all the time in SuSe :-)). Cheers. -- If logic ruled the World, men would ride side-saddle.
Bernd Koepsell wrote:
On Saturday 04 October 2003 04:09, Basil Chupin wrote: <snip>
Congratulations! Double congratulations in fact: not only are you staying on-line for 5 hours but you haven't lost your marbles! :-).
Who says I haven't???
<Shrug> Just a hunch. :-)
I am going to try and get a copy of the manual for your modem from the Robotics site because I still don't like the init string(s) you are feeding the modem (ATZ and AT&F1, in this order) simply because as far as I am concerned there is a contradiction between ATZ (=ATZ0) and AT&F1.
I saw the same thing in the manual. It is a contradiction! Z = reset to Y command, which I am not issuing directly, but may be programmed within the 'current' configuration. I'm so afraid to touch anything right now, to even find out. Although I'm 'successfully' using kinternet now, I have no terminal program to allow direct keyboard input to the modem. The way that I have executed my ATI commands, was to modify wvdial.conf, save it, then execute wvdial in the shell and view the output.
See the message from Joe Morris. Install minicom. I just installed it and it is exactly what I have been looking for for a while. Run minicom and, in your case, type ATI4 and then ATI5 to see what settings are being used by the modem. The manual explains I4 and I5 commands. I wouldn't fool around with the S Registers as you mention below re line noise and drop delays - there is no need to touch the Registers. The only one which needs setting is ATS0=0 so that your modem will not answer an incoming phone call.
The manual says that I should be using Z4, which resets to default profile 1 (&F1). Things went screwy in the modem (probably my fault, even though I swear I didn't program anything into the profiles) which caused the dns not to function properly. Because of this, I don't think the Z commands point to the right profile, or maybe &F commands don't, or both. When I tried just AT as my init 1, like in windoze, I got an 'ok' back, but the next init string wasn't liked all too well. &F is to a Generic template, &F1 to the Hardware template, and &F2 to the Software template.
Yes, ATZ is a contradiction with AT&F1.
But then again...
- Z could be ignored because no Y command is issued. - Z could be used because there is a properly issued Y in the 'current' programmed profile.
There is no Y command issued because it is part of the internal check which the modem performs when it is powered on. However, it IS possible to include it in the init string.
Anyhow, I have a not-so-healthy respect and fear for my modem's "mysterious" operations.
I would like to be able to input some appropriate S-registers for line noise and drop delays, etc., but I'm afraid they may conflict with what is behind door number '&F1'.
It is working at present. Although, I would like to have control of my modem.
However, if it ain't broke don't fix it --until, that is, I look at the manual (if I can download it) :-).
I have it, obviously. It's a 301Kb pdf file. If you'd like I could attach it to an e-mail direct to you.
I've downloaded it, thanks. From what you have said it now appears that you are able to connect and stay on-line for at least 5 hours so I think this "case" may not be considered closed; although I have to say that I am not especially happy with the init string(s) issued to the modem in Linux (as I have already said). But, you are on-line so let's not worry about it too much. The only thing I will add here is that if you can get the model number and/or the number Robotics has assigned to your modem then you could try and find what the init string is issued to it by Windows. Heree I am talking about Windows XP. If you go to \Windows\inf sub-directory you will find a series of files called mdm*.inf. These are the information files necessary to get "your" modem up and running, and when "your" modem is recognised by Windows this info file is compiled by Windows into mdm*.PNF file. There are a series of files called mdmusr?.inf for the Robotics modems and if you can find the one which relates to your modem then you will be able to see the init string Windows uses for your modem. All you would need to do is to use the same string in Linux AS INIT 1 because you can forget about init 2 (useless). Keeping in mind that XP came out at the end of 2001 it is possible that your modem is not in this mdmusr?.inf series of info files. However, if you go to Start/Control Panel/Performance and System/Admin/Device Manager and have a look at the driver(s) used for your modem you may be able to pinpoint the info (*.inf) file used. The other thing, of course, but here I just don't remember what happens because it has been a looooooong time since I've used Win to access the Web, is that there (??) should be a log file generated when you dial and this will contain the init string issued to the modem. If so, then this will save going thru looking for it in the mdm*.inf files :-).
Again, Thanks to Everyone!!!!!
Bernd
Not a problem. One of the reasons why this group exists - Penguinees Helping Penguinees (c) :-). Cheers. -- If logic ruled the World, men would ride side-saddle.
On Monday, 06 October, 2003 05:04, Basil Chupin wrote:
Bernd Koepsell wrote: <snip>
The way that I have executed my ATI commands, was to modify wvdial.conf, save it, then execute wvdial in the shell and view the output.
See the message from Joe Morris. Install minicom. I just installed it and it is exactly what I have been looking for for a while.
Thanks to Joe for minicom!!!
Run minicom and, in your case, type ATI4 and then ATI5 to see what settings are being used by the modem. The manual explains I4 and I5 commands.
Did that through wvdial just after my reinstall. ATI4 showed Y4 (factory configuration 2) being used. Because it was using that, for some wierd reason, dns wasn't working. Please don't ask me why! I have no idea what is contained in factory config 2. But when I switched to AT&F1(&F1=Y0=Hardware control template), the dns problem ended. I keep scratching my head, but it works now. That IS what matters.
The only thing I will add here is that if you can get the model number and/or the number Robotics has assigned to your modem then you could try and find what the init string is issued to it by Windows.
I pulled the log from windoze shortly after I started this thing in August, and used the same init string in linux, without success. This is why this thread is named the way it is. After reinstall, everything mysteriously was fixed, except for the dns problem. Which was fixed with AT&F1, even though I had used this same init before reinstall, without success. Who knows??? Oh well! I am now -consistently- connecting for 5 hours before my ISP drops me! YEAH!!! MMT Bernd -- "If you want to build a ship, don't drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea." Antoine de St. Exupery
The 03.10.02 at 22:46, Bernd Koepsell wrote:
THANKS SO VERY VERY MUCH TO EVERYONE!!!!!!!!!
Well, I'm glad :-) I would like to know what was the cause of all this, but... the important think is that it works. About your the dns problem you were having, it could be that those two dns servers your ISP used where down - it can be checked with dig, I think. I have seen your message with a log report from wvdial, and I would think it is a problem with the resolv file not being modified properly by the ip-up script, as Joe Morris said. But this is academic now :-) I prefer to use a local dns server configured as a cache - there is a default config in the suse packages for this. It makes for some faster connections over a modem. -- Cheers, Carlos Robinson
On Saturday 04 October 2003 06:11, Carlos E. R. wrote:
The 03.10.02 at 22:46, Bernd Koepsell wrote:
THANKS SO VERY VERY MUCH TO EVERYONE!!!!!!!!!
Well, I'm glad :-)
I would like to know what was the cause of all this, but... the important think is that it works.
About your the dns problem you were having, it could be that those two dns servers your ISP used where down - it can be checked with dig, I think. I have seen your message with a log report from wvdial, and I would think it is a problem with the resolv file not being modified properly by the ip-up script, as Joe Morris said. But this is academic now :-)
Actually, dns wasn't working after fresh system install with default modem string. When I changed the init string it began working. I tested this out a couple of times. I'm almost afraid of my modem now. It wasn't the resolve file itself, its' location, or permissions. I looked at it in several ways before I dumped the system, then again when dns wasn't working, after I reinstalled. It was the modem init string. Strange but true!
I prefer to use a local dns server configured as a cache - there is a default config in the suse packages for this. It makes for some faster connections over a modem.
Where and how? Thanks again, Bernd -- "If you want to build a ship, don't drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea." Antoine de St. Exupery
The 03.10.04 at 13:06, Bernd Koepsell wrote: [dns]
Actually, dns wasn't working after fresh system install with default modem string. When I changed the init string it began working. I tested this out a couple of times. I'm almost afraid of my modem now.
It wasn't the resolve file itself, its' location, or permissions. I looked at it in several ways before I dumped the system, then again when dns wasn't working, after I reinstalled. It was the modem init string. Strange but true!
Unbelievable! But I'll trust you. X'-)
I prefer to use a local dns server configured as a cache - there is a default config in the suse packages for this. It makes for some faster connections over a modem.
Where and how?
Let me see... my setup is a bit more complicated, but I installed it for a friend in minutes (like twenty). Ok, install bind. The default /etc/named.conf is directly set up for cache, if my memory serves me right (it varies depending on the sue version) -- or it is so on a sample file with the docs. You need to change some lines, though: #forwarders { 10.11.12.13; 10.11.12.14; }; #forward first; Enable, and enter your ISP dns servers. Of course, they must be fixed, these can not be entered automatically. You may use the same one that you get on the wvdial console, or read them from the /etc/resolv.conf while connected. Possibly, setup this: #listen-on port 53 { 127.0.0.1; }; to your local IPs, not the internet IP -- which is dynamic, anyway: you do not need to answer queries from the internet. Then, you need to start up bind: "rcnamed start". Look up on /var/log/messages for possible errors. Then edit /etc/resolv.conf, something similar to this (use 127.0.0.1 instead, I think): nameserver 192.168.100.2 search valinor And test it - without connecting: nimrodel:~ # host localhost localhost.valinor has address 127.0.0.1 Perhaps you need to issue a "rcnetwork restart" first. Then, you need to change your configuration (ARGH! ;-) ) so that the resolv.conf file is not touched during connection. This was done changing a variable somewhere, but I don't remember... ah, found it (etc/ppp/ip-up): | If you do not want the pppd to change your nameserver settings | set MODIFYDNS=no in the config file for this provider in | /etc/sysconfig/network/providers/ and ensure that the option | usepeerdns is not set in /etc/ppp/options. Mmm, that's not where I did it :-? I need some investigating done. It is something I don't touch much since suse 7.1 or roundabouts, and this is sue 8.2 ;-) -- Cheers, Carlos Robinson
Carlos E. R. wrote:
The 03.10.02 at 22:46, Bernd Koepsell wrote:
THANKS SO VERY VERY MUCH TO EVERYONE!!!!!!!!!
Well, I'm glad :-)
I would like to know what was the cause of all this, but... the important think is that it works.
About your the dns problem you were having, it could be that those two dns servers your ISP used where down - it can be checked with dig, I think. I have seen your message with a log report from wvdial, and I would think it is a problem with the resolv file not being modified properly by the ip-up script, as Joe Morris said. But this is academic now :-)
I prefer to use a local dns server configured as a cache - there is a default config in the suse packages for this. It makes for some faster connections over a modem.
I've just read your most recent response to Bernd re how to install this you-beaut-speeder-upper-of-modem-connections and I have to admit it had me totally confused within minutes :-). But maybe Bernd will not be confused :-). However, what I really want to know is: what exactly do you mean by "It makes for some faster connections over a modem."? Do you mean that you will get connected faster to your ISP when you dial-in? Or do you mean that the data transfer rates between you and the ISP will be faster once the connection has been established? Cheers. -- If logic ruled the World, men would ride side-saddle.
The 03.10.06 at 21:00, Basil Chupin wrote:
I've just read your most recent response to Bernd re how to install this you-beaut-speeder-upper-of-modem-connections and I have to admit it had me totally confused within minutes :-). But maybe Bernd will not be confused :-).
Sorry O:-)
However, what I really want to know is: what exactly do you mean by "It makes for some faster connections over a modem."?
Do you mean that you will get connected faster to your ISP when you dial-in?
No.
Or do you mean that the data transfer rates between you and the ISP will be faster once the connection has been established?
Neither :-) No, simply DNS queries will be faster, because the second time you need one, it is made locally, and not to a remote server. This applies, for example, when browsing, and on some mail sending/receiving operations, and it asumes, of course, that repeated or frequent dns queries over a modem line are slow. How slow? that depends, of course. Notice that if you ask your remote server for a name, and it doesn't knows already, it has to ask further up the chain, adding time. The second time should be faster, but asking locally would be instantaneous. On the other hand, it can use a lot of memory over time. -- Cheers, Carlos Robinson
participants (9)
-
Basil Chupin -
Bernd -
Bernd Koepsell
-
bernd＠covenantmail.net
-
Bruce Marshall -
Carlos E. R. -
Joe Morris (NTM) -
John -
Ken Schneider