--7/n32iUg2MEZqnOh
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Apr 20, 2005 at 01:32:19PM -0400, C=E9sar Catri=E1n C. wrote:
[...]
> > > > If it talks PPPoA to the modem, then why would it offer a PPPoE int=
erface
> > > > instead of directly a PPP interface?  This looks completely bogus.
> > >=20
> > > The pppoa2 program talks only PPPoA to the modem_run program (the USB=
 modem=20
> > > driver), and at the same time it offers an ethernet like interface fo=
r use with=20
> > > our PPP implementation for the authentication, etc.
> > >=20
> > > net/speedtouch out of the box uses net/userppp to work, and userppp a=
ccept the=20
> > > output of pppoa2 piped as a device in the config file. But I wanted t=
o use=20
> > > native PPP.
> >=20
> > But userppp and pppoe are very different things.  The kernel equivalent
> > of userppp is ppp(4) and the userland equivalent of pppoe(4) is
> > rp-pppoe.  The fact that your current setup works (with its drawbacks,
> > but still) means that you're actually doing PPPoEoA (that is, with an
> > added Ethernet layer).  If userppp can work with your DSL installation,
> > you'd better try using ppp(4) if you want the native implementation,
> > because involving Ethernet in this only brings trouble, notably with
> > tht MTU.
>=20
> The main reason I quit using userppp was for the MTU issues, problems whi=
le
> setting the default route, etc.

What MTU issues with userppp?  I don't know any, and compared to the
whole mess PPPoE is about it...

> So I looked at ppp(4), but doesn't allow to specify a program (pppoa2) as=
 a device
> as userppp does. And at the same time, pppoa2 provides bridging option (-=
b) to=20

Sure it does.  pppd pty "my program".

> use a ethernet interface. The rest was to use native PPPoE with my setup.

Well, I strongly advise you to avoid PPPoE at all cost.  userppp simply
_cannot_ be as bad as having to use PPPoE.

If you want, I can have a look at making net/speedtouch work with
ppp(4).  I know that last time I tried (about 3 years ago...), it
didn't work for some strange reason I couldn't properly investigate,
and userppp was working reasonably enough for me.  However, its lack
of support to maintain the link with LCP Echo packets is annoying,
which is a good reason to switch to pppd(8).

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"When I find the controls, I'll go where I like, I'll know where I want
to be, but maybe for now I'll stay right here on a silent sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.

--7/n32iUg2MEZqnOh
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)

iQEVAwUBQmaVtNgoQloHrPnoAQI59gf/eWfHqBPSNF87ORIGf2tnFhmrLg2DFR7K
Q7QisKzDOraTyRQCHRSOkicUPpAtCBFxhtEW9sbYYI/6bfZp2FzQQV9zPmV59Fwt
DxlqsE2G2JqYo4okhyj4e17fBgT5je8WOWiYj0qqgyjObNLnG33ygyndIa2nsCaM
Y6osOYRC/k3UsjMT3etOLwRbAbUcSE58rUcSxIinUi7ESj5JXak2FkWV5iqh/sxv
iMKuZMZ7EqHQi5ZkWswgUvFkHSlz1nq9yTOCK3EBe+FKdEkkWbU6uFaiYOG6dOoe
06B6es46MrIyDiCMH7CddW8s/JXwr1utxP8qD53hbDqGkPsrD0kjtQ==
=7flS
-----END PGP SIGNATURE-----

--7/n32iUg2MEZqnOh--