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. Now all I
> get is the following:
>
> 192.168.0.0   *   255.255.255.255   UH   1   0   0   dummy0
> 192.168.1.8   *   255.255.255.255   UH   0   0   0   sl0
> 192.168.1.8   *   255.255.255.255   UH   0   0   0   sl0
> 192.168.0.0   *   255.255.255.0     U   0   0   0   eth0
> loopback       *   255.0.0.0         U   0   0   0   lo
> default           *   0.0.0.0           U   0   0   0   sl0
>
> I have a simple network of a Linux server running SuSE 6.2, kernel 2.2.13,
> samba, diald 0.99.1, dhcp. I do not use NFS, NIS, named, or routed.
>
> The network functions. User workstations log on, dhcp gives them an
address
> and samba communicates.
>
> If I set diald 'up' it dials out and gathers the dynamic addresses
> producing a new route table with sl0 replaced by ppp0, and the new IP
> address in place. But still Netscape does not see the interface.
>
> 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]

Reply via email to