From mboxrd@z Thu Jan 1 00:00:00 1970 From: Georgi Alexandrov Date: Wed, 24 May 2006 06:51:14 +0000 Subject: Re: [LARTC] Shaping of pppoe clients Message-Id: <44740262.4000108@gmail.com> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============1090301881==" List-Id: References: In-Reply-To: To: lartc@vger.kernel.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============1090301881== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigDF2BD5B93E9D5EED02D5CFE9" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDF2BD5B93E9D5EED02D5CFE9 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable 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 ;-) --=20 regards, Georgi Alexandrov key server - http://pgp.mit.edu/ :: key id - 0x37B4B3EE key fingerprint - E429 BF93 FA67 44E9 B7D4 F89E F990 01C1 37B4 B3EE --------------enigDF2BD5B93E9D5EED02D5CFE9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEdAJi+ZABwTe0s+4RAnxyAJ0VaCuuENJu2vjSxbT8/TifOTc1kwCeIKR/ 02wNrDvQ9CGVxKrhnrHKy0I= =Y9gX -----END PGP SIGNATURE----- --------------enigDF2BD5B93E9D5EED02D5CFE9-- --===============1090301881== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc --===============1090301881==--