On 29-Jun-2000 Adrian Chiang wrote:
> I got diald 0.99 configured and connecting fine the first time.
> But everytime that I lose the connection, Diald does not re-dial.
> Only way is to kill it and restart diald.
I'm using diald-0.99 at home with RH6.0 + 2.2.14 kernel, and it works fine.
Well, OK, I did recently have a problem with it not seeing TCP closes - patch
mailed to Mike Jagdis - but that isn't your problem.
Your config looks OK to me, with the proviso that I'm not familiar with the
ipcp-accept-remote parameter. I don't have diald handy (at work now), so I'm
not sure what it does. Apart from that the only other significant difference in
our setups is that I use ethertap rather than slip.
The ioctl chatter in the logs is perfectly normal, BTW.
Couple of things to try:
1. Check your routing table before and after the connection. Is it the same?
2. Fire up dctrl and check diald's internal state after the connection. Does it
see the packets requesting the link come back up and ignore them? Does
it try dialling but the connect fails? If this happens enough times, diald
will decide the other end has died and will not try it again until restarted.
--
Jim Hague - [EMAIL PROTECTED] (Work), [EMAIL PROTECTED] (Play)
Never trust a computer you can't lift.
--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to [EMAIL PROTECTED] with
unsubscribe in the text
