Hi Erik,
many thanks for enlightening the end of the tunnel!
Erik Corry wrote:
>
> On Fri, Aug 07, 1998 at 08:04:52PM +0200, Thomas Michalka wrote:
> > the link was hold/brought up caused by packets which came from an IP address
> > outside of my system, moreover, the IP number is one of my provider's pool!
> > The destination also is anywhere in the world.
>
> The IP number is an old one which your machine used to have, but
> doesn't have any more. The problem is caused by stuck sockets
> which cannot close because they have an old address, and so never
> get any answers from the remote end, which would let them close.
Sounds like a basic problem with demand diallers, and why didn't I have it with
diald 0.14 (a lot of others with this version ?-P ), but now with 0.16?
But what causes the socket to still remain after diald has disconnected?
> Solve this with
>
> echo 5 > /proc/sys/net/ipv4/ip_dynaddr
And why do I have to manually clear the socket? I want diald to do this or
anyway to be done automatically!
How can I solve this problem in an elegant way?
Can't diald close the socket when it brings a link down?
> See /usr/src/linux/Documentation/networking/ip_dynaddr.txt
> for details. You need at least 2.0.34 for this to work
> (slightly older if you have a SuSE kernel rather than
> straight Alan/Linus).
I have SuSE system with kernel 2.0.33, young enough?
>
> > But here I'm at the end with my latin (is this a possible phrase in English?),
>
> Afraid not :-).
'Latin' here stands for 'knowledge', I just translated the German phrase ;-) How
would you say in English?
Many thanks for dealing with my problem!
Best regards, Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
