On 09-Aug-98 Pieter Meiring wrote:
>>
>> On 07-Aug-98 Pieter Meiring wrote:
>> >Hello Karl,
>> >Firstly, let me thank you gain for your contribution of the diald config
>> >scripts - I have used them successfully first under RedHat 4.2 and later
under
>> >5.0. Up to now they have worked perfectly.
>> >
>> >However, I recently upgraded to RedHat 5.1 and have since been unable to
get
>> >diald to work.
>> >Vanilla Diald goes through the connection process but fails to start PPP.
PPD
>> >on its own starts up fine.
>> >With config-metered installed, the same happens. The modem connects. the
>> >connect script finishes and PPP dies with a SIGHUP.
>> >I have also been unable to get start-dctrl to work (or dctrl, for that
matter)
>> >- don't seem to be able to get it to read/write the pipes properly. Syslog
>> >reports the errors similar to:
>> >diald[nnn]: requests complete access to /tmp/dctrl-xxx
>> >diald[nnn]: failure to read /temp/dctrl-xxx - device not configured.
>> >
>> >I wonder if you have come across this problem with RH5.1 or if you can give
me
>> >any pointers where to look for the problem?
>>
>> 1st, make sure your using the most current version, 1.2.1. Second, there's a
>> problem using clone devices. It sounds like that could be it. If you are,
let
>> me know. It's about time I put the fix out anyhow.
>>
>> Please let me know how it goes.
>>
>> Thanks for the report.
>Am using 1.2.1 RPM downloaded from RedHat contribs mirror - still no joy.
>No, not using clones. I have found the trouble to lie in diald itself - it
>does not appear to be handing over to PPPD once the connection is made. I have
>reverted to an older version of diald (0.14) which comes with SUSE 5.2 and
>hacked the config files and stuff to fit in with RedHat and it now works -
>sadly not with your config scripts....
>
>Best Wishes, Pieter
Humm, that is fairly disturbing. The only similar experiences I've
had were when I used a version of ppp that didn't have the -s option
to chat, which is not the case with Redhat 5.1 and anyhow the modem
never connected. The other time (I think) was when I had the dns
timout too low, so that the connection would time out before the
connection script could complete. Because the first tcp packets over
ppp are almost always dns this generally screwed things. At least I
recall that happening. You could test this by initiating the
connection with a command that used an ip number instead of a name.
Did you try the .16 diald with the .14 (now working) configs, just to
be sure it's the program?
Oh well. Just when I put the work into a new release too. If you do
find out that I need to fix anything, please let me know.
I'm running the diald-0.16-3 rpm, and I don't see a newer one out there. Did
you get the 0.16.5 patch (http://www.loonie.net/~eschenk/diald.html) and make a
new one? (I'd expect a newer one to be 0.16.5-N.) If so, I'd like a copy of
the source rpm.
Good luck.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
