linux-ppp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cristi Mitrana <cristi.mitrana@gmail.com>
To: linux-ppp@vger.kernel.org
Subject: Re: Linux Greatest Feature
Date: Mon, 18 Jul 2005 13:36:34 +0000	[thread overview]
Message-ID: <f1de940b05071806368720815@mail.gmail.com> (raw)
In-Reply-To: <dbfm3g$h6$1@sea.gmane.org>

 hello, 

> Under Linux this doesn't happen. I get disconnected, and I have to wait
> for the sockets to TIMEOUT. So I end up with Psi spewing things into a
> blackhole, and Thunderbird flat out screws up and can barely function.
> 
> A long while back I made a post about this to the Linux PPP mailing
> list. The reason that was laid out is that sockets and the devices are
> in seperate layers so a socket doesn't know what device it is on. That's
> nice if you have an ethernet cable powering a static IP, and you like to
> unplug it just for shits. It's not so nice when you're on a dynamic IP
> and well, those connections just don't make any sense anymore.
>

 The behaviour you describe I see it as an advantage, it keeps your
connection 'up' even if the link goes down, say ppp disconects
accidentally and you have not finished transfering you files, ppp
connects and the link is up again, so the transfer continues without
interruption. This is ok for TCP/IP  connections, for some other this
might not be the case.
  The timeouts for the link to announce itself as 'down' can be
customized with the '/proc' (sysctl) interface, so you can customize
it. The linux kernel has by default a bigger timeout than MS Windows'
kernel/net stack so that's why you perceive the difference more
easily.

hth,
 mitu

      reply	other threads:[~2005-07-18 13:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-18  7:35 Linux Greatest Feature Nolan Eakins
2005-07-18 13:36 ` Cristi Mitrana [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f1de940b05071806368720815@mail.gmail.com \
    --to=cristi.mitrana@gmail.com \
    --cc=linux-ppp@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).