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/