PPPoE not usable in current AirOSV releases [Archive]

jacobsuter

09-14-2009, 12:16 PM

I was wondering when the ETA is for a software release with working PPPoE mode?

I've sent support what they need to know to release a version of the firmware that will work. Essentially all that is wrong is the pppd included in AirOS-V writes its resolv.conf file to /etc/ppp/resolv.conf instead of the correct location at /etc/resolv.conf.

This also should have been caught in the earliest of beta tests since it *always* happens and its *always* a show-stopper. Do you have any real WISPs as beta testers? Does this stuff get tested at all before its released?

I tested the shipping firmware and 5.0.2-RC.

UBNT-Mike.Ford

09-14-2009, 02:26 PM

I was wondering when the ETA is for a software release with working PPPoE mode?

I've sent support what they need to know to release a version of the firmware that will work. Essentially all that is wrong is the pppd included in AirOS-V writes its resolv.conf file to /etc/ppp/resolv.conf instead of the correct location at /etc/resolv.conf.

This also should have been caught in the earliest of beta tests since it *always* happens and its *always* a show-stopper. Do you have any real WISPs as beta testers? Does this stuff get tested at all before its released?

I tested the shipping firmware and 5.0.2-RC.

Hello,

I have asked my software guys for an update.

Thanks,

drwho17

09-15-2009, 12:11 AM

They are aware of this issue, Ubiquity forgot a few scripts in their 5.0 build. I reported the DNS proxy issue to them, it's not a PPPoE issue per say, it's a DNS proxy issue to clients. If you specify the DNS on your clients behind the router they work fine.

UBNT-Edmundas

09-15-2009, 12:45 AM

I was wondering when the ETA is for a software release with working PPPoE mode?

I've sent support what they need to know to release a version of the firmware that will work. Essentially all that is wrong is the pppd included in AirOS-V writes its resolv.conf file to /etc/ppp/resolv.conf instead of the correct location at /etc/resolv.conf.

This also should have been caught in the earliest of beta tests since it *always* happens and its *always* a show-stopper. Do you have any real WISPs as beta testers? Does this stuff get tested at all before its released?

I tested the shipping firmware and 5.0.2-RC.

This problem will be fixed in upcoming v5.0.2 firmware release. In v5.0.2-rc needed fix was not implemented.