[SLE] how to connect different isp's thru Wvdial
My questionn is how to configure wvdial to make a connection to different ISP's. If I have two or three different accounts with diffrent ISP's how do I make a connection to them thru the sue of wvdial ? Thanks -- Togan Muftuoglu toganm@yahoo.com __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.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/
Togan Muftuoglu wrote:
Basically, you have different sections in your wvdial.conf for each ISP and they are called from the command line. For example, using my wvdial.conf, I would connect to LineOne by typing: wvdial LineOne Here is part of my wvdial.conf file (with bits ****'d out): [Dialer Defaults] Modem = /dev/ttyS1 Baud = 115200 Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0 Phone = **** Username = **** Password = **** Dial Command = ATDT Stupid Mode = 0 New PPPD = 1 [Dialer LineOne] Phone = **** Username = **** Password = **** Stupid Mode = 1 For more detailed information see 'man wvdial'. Hope that helps, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\ -- 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/
Togan Muftuoglu wrote:
Getting wvdial to dial different isp's is very easy. There is a readme file that explains all this. There is a cascading effect, only put stuff in the lower sections that you want different from that in the main. Basically, just follow this: /etc/wvdial.conf ======================================================================================= [Dialer Defaults] Username = your login for isp 1 Modem = /dev/ttyS0 Password = your password for isp 1 Area Code = Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0 Tonline = 0 Compuserve = 0 Dial Command = ATDT Phone = isp 1 access no. Baud = 115200 Auto DNS = 0 Stupid Mode = 1 New PPPD = 1 [Dialer 2] Phone = isp 2 access no. Username = your login for isp 2 Password = your password for isp 2 [Dialer 3] etc. ======================================================================================= The command <wvdial> will dialup isp 1. The command <wvdial 2> will dialup isp 2. And yes there is a space in there. However, the problem I've had is that one isp's dns server won't work with the other's and vise/versa. Some will, some won't. Also, I have written a script to alleviate a severe and persistant problem I've had using wvdial. That of permissions changing on /dev/ttyS0. It was simple enough to incorporate a list of isp's in the script so that when called, you make your choice and it dials the appropriate number. What I think I need to do is have my script rewrite resolve.config with the appropriate dns servers depending on the choice of isp, 'cause right now isp 2 won't work for me without editing resolve.config first and then back again for isp 1. You'll see that in order for this script to work for users beside root, generous permission must be given for chmod. No doubt this opens a potential security hole as big as the Grand Canyon. But mine is a stand alone machine and the wife and kids only use windows. I have SuSEconfig set my permissions per secure local. The local entries are as follows: ======================================================================================= # Format: # <file> <owner>.<group> <permission> # /bin/umount root.disk 6775 /bin/mount root.disk 6775 /dev/ttyS0 root.uucp 6660 /etc/chap-secrets root.uucp 660 /etc/pap-secrets root.uucp 660 /etc/options root.uucp 660 /etc/wvdial.conf root.uucp 660 /bin/chmod root.trusted 6755 ======================================================================================= Yeah the permissions are lax to say the least. I'm the only one in the trusted group at this point. After spending a great deal of time trying to sneak up on the right settings, I just decided to go whole hog and work on trimming things down as I go. Well, here's the script as it exists today. It has performed flawlessly for about a week or more. I've not had to manually change permissions since. I named it dialup. ======================================================================================= #!/bin/sh chmod 6770 /dev/ttyS0 echo "chmod 6770 /dev/ttyS0" chgrp uucp /dev/ttyS0 echo "chgrp uucp /dev/ttyS0" echo "Choose ISP" echo "'m' for Mindspring or 'p' for Prodigy" read isp if [ "$isp" = "m" ]; then wvdial 2 elif [ "$isp" = "p" ]; then wvdial else echo "Sorry, $isp not recognized. Enter m or p" exit 1 fi exit 0 ======================================================================================= Not too bad for a first attempt to 'solve' (ok, bandaid) a real problem, eh? Yes I know everyone is going to say let SuSEconfig set the permissions for ttyS0. This doesn't work for some of us. According to Avery(?) at Worldvisions (wvdial folks) pppd needs to reset those permissions each time it runs. The problem is pppd can take up to 30 seconds to fully close. Hence the line "Attempting to exit gracefully...". After closing, it is supposed to reset the permissions back the way it was but this doesn't always happen. I had to manually change permissions almost everytime I dialed up. Sheesh. I wonder if it is just certain combinations of hardware that have this problem? Perhaps something needs to be changed in the pppd source. I don't think I'm ready for anything that heavy-duty. I'll keep workin' on it but if anyone has better ideas... Tim, NJ -- 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/
Togan Muftuoglu wrote:
Basically, you have different sections in your wvdial.conf for each ISP and they are called from the command line. For example, using my wvdial.conf, I would connect to LineOne by typing: wvdial LineOne Here is part of my wvdial.conf file (with bits ****'d out): [Dialer Defaults] Modem = /dev/ttyS1 Baud = 115200 Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0 Phone = **** Username = **** Password = **** Dial Command = ATDT Stupid Mode = 0 New PPPD = 1 [Dialer LineOne] Phone = **** Username = **** Password = **** Stupid Mode = 1 For more detailed information see 'man wvdial'. Hope that helps, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\ -- 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/
Togan Muftuoglu wrote:
Getting wvdial to dial different isp's is very easy. There is a readme file that explains all this. There is a cascading effect, only put stuff in the lower sections that you want different from that in the main. Basically, just follow this: /etc/wvdial.conf ======================================================================================= [Dialer Defaults] Username = your login for isp 1 Modem = /dev/ttyS0 Password = your password for isp 1 Area Code = Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0 Tonline = 0 Compuserve = 0 Dial Command = ATDT Phone = isp 1 access no. Baud = 115200 Auto DNS = 0 Stupid Mode = 1 New PPPD = 1 [Dialer 2] Phone = isp 2 access no. Username = your login for isp 2 Password = your password for isp 2 [Dialer 3] etc. ======================================================================================= The command <wvdial> will dialup isp 1. The command <wvdial 2> will dialup isp 2. And yes there is a space in there. However, the problem I've had is that one isp's dns server won't work with the other's and vise/versa. Some will, some won't. Also, I have written a script to alleviate a severe and persistant problem I've had using wvdial. That of permissions changing on /dev/ttyS0. It was simple enough to incorporate a list of isp's in the script so that when called, you make your choice and it dials the appropriate number. What I think I need to do is have my script rewrite resolve.config with the appropriate dns servers depending on the choice of isp, 'cause right now isp 2 won't work for me without editing resolve.config first and then back again for isp 1. You'll see that in order for this script to work for users beside root, generous permission must be given for chmod. No doubt this opens a potential security hole as big as the Grand Canyon. But mine is a stand alone machine and the wife and kids only use windows. I have SuSEconfig set my permissions per secure local. The local entries are as follows: ======================================================================================= # Format: # <file> <owner>.<group> <permission> # /bin/umount root.disk 6775 /bin/mount root.disk 6775 /dev/ttyS0 root.uucp 6660 /etc/chap-secrets root.uucp 660 /etc/pap-secrets root.uucp 660 /etc/options root.uucp 660 /etc/wvdial.conf root.uucp 660 /bin/chmod root.trusted 6755 ======================================================================================= Yeah the permissions are lax to say the least. I'm the only one in the trusted group at this point. After spending a great deal of time trying to sneak up on the right settings, I just decided to go whole hog and work on trimming things down as I go. Well, here's the script as it exists today. It has performed flawlessly for about a week or more. I've not had to manually change permissions since. I named it dialup. ======================================================================================= #!/bin/sh chmod 6770 /dev/ttyS0 echo "chmod 6770 /dev/ttyS0" chgrp uucp /dev/ttyS0 echo "chgrp uucp /dev/ttyS0" echo "Choose ISP" echo "'m' for Mindspring or 'p' for Prodigy" read isp if [ "$isp" = "m" ]; then wvdial 2 elif [ "$isp" = "p" ]; then wvdial else echo "Sorry, $isp not recognized. Enter m or p" exit 1 fi exit 0 ======================================================================================= Not too bad for a first attempt to 'solve' (ok, bandaid) a real problem, eh? Yes I know everyone is going to say let SuSEconfig set the permissions for ttyS0. This doesn't work for some of us. According to Avery(?) at Worldvisions (wvdial folks) pppd needs to reset those permissions each time it runs. The problem is pppd can take up to 30 seconds to fully close. Hence the line "Attempting to exit gracefully...". After closing, it is supposed to reset the permissions back the way it was but this doesn't always happen. I had to manually change permissions almost everytime I dialed up. Sheesh. I wonder if it is just certain combinations of hardware that have this problem? Perhaps something needs to be changed in the pppd source. I don't think I'm ready for anything that heavy-duty. I'll keep workin' on it but if anyone has better ideas... Tim, NJ -- 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)
-
chris.reeves@iname.com
-
tajcs@mindspring.com
-
toganm@yahoo.com