public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Schlenstedt <mailinglists_michael@schlenn.net>
To: paulus@samba.org
Cc: ppp-bugs@samba.org, Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: [pppd] increasing limit of transfered bytes - kernelbug?
Date: Wed, 31 Jul 2002 18:20:17 +0200	[thread overview]
Message-ID: <20020731162017.GA1424@schlenn.net> (raw)

Dear all!

I wrote a little script which logs the amount of bytes which were transfered
over a ppp-line (ADSL/PPPoE).

The problem: this only works untill you do not transfer more than 2 GB
(pppd-limit) or 4 GB (kernel-limit).

Within pppd it seems that there is a problem with the $BYTES_RECVD and
$BYTES_SENT variables which can be used in /etc/ppp/ip-up and -down.

PPPD uses "signed int"-counters instead of an "unsigned-int". This is
not a great problem, a patch is attached to this email (thanks to Evgeni
Gechev).

Unfortunately, this only increases the amount of transfered bytes to 4
GB (kernel-limit).

Is there any chance to increase the kernel-limit in feature
kernel-releases?

Bye,
Michael

,----[ pppd patch ]-
| 
| --- main.c      Fri Jan 25 15:03:38 2002
| +++ main.c.etg  Fri Jul  5 00:18:25 2002
| @@ -1090,9 +1090,9 @@
| 
|      slprintf(numbuf, sizeof(numbuf), "%d", link_connect_time);
|      script_setenv("CONNECT_TIME", numbuf, 0);
| -    slprintf(numbuf, sizeof(numbuf), "%d", link_stats.bytes_out);
| +    slprintf(numbuf, sizeof(numbuf), "%u", link_stats.bytes_out);
|      script_setenv("BYTES_SENT", numbuf, 0);
| -    slprintf(numbuf, sizeof(numbuf), "%d", link_stats.bytes_in);
| +    slprintf(numbuf, sizeof(numbuf), "%u", link_stats.bytes_in);
|      script_setenv("BYTES_RCVD", numbuf, 0);
|  }
| 
`----


                 reply	other threads:[~2002-07-31 16:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020731162017.GA1424@schlenn.net \
    --to=mailinglists_michael@schlenn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=ppp-bugs@samba.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