> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Joe Pfeiffer
> Sent: Tue, Jun 22, 99 9:58 PM
> To: [EMAIL PROTECTED]
> Subject: immediate hangup on demand dialing
>
>
> I've been using diald-0.16 for some years with no problem. Last
> weekend I upgraded to RH 6.0, so I upgraded to diald-0.99.1 while I
> was at it. I'm now not able to get demand dialing to work -- moments
> after establishing a connection, it announces it is taking down an
> idle link. If I force the connection up, it stays up. In what
> follows, I have one major and two minor questions:
>
> (major) how can I get my link to come up and stay up?
I also recently upgraded to 0.99.1. I use my linux machine mainly as an
internet gateway for a couple of Windows machines so my link normally is
activated because of an http request. I just make sure that I hit the
refresh button when I see the ppp connect info displayed in the "tail
/var/log/messages" window. :-) Then I have the http disconnect time instead
of the nearly instant disconnect associated with the packet that caused the
connection. I also change the http timeout to 600 seconds from 120 seconds.
I guess the proper solution would be to lengthen the timeout on whatever the
packet type is that causes the connection in the first place.
> (minor) what is the purpose of an Ethertap device, and why should we
> now be using them? I didn't find the description in
> /usr/doc/kernel-doc-2.2.5/networking/ethertap.txt to be much help.
> (minor) what is the meaning of the errors relating to SIOCSIFMETRIC?
> I haven't been able to find that symbol in the kernel
> include files,
> nor in the source for diald.
Me, too.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
