[SLE] WVDIAL timeouts
Hello. This is Gary in Spanaway, WA. I am trying to set up a full time internet to amateur radio TCPIP gateway using Suse Linux v6.2. I am using WVDIAL on a full-time PPP dialup link with my local ISP, with a fixed IP address. Although WVDIAL configured easily, thus taking all of the headaches out of getting PPP running, I am plagued by a chronic timeout problem. After the link is established and I am logged onto my ISP, everything works well for 20-30 minutes. Then I get an error message saying that "PPP has died" and I try to redial and re-establish the link... That happens for awhile, until I get a message from WVDIAL saying that the modem is not responding.... I would like to think that the timeout is not a matter of the ISP dumping me, as I can stay connected for days or weeks with my Winders-98 or Winders-2000 Beta-RC2 machines, without a problem.... Somehow I think there is a need to play with the configuration of WVDIAL somehow, but so far I cannot seem to find out what that entails. Can someone give some advice? I would hope that it would be a simple matter of setting a timer or some other flag.... Oh yes, btw, I am using a US Robotics 56K Sportster modem (external), and get very good connects to my ISP in v.90 mode (48K to 53,333K). I just wish I could stay connected for extended periods of time without having to redial or the modem die on me... Now to really confuse things... I have tried a second 56K modem of different manufacture, and it does exactly the same things as described above.... Your suggestions and comments would be appreciated. Thanks.... Best regards, Gary -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
w7ntf@aol.com wrote:
play with the configuration of WVDIAL somehow, but so far I cannot seem to find out what that entails. Can someone give some advice? I would hope that it would be a simple matter of setting a timer or some other flag....
Alot of people are having trouble with wvdial. I don't get timeout problems, but I do get "modem not responding" frequently and have to OFF/ON cycle the modem to get it back. As with you, winblows handles the modem fine. My suspiscions are: 1. pppd problem-- try killall pppd or "New pppd=1" in wvdial.conf 2. Something with the new kernels requiring the serial line users to be members of group uucp, maybe wvdial isn't handling this correctly. 3 I'm also getting a strange symptom where my /dev/ttyS1 is being "automagically" changed from root:dialout 666 to root:dialout 600. This occurs while I'm ONLINE!!!! I'm beginning to loose faith in the stability of the filesystem. I dialout fine, then if I disconnect and try to reconnect, I get "permission denied /dev/ttyS1", and the 666 => 600 conversion occured. It has to be something screwy with the serial line=>modem path. I'm getting fed up enough that I'm getting ready to setup Suse's ppp-up script. I hope we get wvdial sorted out and back on track for everyone. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Tue, Nov 30, 1999 at 05:41:00AM -0500, zentara wrote:
Alot of people are having trouble with wvdial. I don't get timeout ... My suspiscions are: 1. pppd problem-- try killall pppd or "New pppd=1" in wvdial.conf 2. Something with the new kernels requiring the serial line users to be members of group uucp, maybe wvdial isn't handling this correctly.
Ownership and permissions are not the kernel's issue, but are defined by SuSE's installation tools and various conventions. One would hope that wvdial, as found on the SuSE CDs, would have compatible ownership with the serial devices, but the same would not be true with wvdial downloaded off the net. That said, I think previous SuSE versions may have used group dialout where now they use uucp.
3 I'm also getting a strange symptom where my /dev/ttyS1 is being "automagically" changed from root:dialout 666 to root:dialout 600. This occurs while I'm ONLINE!!!! I'm beginning to loose faith in the stability of the filesystem. I dialout fine, then if I disconnect and try to reconnect, I get "permission denied /dev/ttyS1", and the 666 => 600 conversion occured. It has to be something screwy with the serial line=>modem path.
This has come up on this list quite a few times, and I think is an issue with SuSEconfig tools, and can be fixed, either through YaST or by editing one or more files in /etc.
I'm getting fed up enough that I'm getting ready to setup Suse's ppp-up script.
I hope we get wvdial sorted out and back on track for everyone.
As I understand it, wvdial was developed to simplify establishing a ppp connection, replacing the chat scripts with a compiled application. I used it at first in SuSE, but then realized that the chat scripts (i.e., ppp-up) where also pretty simple, at least for my ISP, so abandoned wvdial; later I turned to diald, which uses more or less the same chat scripts. IMHO wvdial serves as a stepping stone to get underway, but I'd recommend "upgrading" to the ppp-up scripts for more flexibility, then to diald for automating dial-up connection. BTW, 'chmod 666 /dev/ttyS1' seems a bit excessive, since it would allow any user (or any program) to control the modem. Using 660 allows only users in the modem's group (e.g., dialout, uucp, or whatever) to do so, and might be preferred. -- Ken Irving Trident Software jkirving@mosquitonet.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (3)
-
jkirving＠mosquitonet.com -
w7ntf＠aol.com -
zentara＠gnat.net