From: Michal Ostrowski <mostrows@earthlink.net>
To: linux-ppp@vger.kernel.org
Subject: Re: 4 adsl lines in one nic
Date: Fri, 02 Jun 2006 18:35:43 +0000 [thread overview]
Message-ID: <1149273344.6507.163.camel@brick> (raw)
In-Reply-To: <20060602131035.sdpe7qwh59c084ow@webmail.fcq.unc.edu.ar>
Ah... do you know if you are even using the kernel-assisted pppoe? I
assume that is not the case.
On Fri, 2006-06-02 at 14:04 -0300, Marcos Dione wrote:
> Quoting Michal Ostrowski <mostrows@earthlink.net>:
> > The Linux kernel component identifies PPPoE sessions using (SID,MAC
> > ADDR) pairs. Thus, it should handle this case correctly.
> > (See /proc/net/pppoe for a current listing of active sessions.)
>
> I have no such file here, not even in the whole /proc tree. kernel version
> is 2.6.15-1-686 from debian etch.
>
--
Michal Ostrowski <mostrows@earthlink.net>
next prev parent reply other threads:[~2006-06-02 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 16:10 4 adsl lines in one nic Marcos Dione
2006-06-02 17:04 ` Marcos Dione
2006-06-02 18:35 ` Michal Ostrowski [this message]
2006-06-05 14:29 ` Marcos Dione
2006-06-05 14:34 ` Michal Ostrowski
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=1149273344.6507.163.camel@brick \
--to=mostrows@earthlink.net \
--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).