This change does indeed fix the issue for all the sites that were
having problems. This may be common enough now with an ISP as large as
AT&T requiring it that it should be exposed in the webGUI (unless mpd
itself can be fixed). Otherwise I think people won't look into it far
enough to find the resolution and just assume it doesn't work. I'll
add it to the FAQ, but I still think it should be considered for the
On Jan 3, 2008 5:17 AM, Adam Armstrong <lists at memetic dot org> wrote:
> I'm glad we didn't see the same bad behaviour on the m0n0wall list as on
> the pfsense list with regards to this issue.
> It was sad to see lead pfsense developers spitting at AT&T/Bellsouth and
> refusing to acknowledge there could be an issue elsewhere.
> Just my impression.
This was uncalled for and misleading, if not an outright lie. I said
in that thread I was going to look into this issue before anyone
brought it up here, there was absolutely no "refusal to acknowledge
there could be an issue". Those of us who deal with Bellsouth on a
routine basis have more than adequate justification to "spit at" them,
trust me! :) I won't bother to detail the conversation on this issue
I attempted with their technical support, suffice it to say I think
the most that person knew about PPPoE is it's comprised of 5 letters.