[SLE] Dial on Demand Frustrated.
I have been trying to get dial on demand going for a couple
of months now. I just can't seem to get anything going.
I tried diald for a while and after a couple of weeks
gave up on that. Then tried the wvdial.dod script from
suse. It didn't work out eighther. So I gave up for a
while.
I just recently started trying it again with the wvdial.dod
script from the german site. But I can't get that working.
What the hell!!?? I had less pain setting up
SAMBA and ipchains.
Can someone help me out? This is starting to suck. I
figure I'm real stupid or something is messed up on my
system. I'm hoping it's the system.
Anyway here is the output of wvdial.dod start:
---------------
root@crow:/sbin/init.d > wvdial.dod start
killing pppd process PID=14589
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 369 63.27.84.103:1891 194.112.123.20:www-http LAST_ACK -
tcp 1 1 63.27.84.103:1886 194.112.123.20:www-http LAST_ACK -
tcp 1 1 63.27.84.103:1884 194.112.123.20:www-http LAST_ACK -
tcp 1 1 63.27.84.103:1883 194.112.123.20:www-http LAST_ACK -
tcp 0 463 63.27.84.59:1877 194.112.123.20:www-http LAST_ACK -
tcp 0 437 63.27.84.59:1876 194.112.123.20:www-http LAST_ACK -
tcp 0 463 63.27.84.59:1874 194.112.123.20:www-http LAST_ACK -
/sbin/wvdial.dod: [: too many arguments
starting pppd 192.168.1.1: 192.168.99.99 /dev/ttyS2 115200 modem crtscts defaultroute -detach user MSN/B_Jilek ipcp-accept-local ipcp-accept-remote call wvdial demand idle 180 connect "/usr/bin/wvdial --chat "... PID=14631
ls: /var/run/ppp?.pid: No such file or directory
---------------
Someone please explain what may be causing:
/sbin/wvdial.dod: [: too many arguments
ls: /var/run/ppp?.pid: No such file or directory
What is that ^^^^^^^^ for?
After starting it it will not connect. I can still activate
wvdial myself.
Thank you for any help.
P.S. I was root when trying to run this. I don't know why
it gives the "Not all processes..." line.
--
B. L. Jilek
Brian:
All I did to get my system to connect via dial-up was followed the
instructions in the ISP-Hookup Howto.
Of course the howto requires you to read a couple of man pages, but
it's not really a whole lot of reading.
If it is not working even after that, then maybe something else is
wrong with your system. One thing you need to know is the irq and com
port that your modem is configured for. If you have one of those plug
& play winmodems, they don't work under linux (from what I
understand).
Mark
On Sat, 8 Apr 2000, Brian L. Jilek wrote:
| I have been trying to get dial on demand going for a couple
| of months now. I just can't seem to get anything going.
| I tried diald for a while and after a couple of weeks
| gave up on that. Then tried the wvdial.dod script from
| suse. It didn't work out eighther. So I gave up for a
| while.
|
| I just recently started trying it again with the wvdial.dod
| script from the german site. But I can't get that working.
| What the hell!!?? I had less pain setting up
| SAMBA and ipchains.
|
| Can someone help me out? This is starting to suck. I
| figure I'm real stupid or something is messed up on my
| system. I'm hoping it's the system.
|
| Anyway here is the output of wvdial.dod start:
| ---------------
| root@crow:/sbin/init.d > wvdial.dod start
| killing pppd process PID=14589
| (Not all processes could be identified, non-owned process info
| will not be shown, you would have to be root to see it all.)
| Active Internet connections (w/o servers)
| Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
| tcp 0 369 63.27.84.103:1891 194.112.123.20:www-http LAST_ACK -
| tcp 1 1 63.27.84.103:1886 194.112.123.20:www-http LAST_ACK -
| tcp 1 1 63.27.84.103:1884 194.112.123.20:www-http LAST_ACK -
| tcp 1 1 63.27.84.103:1883 194.112.123.20:www-http LAST_ACK -
| tcp 0 463 63.27.84.59:1877 194.112.123.20:www-http LAST_ACK -
| tcp 0 437 63.27.84.59:1876 194.112.123.20:www-http LAST_ACK -
| tcp 0 463 63.27.84.59:1874 194.112.123.20:www-http LAST_ACK -
| /sbin/wvdial.dod: [: too many arguments
| starting pppd 192.168.1.1: 192.168.99.99 /dev/ttyS2 115200 modem crtscts defaultroute -detach user MSN/B_Jilek ipcp-accept-local ipcp-accept-remote call wvdial demand idle 180 connect "/usr/bin/wvdial --chat "... PID=14631
| ls: /var/run/ppp?.pid: No such file or directory
| ---------------
|
| Someone please explain what may be causing:
| /sbin/wvdial.dod: [: too many arguments
|
| ls: /var/run/ppp?.pid: No such file or directory
|
| What is that ^^^^^^^^ for?
|
| After starting it it will not connect. I can still activate
| wvdial myself.
| Thank you for any help.
|
| P.S. I was root when trying to run this. I don't know why
| it gives the "Not all processes..." line.
| --
| B. L. Jilek
were you able to get plian wvdial to work before playing with wvdial.dod ? At 07:57 PM 4/8/2000 -0400, Mark B Withers wrote:
Brian:
All I did to get my system to connect via dial-up was followed the instructions in the ISP-Hookup Howto.
Of course the howto requires you to read a couple of man pages, but it's not really a whole lot of reading.
If it is not working even after that, then maybe something else is wrong with your system. One thing you need to know is the irq and com port that your modem is configured for. If you have one of those plug & play winmodems, they don't work under linux (from what I understand).
Mark
On Sat, 8 Apr 2000, Brian L. Jilek wrote:
| I have been trying to get dial on demand going for a couple | of months now. I just can't seem to get anything going. | I tried diald for a while and after a couple of weeks | gave up on that. Then tried the wvdial.dod script from | suse. It didn't work out eighther. So I gave up for a | while. | | I just recently started trying it again with the wvdial.dod | script from the german site. But I can't get that working. | What the hell!!?? I had less pain setting up | SAMBA and ipchains. | | Can someone help me out? This is starting to suck. I | figure I'm real stupid or something is messed up on my | system. I'm hoping it's the system. | | Anyway here is the output of wvdial.dod start: | --------------- | root@crow:/sbin/init.d > wvdial.dod start | killing pppd process PID=14589 | (Not all processes could be identified, non-owned process info | will not be shown, you would have to be root to see it all.) | Active Internet connections (w/o servers) | Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name | tcp 0 369 63.27.84.103:1891 194.112.123.20:www-http LAST_ACK - | tcp 1 1 63.27.84.103:1886 194.112.123.20:www-http LAST_ACK - | tcp 1 1 63.27.84.103:1884 194.112.123.20:www-http LAST_ACK - | tcp 1 1 63.27.84.103:1883 194.112.123.20:www-http LAST_ACK - | tcp 0 463 63.27.84.59:1877 194.112.123.20:www-http LAST_ACK - | tcp 0 437 63.27.84.59:1876 194.112.123.20:www-http LAST_ACK - | tcp 0 463 63.27.84.59:1874 194.112.123.20:www-http LAST_ACK - | /sbin/wvdial.dod: [: too many arguments | starting pppd 192.168.1.1: 192.168.99.99 /dev/ttyS2 115200 modem crtscts defaultroute -detach user MSN/B_Jilek ipcp-accept-local ipcp-accept-remote call wvdial demand idle 180 connect "/usr/bin/wvdial --chat "... PID=14631 | ls: /var/run/ppp?.pid: No such file or directory | --------------- | | Someone please explain what may be causing: | /sbin/wvdial.dod: [: too many arguments | | ls: /var/run/ppp?.pid: No such file or directory | | What is that ^^^^^^^^ for? | | After starting it it will not connect. I can still activate | wvdial myself. | Thank you for any help. | | P.S. I was root when trying to run this. I don't know why | it gives the "Not all processes..." line. | -- | B. L. Jilek
| ICQ: 10733954 | | Linux user: 163800 | PGP: DSS 0x800B3A69 RSA 0x3F1963C5 | OS: SuSE Linux 6.3 | --------------------------------------------------------- | | | -- | 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/ |
-- 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/
-- 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/
At 19:36 04/08/2000 -0400, you wrote:
I have been trying to get dial on demand going for a couple of months now. I just can't seem to get anything going.
I had that trouble too. The error you're getting:
/sbin/wvdial.dod: [: too many arguments
indicates that the wvdial.dod you got from the German site has line-breaks where you don't want them. I'm attaching a gzipped version of my wvdial.dod that works on my system in a separate email, since I don't want to send an attachment to the list. However, let's start with your /etc/wvdial.conf file just to make sure you don't have problems there... Here is my /etc/wvdial.conf with username and password masked, as well as the phone number to my ISP. Make appropriate changes, and save in /etc/wvdial.conf. Notice the distinct lack of the new wvdial.conf "Sections" that allow for multiple ISP's to be configured. They do not play well with wvdial.dod, and have therefore been removed. = = = begin /etc/wvdial.conf = = = [Dialer Defaults] Modem = /dev/modem Baud = 57600 Init1 = ATZ Init2 = AT M0 L0 Q0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0 Area Code = Phone = 5551212 Username = bljilek Password = password Dial Command = ATDT Stupid Mode = 1 New PPPD = 1 = = = end /etc/wvdial.conf = = = Next, make sure you're running at least version 1.4 of wvdial: As root: rpm -q wvdial If you're not, try using Yast to update your version of wvdial from one of the SuSE mirror sites. I suggest ftp.twoguys.org. Now, let's have a look at your wvdial.dod script. As I said, I suspect you're having line break problems due to trying to get a working copy from a web site. With that wvdial.dod.gz I sent you in a separate email, and again assuming you're logged in as root, are in the /root directory, and that the wvdial.dod.gz file is sitting in /root: gzip -d wvdial.dod.gz mv wvdial.gz /sbin/init.d chmod 744 /sbin/init.d/wvdial.dod And the symbolic links in case they don't exist: ln -s /sbin/init.d/wvdial.dod /sbin/init.d/rc2.d/S20wvdial.dod ln -s /sbin/init.d/wvdial.dod /sbin/init.d/rc2.d/K20wvdial.dod ln -s /sbin/init.d/wvdial.dod /sbin/init.d/rc3.d/S20wvdial.dod ln -s /sbin/init.d/wvdial.dod /sbin/init.d/rc3.d/K20wvdial.dod That should get that piece of the equation working for you. Hope this helped you out... Argentium -- 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/
Hi Argentium! On Sat, 08 Apr 2000, Argentium G. Tiger wrote:
/sbin/wvdial.dod: [: too many arguments
indicates that the wvdial.dod you got from the German site has line-breaks where you don't want them. I'm attaching a gzipped version of my wvdial.dod that works on my system in a separate email, since I don't want to send an attachment to the list.
I am still getting the same errors. However I've noticed something in the Console log. Everytime I try to activate wvdial.dod this line is printed in the console. Apr 8 22:49:20 crow pppd[22868]: unrecognized option '192.168.99.99' This line in wvdial.dod does not seem to be messed up. What could this mean?
However, let's start with your /etc/wvdial.conf file just to make sure you don't have problems there...
Next, make sure you're running at least version 1.4 of wvdial:
Version 1.41-9 is what I'm running. I've edited the wvdial.conf
script like you sugested.
Still no luck.
--
B. L. Jilek
At 22:59 04/08/2000 -0400, "Brian L. Jilek"
/sbin/wvdial.dod: [: too many arguments
I am still getting the same errors. However I've noticed something in the Console log. Everytime I try to activate wvdial.dod this line is printed in the console.
Apr 8 22:49:20 crow pppd[22868]: unrecognized option '192.168.99.99'
Hrm... This is puzzling. I'm assuming you overwrote your /sbin/init.d/wvdial.dod with the copy I sent you in a private mail. I've gotten confirmation back from others that this file has worked for them, so we can rule it out as the source of the problem. Something else seems to be having problems with the exact line: Remote_IP="192.168.99.99"
This line in wvdial.dod does not seem to be messed up. What could this mean?
Well, at first I have to admit I'm a bit stumpped. [ Version of wvdial ]
Version 1.41-9 is what I'm running. I've edited the wvdial.conf script like you sugested.
Ok, that rules that out. I'm running "wvdial-1.40-19", so it's a slightly more recent version than yours. You _might_ try updating wvdial from an ftp mirror. I sometimes use ftp.twoguys.org. The update directory for that site is /SuSE/current/ My most recent update is from a german mirror: 212.122.128.32 /pub/SuSE-Linux/6.3/i386.de/ Since our version numbers on wvdial are so close, I doubt this is the most likely source of the problem.
Still no luck.
Ok, let me try a few exploratory questions: Are you hooked to an internal network on eth0/eth1/etc... or are you only hooking up via a PPP connection via /dev/modem to the internet? The reason I ask is I want to make sure that the PPPD (PPP Daemon) is binding to the correct interface. I think you stated that wvdial when run manually works fine. Are you running this as root, or as a user? Perhaps wvdial.dod doesn't have the necessary permissions to change the routing tables or make a connection. That's all I can think of off the top of my head right now. We probably need input from some more people that have had problems similar to yours who found a solution. I know what works, but only in my situation when also combining with the SuSEfirewall 2.1 firewall / packet filter package on a machine built for firewall and dialout purposes. Argentium -- 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/
"Brian L. Jilek" wrote:
I have been trying to get dial on demand going for a couple of months now. I just can't seem to get anything going. [..} /sbin/wvdial.dod: [: too many arguments starting pppd 192.168.1.1: 192.168.99.99 [..]
The blank after "...1: 192" is too much in the line above. Ralf -- 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/
Hi Ralf! On Sun, 09 Apr 2000, Ralf Corsepius wrote:
"Brian L. Jilek" wrote:
I have been trying to get dial on demand going for a couple of months now. I just can't seem to get anything going. [..} /sbin/wvdial.dod: [: too many arguments starting pppd 192.168.1.1: 192.168.99.99 [..]
The blank after "...1: 192" is too much in the line above.
PPPPDPARAMS="$Local_IP:$Remote_IP $Modem $Baud modem crtscts
$DEFAULTROUTE -detach user $Username ipcp-accept-local ipcp-accept-remote
call wvdial demand idle $Idle"
This is all one line but I guess it's setting up what you said
is wrong. It looks right. How would I get it to quit putting
the space in there?
--
B. L. Jilek
At 11:09 AM 04/09/00 -0400, Brian L. Jilek wrote:
PPPPDPARAMS="$Local_IP:$Remote_IP $Modem $Baud modem crtscts $DEFAULTROUTE -detach user $Username ipcp-accept-local ipcp-accept-remote call wvdial demand idle $Idle"
I don't use the IP setup. I simply use PPPPDPARAMS="$Modem $Baud modem crtscts $DEFAULTROUTE lcp-echo-interval 0 \ nodetach user $Username ipcp-accept-local ipcp-accept-remote \ call wvdial demand idle $Idle"; I don't know if that will work on your setup or not. Bill Moseley mailto:moseley@hank.org -- 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/
"Brian L. Jilek" wrote:
Hi Ralf!
On Sun, 09 Apr 2000, Ralf Corsepius wrote:
"Brian L. Jilek" wrote:
I have been trying to get dial on demand going for a couple of months now. I just can't seem to get anything going. [..} /sbin/wvdial.dod: [: too many arguments starting pppd 192.168.1.1: 192.168.99.99 [..]
The blank after "...1: 192" is too much in the line above.
Sorry, my answer was somewhat unclear/broken. I actually meant the blank after the ':' in '192.168.1.1: 192..' should not be there. This causes pppd to read this as two arguments instead of one.
PPPPDPARAMS="$Local_IP:$Remote_IP $Modem $Baud modem crtscts
I assume that $Remote_IP does not get set up correctly /sbin/init.d/wvdial.dod.
$DEFAULTROUTE -detach user $Username ipcp-accept-local ipcp-accept-remote call wvdial demand idle $Idle"
This is all one line but I guess it's setting up what you said is wrong. It looks right. How would I get it to quit putting the space in there?
There seem to be several versions of wvdial.dod floating around, so I can't exactly tell what to do. Try checking how wvdial.dod sets up $Remote_IP. Ralf -- Ralf Corsepius Forschungsinstitut fuer Anwendungsorientierte Wissensverarbeitung (FAW) Helmholtzstr. 16, 89081 Ulm, Germany Tel: +49/731/501-8690 mailto:corsepiu@faw.uni-ulm.de FAX: +49/731/501-999 http://www.faw.uni-ulm.de -- 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/
Make sure you use the wvdial.dod from the GERMAN version of the site - line wrapping on the English version has killed it. Worked first time on my box after getting the German .dod script.
I have been trying to get dial on demand going for a couple of months now. I just can't seem to get anything going. [..}
-- This sig brought to you by SuSE 6.3 and sendmail. Linux - you know it makes sense. -- 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/
I used the german version form the web sight , saved the html , then used joe to delete everthing above and below it. You might have some old stuff lurking there , ie an old wvdial.dod script , old ppp scripts , old chap scripts etc... Try cleaning all those out. then run wvdial and configure it to work. Once it works , download , save the german html and edit it to remove the html code. Follow the instructions from the englisgh web page ( the instructions work , not the script) and be carfull to follw the exactly. If you want ti to wrok ehen ever you reboot , you will need to make the sym linhs in the instructions. At 07:36 PM 4/8/2000 -0400, Brian L. Jilek wrote:
I have been trying to get dial on demand going for a couple of months now. I just can't seem to get anything going. I tried diald for a while and after a couple of weeks gave up on that. Then tried the wvdial.dod script from suse. It didn't work out eighther. So I gave up for a while.
I just recently started trying it again with the wvdial.dod script from the german site. But I can't get that working. What the hell!!?? I had less pain setting up SAMBA and ipchains.
Can someone help me out? This is starting to suck. I figure I'm real stupid or something is messed up on my system. I'm hoping it's the system.
Anyway here is the output of wvdial.dod start: --------------- root@crow:/sbin/init.d > wvdial.dod start killing pppd process PID=14589 (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 369 63.27.84.103:1891 194.112.123.20:www-http LAST_ACK - tcp 1 1 63.27.84.103:1886 194.112.123.20:www-http LAST_ACK - tcp 1 1 63.27.84.103:1884 194.112.123.20:www-http LAST_ACK - tcp 1 1 63.27.84.103:1883 194.112.123.20:www-http LAST_ACK - tcp 0 463 63.27.84.59:1877 194.112.123.20:www-http LAST_ACK - tcp 0 437 63.27.84.59:1876 194.112.123.20:www-http LAST_ACK - tcp 0 463 63.27.84.59:1874 194.112.123.20:www-http LAST_ACK - /sbin/wvdial.dod: [: too many arguments starting pppd 192.168.1.1: 192.168.99.99 /dev/ttyS2 115200 modem crtscts defaultroute -detach user MSN/B_Jilek ipcp-accept-local ipcp-accept-remote call wvdial demand idle 180 connect "/usr/bin/wvdial --chat "... PID=14631 ls: /var/run/ppp?.pid: No such file or directory ---------------
Someone please explain what may be causing: /sbin/wvdial.dod: [: too many arguments
ls: /var/run/ppp?.pid: No such file or directory
What is that ^^^^^^^^ for?
After starting it it will not connect. I can still activate wvdial myself. Thank you for any help.
P.S. I was root when trying to run this. I don't know why it gives the "Not all processes..." line. -- B. L. Jilek
| ICQ: 10733954 | Linux user: 163800 PGP: DSS 0x800B3A69 RSA 0x3F1963C5 | OS: SuSE Linux 6.3 --------------------------------------------------------- -- 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/
-- 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/
Just to let you all know, I didn't get wvdial.dod working. In
fact I ended up trashing something so I couldn't connect to
the internet at all.
Since I was wanting to get rid of the other OS taking up 8G
of hard drive space anyway, I went ahead and reinstalled.
Took me a week to get everything back to normal
because I screwed up the
backups.
Anyway, thanks to everyone who tried to help me out. I'll
try again in a few days. Hopefully this fresh install will
fix whatever was wrong.
--
B. L. Jilek
participants (7)
-
agtiger@coolnet.net
-
Anonymous User
-
bljilek@bigfoot.com
-
corsepiu@faw.uni-ulm.de
-
moseley@hank.org
-
samelash@ix.netcom.com
-
wulfie@wulfric7.co.uk