On Sun, Nov 10, 2002 at 08:44:33PM -0600, Richard Rauch wrote:
> I know that TCP can't handle it.  That's why this seems like a ``good
> thing'' for ssh to be able to recover from.  I'd hoped that it was a
> feature that was built into ssh.  Alas, from what you say, ssh doesn't
> provide recovery for this, either.  I know I'm not the first person to
> want/need such a thing (else GNU screen wouldn't have it; (^&).

GNU screen is much, much older than ssh

> Unfortunately, so far as I know, you can't use GNU screen's support to
> carry anything other than a text/console/shell type session.

vnc can do the same for X11

> 
> 
> >
> > NetBSD's pppoe doesn't use the ppp daemon, all is happening in kernel.
> 
> I thought our ppp device was in the kernel.

For ppp over serial, there is a device in the kernel, and a daemon to
manage it (and handle auth, etc ). In case of pppoe or sppp, all is in the
kernel.

> 
> 
> > pppoe should be able to do it. Try:
> > ifconfig pppoe0 link1
> > You may also want to tweak the idle-timeout parameter with pppoectl
> 
> Hm...okay, thanks.  What's the LCP timeout about (I have left it at the
> default 1 second setting, but don't know what it means).

LCP is some kind of ping happening at the ppp protocol level. It's used to
see if the peer is still reachable. After sending a LCP echo request,
it'll wait  "lcp-timeout" for a reply. I think it'll wait for several
consecutive missing LCP echo reply before making the link dead, but I didn't
find this info in the man page.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 23 ans d'experience feront toujours la difference
--