> But the current problem is this: It runs fine for a few days (3-5) then
> all of a sudden quits working. When I say "quits working" I mean one time
> I send out some packets it will bring up the link to my ISP then all of
> a sudden the next time it won't. it continues to "not work" until I kill
> diald and restart it, after which it is fine again for a few more days.
Yes, I have noticed the same behavior on my LRP setup and found
it infuriating: it makes diald worse than useless, IMO.
Frankly, I wonder if the problem doesn't have something to do with
the 2.0.36 kernel. Does your RH 5.2 use 2.0.36 perhaps?
I used tcpdump to snoop diald's slip interface while pinging an
Internet IP. I found that the kernel was simply not forwarding the
ping packets sent to it to diald's slip interface. They just
disappeared into the ether.
I also did a system trace of diald in its hung state which makes me
think that the problem lies with the kernel and not diald: diald was
looping endlessly waiting for a packet to appear despite the fact
that ping was sending a steady stream of packets to diald's slip
interface.
Ed G.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
