Hans Houwaard wrote:
> Hello,
>
> Saw your mail in the suse-linux-e mailing list and it seems like we have the
> same kind of problem. Diald stops working correctly at some point in time and
> the link is gone. My question is, have you been able to solve the problem? And
> if you have, how did you do it? I have a feeling it has to do with diald and
> the new kernel, which implements a new way of adding and deleting routes. But
> all that is way out of my league of knowledge, so I depend on others to solve
> the problem.
There is definitely a new 'feature' in the kernel ehich generated dupicate routes. But
diald-0.99 (according to Mike Jagdis) has been modified to take this into account. So
I installed diald-0.99 and for good measure began using the ethertap proxy in
preference to
the old SLIP proxy. It seems to have worked, but introduces weird new error messages
into the
log file.
I posted an update detailing all this but the list seems very slow to get my postings
for
some reason - it takes days until my postings to the list show up in _my_ mailbox
anyway.
Here's the update:
> I abandoned diald-0.16 as I just couldn't work out why it was dying
> (SuSE 6.1/glibc2.0.7/2.2.9 kernel). Taking on board the remarks I've seen in the
> archives about the 2.2 kernel's tendency to set up superfluous routes,
> I installed diald-0.99.
>
> The link now seems to go up and down correctly, diald does not die any more,
> there are no more complaints about 'sl0: transmit timed out, bad line quality?'
> (as sl0 is no longer used) and there are no more errors like 'Nonzero exit
> status (7) on command '/sbin/route add 158.152.1.222 metric 1 dev sl0'.
>
> However, there are now some other rather strange errors showing up in the log
> file. Is anyone able to shed some light on what these strange error codes mean?
>
> When diald runs the connect script:
>
> running '/etc/suseppp/scripts/generic.connect'
> connector: shell-init: could not get current directory: getcwd: cannot access
> parent directories: No such file or directory
>
> When a FIFO "down" request is received, or closing down idle link:
>
> running '/sbin/ifconfig tap0 193.237.131.114 pointopoint 158.152.1.222 broadcast
> 0.0.0.0 netmask 255.255.255.255 metric 0 mtu 1500 up'
> start tap0: SIOCSIFMETRIC: Operation not supported
> SIGCHLD[55]: pid 6267 system, status 256
>
> ---
>
> Immediately after pppd negotiation completes:
>
> running '/sbin/ifconfig ppp0 193.237.131.114 pointopoint 158.152.1.222 broadcast
> 0.0.0.0 netmask 255.255.255.255 metric 0 mtu 1500 up'
> start ppp0: SIOCSIFMETRIC: Operation not supported
> SIGCHLD[65]: pid 6293 system, status 256
>
> ---
>
> Immediately after pppd exits (returning 256 as shown below), two scenarios:
>
> (A) diald closes down link from this end
>
> SIGCHLD[60]: pid 5388 link, status 256
> running '/sbin/ifconfig tap0 193.237.131.114 pointopoint 158.152.1.222 broadcast
> 0.0.0.0 netmask 255.255.255.255 metric 0 mtu 1500 up'
> start tap0: SIOCSIFMETRIC: Operation not supported
> SIGCHLD[61]: pid 6274 system, status 256
> start tap0: Establishing routes for tap0
> running '/sbin/route add 158.152.1.222 metric 0 dev tap0'
> start tap0: SIOCADDRT: File exists
> SIGCHLD[62]: pid 6275 system, status 1792
> running '/sbin/route add default metric 0 netmask 0.0.0.0 dev tap0'
> start tap0: SIOCADDRT: File exists
> SIGCHLD[63]: pid 6276 system, status 1792
>
> (B) modem hangs up unexpectedly at the remote end:
>
> SIGCHLD[70]: pid 6290 link, status 256
> running '/sbin/ifconfig tap0 193.237.131.114 pointopoint 158.152.1.222 broadcast
> 0.0.0.0 netmask 255.255.255.255 metric 0 mtu 1500 up'
> start tap0: SIOCSIFMETRIC: Operation not supported
> SIGCHLD[71]: pid 6539 system, status 256
> start tap0: Establishing routes for tap0
> running '/sbin/route add 158.152.1.222 metric 0 dev tap0'
> SIGCHLD[72]: pid 6540 system, status 0
> running '/sbin/route add default metric 0 netmask 0.0.0.0 dev tap0'
> SIGCHLD[73]: pid 6541 system, status 0
> stop ppp0: Removing routes for ppp0
> running '/sbin/route del default metric 0 netmask 0.0.0.0 dev ppp0'
> stop ppp0: SIOCDELRT: No such process
> SIGCHLD[74]: pid 6542 system, status 1792
> running '/sbin/ifconfig ppp0 0.0.0.0'
> ppp: ppp0 not active
> stop ppp0: SIOCSIFFLAGS: Device not configured
> SIGCHLD[75]: pid 6543 system, status 65280
> Link died on remote end.
> running '/sbin/ifconfig tap0 193.237.131.114 pointopoint 158.152.1.222 broadcast
> 0.0.0.0 netmask 255.255.255.255 metric 0 mtu 1500 up'
> start tap0: SIOCSIFMETRIC: Operation not supported
> SIGCHLD[76]: pid 6544 system, status 256
> start tap0: Establishing routes for tap0
> running '/sbin/route add 158.152.1.222 metric 0 dev tap0'
> start tap0: SIOCADDRT: File exists
> SIGCHLD[77]: pid 6545 system, status 1792
> running '/sbin/route add default metric 0 netmask 0.0.0.0 dev tap0'
> start tap0: SIOCADDRT: File exists
> SIGCHLD[78]: pid 6546 system, status 1792
>
> --
>
--
[EMAIL PROTECTED] Ralph Clark, Virgo Solutions Ltd (UK)
__ _
/ / (_)__ __ ____ __ * Powerful * Flexible * Compatible * Reliable *
/ /__/ / _ \/ // /\ \/ / *Well Supported * Thousands of New Users Every Day*
/____/_/_//_/\_,_/ /_/\_\ The Cost Effective Choice - Linux Means Business!
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
