It's working fine now...I've done so many things to try to get it to go,
that I have no idea what really did it.
Though it might be the fact the original
/etc/sysconfig/network-scripts/ifup was different than the one that was
there....and this was after a fresh install..Strange indeed! So anyways, I
copied it from another system....and as far as I know that's when it
started to work properly (not sure though...I spent days on end setting up
that server and trying to figure out diald...then that problem).
hmm, one strange thing I get on bootup is an error in ifup It complains
about my ifup-route and ifup-post The really wacked thing about that is,
it doesn't seem to effect the system at all (other than cosmetic crap on
bootup).....
Owell...it's working. Just wish I knew why. =)
Thanks.
Dan
At 09:06 PM 5/25/1998 MET, Stefan Ulrich Hegner wrote:
>Addressed to: Dan Cyr <[EMAIL PROTECTED]>
> [EMAIL PROTECTED]
>
>** Reply to note from Dan Cyr <[EMAIL PROTECTED]> Sun, 24 May 1998
15:28:38 -0700
>
>Dan,
>Just an idea: Could it be that you have a double dial command? That was
>the problem I got stuck with first and the results were very similar.
>
>You specify the "connect" option with script only in your /etc/diald.conf
>and the /etc/ppp/options leave WITHOUT a "connect" setting ...
>
>Stefan
>
> />>>> [EMAIL PROTECTED], [http://www.cam.net.uk/home/hegi] <<<<\
>|_____________/ my alternative cyberspace identities & sites:
\______________|
>| "hegi" alias Stefan U. Hegner, [http://userpage.fhw-berlin.de/~hegi]
|
> \Alt.Email: [EMAIL PROTECTED], Fachhochschule f"ur Wirtschaft, Berlin, FRG/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
