Hi Folks,
I'm not too familiar with this list (yet), so, sorry if
I'm asking about old news, but I've got a problem I gotta
get figured out... :)
I'm running a RH6.0 system, with masqurading (currently
off, becuase I haven't finished getting the diald
managed link done yet. Once it's connecting, I'll worry
about masqurading packets through the link :). I have
a working ppp configuration (I just set it up using
the linuxconf stuff).
Bottom line is this:
- when I connect using the RH supplied connect
script, the link comes up fine.
- when I let diald call the chat script & start
pppd, it never connects - it'll finish the
chat script, start pppd, wait, and then
ppp will die without generating errors or
authenticating or anything.
RH6.0 puts a couple of wrappers around calling pppd (there is:
a chat script file, a file containing options, a ifup-ppp
script that understands how to set pppd options based on the
options file & how to call pppd, and a ifup script that
is a generic script for bringing up interfaces). Anyway,
I unwound the abstraction by the simple expedient of
replacing /usr/sbin/pppd temporily with a script that printed
the command line with which it was called.
I took that command line, and ensured that diald was
calling pppd with similar options.
One big difference I did notice was this: with diald,
the chat script runs, and then diald gets called. With
the default RH scripts, pppd gets called with a connect
script argument. pppd then calls chat, chat returns to
pppd, and everything seems to work.
Is it possible to that control over the modem is not
being cleanly handed over to pppd by diald? Is there
some reason for this difference, or can I remove the
"connect" option from my diald.conf and call
diald like this:
diald -- connect "/usr/sbin/chat -v -f /pathtoscript"
in order to have pppd manage the modem? (I might have to
spec a couple other options, such as my PAP name or
something as well I suppose) [I just tried to do this,
and ran grief - I'm not sure what though, because I
don't get any debugging messages at all back from pppd
or the chat script, even though I have debugging
turned on. What gives?? )
I get one other sort of error, relating to tap0:
diald[3224]: start tap0: SIOCSIFMETRIC: Operation not supported
I can't tell if this actually causes a problem on the
grounds that I don't yet have a working link, but
the FAQ naturally doesn't mention it, and I haven't seen
it mentioned elsewhere. Any opinion anyone?
My thanks for anyone who might have any ideas as to the
above!
Regards,
-Cedric
-
| CCj/ClearLine - Unix/NT Administration and TCP/IP Network Services
| 118 Louisa Street, Kitchener, Ontario, N2H 5M3, 519-741-2157
\____________________________________________________________________
Cedric Puddy [EMAIL PROTECTED]
PGP Key Available at: http://www.thinkers.org/cedric
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
