From: Georgi Alexandrov <georgi.alexandrov@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Shaping of pppoe clients
Date: Wed, 24 May 2006 06:51:14 +0000 [thread overview]
Message-ID: <44740262.4000108@gmail.com> (raw)
In-Reply-To: <fad9d4840605230212p47c5be27yb12f65bdf6bcb347@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 936 bytes --]
Kenneth Kalmer wrote:
> The keyword here is "better", and that was my argument for using a
> bridge in the first place. It would appear to be easier to shape &
> filter away from the messy scripts of pppd & radius servers, but this
> raises the next issue. For the bridge, is the pppoe sessions
> identifiable using say source & destination ips, as opposed to pppoe
> traffic... I know if I perform a tcpdump on the interface that I
> connect to my adsl modem I only see the traffic as pppoe... Logic
> tells me that the bridge would suffer the same consequenses...
Yes, that was my concern too. Maybe someone else on the list that has
already
went trought this may share the experience.
I will test it as soon as I get my hands on a spare machine ;-)
--
regards,
Georgi Alexandrov
key server - http://pgp.mit.edu/ :: key id - 0x37B4B3EE
key fingerprint - E429 BF93 FA67 44E9 B7D4 F89E F990 01C1 37B4 B3EE
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-05-24 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 9:12 [LARTC] Shaping of pppoe clients Kenneth Kalmer
2006-05-23 10:32 ` Georgi Alexandrov
2006-05-23 12:12 ` Kenneth Kalmer
2006-05-24 6:51 ` Georgi Alexandrov [this message]
2006-06-01 20:29 ` Andy Furniss
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=44740262.4000108@gmail.com \
--to=georgi.alexandrov@gmail.com \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.