Thanks to Michele and Bob for your suggestions. I have learnt a lot while
following them up. Unfortunately, I don't have the ip program and diald has
been using route all along. I have now found that diald responds to ping
and that I get a normal response if I put an ip address in my list of
nameservers. I have managed to convince myself that I did not have a
specific nameserver listed before and it all worked fine (logging on to
Compuserve), so I have some digging to do to understand what is happening.
Whatever, the problem is not with diald.
One last question. Where can I get 0.99.3? I have looked at various mirrors
and the diald home page and can't see anything above 0.99.1.
Thanks again
Mike Sandford
At 23:25 02/02/00 +0100, Michele Gius wrote:
>
>Hello Mike,
>
>me too I have SuSE 6.2 and experienced the same problem.
>
>Checking the debugging output and the sources of diald (ver. 0.99.3) I found
>that the problem is with the setup of the routes.
>
>On SuSE 6.2 the ip program is present but it seems that it does not
>correctly support the syntax expected by diald. Diald uses the ip program to
>set up routes if it finds it. If ip isn't present it uses route.
>
>Here is an excerpt from config.h of the diald sources:
>--------
>/*
> * The "ip" program is the preferred way to set routes on Linux 2.2
> * and beyond. Either specify the path here or use the "path-ip"
> * config option. The "ip" program you use needs to understand
> * the "metric" keyword - some older ones do not. You can find
> * "ip" on: ftp://ftp.inr.ac.ru/ip-routing/
> */
>#undef PATH_IP "/usr/sbin/ip"
>--------
>
>TEMPORARY SOLUTION:
>I haven't yet had the time to check out the ip program from the source
>indicated above, so I simply set path-ip permanently to 0 and recompiled
>diald. If you and your system scripts do not use the ip program you may also
>simply rename or delete it.
>Diald - now forced to use the route program to set up the routes - suddenly
>worked fine again.
>
>Also be sure to set IP_DYNIP=yes in /etc/rc.config and to run SuSEconfig and
>reboot or do an "echo 2 > /proc/sys/net/ipv4/ip_dynaddr".
>
>Another tip: If you upgrade to version 0.99.3 you will get rid of the
>duplicate host route on sl0.
>
>I hope this helps.
>
>Michele.
>
>PS: Please excuse my bad English.
>
>----- Original Message -----
>From: Mike Sandford <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Tuesday, February 01, 2000 4:02 PM
>Subject: diald fails to wake up when required
>
>
>> I once had a working diald and now I don't. I admit to making a change in
>> the system configuration somewhere but, and I realise my mistake here, I
>> cannot get back to the previous settings. I am now paying for the oversight
>> and I apologise for having to ask this question. I have not changed the
>> diald parameters.
>>
>> Problem: diald comes up and appears to set routes but Netscape does not
>> find the new interface and diald does not dial out. Previously I noticed
>> that when I entered the command 'route' diald would dial out and eventually
>> 'route' would show the new dynamic IP numbers on interface ppp0.
>>...
>> Any clues please?
>>
>> Mike Sandford
>>
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
>> the body of a message to [EMAIL PROTECTED]
>>
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-diald" in
>the body of a message to [EMAIL PROTECTED]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
