Subject: Re: pppoe problem
To: Martin Husemann <firstname.lastname@example.org>
From: Christopher Vance <email@example.com>
Date: 12/14/2001 19:41:26
Martin, hi, and thanks for a really prompt response.
On Fri, Dec 14, 2001 at 09:10:12AM +0100, Martin Husemann wrote:
: This sounds like a path mtu discovery blackhole. Without MSS clamping
: you won't be able to fix this.
After checking on google, I found rp-pppoe. I'll try that now. I'd
prefer to use the base system pppoe when it works, so I'll be
: > (I'm not convinced ifwatchd is working yet, and getting the default
: > route installed was a pain, but I seem to have done it.)
: It works if your -current is not older than ~ Dec 11.
Mine's from the 7th, so it sounds like I need to update.
Unfortunately cvsup doesn't maintain CVS admin files, so something
other than cvsup is likely to require even more traffic to catch up.
I'll give it a go.
I want to notice up/down to fix ipf rules for my dynamic address, and
to kick ntp.
: There is now a pppoe(4) man page, explaining how to set it all up, including
: the routing. I'm using pppoe without link1 flag (so it connects imediately)
: and have "route add default $3" in my /etc/ppp/ip-up script (and a coresponding
: "route delete default" in /etc/ppp/ip-down).
I got most of my setup by reading the pppoectl man page.
I discovered -link1 by reading if_pppoe.c, noticing the mention of
sppp, and then reading if_spppsubr.c. :-)
Looks like some things are still under development. I'll be watching. :-)