I tried to use diald to manage a ppp connection to my ISP.
I have Red Hat 5.2 ( kernel 2.0.36 ) and I installed diald package
0.16.5a and ppp 2.3.5-1.
Diald establishes correctly the first connection, if an application
needs it (Netscape, ftp...),
and also closes it when time is out.
Obviously I checked out that the "dynamic" option in the .filter file
had been set, to get dynamically the address from the ISP.
The first time the connection comes up everything seems to be all right:
the matter is with the further ones.
Now, try to suppose that an established connection times out so that
diald closes it.
Of course diald attempts to bring it up again if it's needed.
Well, the second time a different address is given (still nothing
strange here), but
sometimes I still see packets whose source address field is filled with
the old IP address
(that is the one of the first connection): as if my computer had somehow
memory of his old address.
These packets keep up the link against my will or make diald open a new
one even
if it's already been down.
I used configuration and filtering files found with the
rpm package (diald.defs diald.conf standard.filter or phone.filter
(tried both)).
I used tcpdump and dcrtl to monitor these packets and I found out that
they contain datas or requests
for the last sites (www or ftp) I visited before the link went down.
Obviously it all repeats over the third connection: there are packets
with the first and the second
IP address circulating. And so on...
I can't understand which process could generate them, or if they belong
to a TX queue whose existence I ignore,
or what else? I'm stuck with it, it's a really teasing matter.
If anyone could help me, I'd be glad.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
