PPPoe

pnutjam · Oct 19, 2010, 3:35 AM

I would like to share an issue I have been having with PPPoe. I have been using 1.2.3 on a cable modem, DHCP. I switched to DSL and configured my DSL modem for passthrough so my pfsense system could perform the PPPoe authentication and receive and addressable IP. It worked great, so I decided to try the latest 2.0 release.

The PPPoe setup seems to have changed drastically. If I define PPPoe as the connection type, it generates a PPPoe interface. I could not figure out if I should assign my WAN to the rl0 interface it was assigned to in 1.2.3 or to the new PPPoe interface. It seemed to work if I assigned the wan to the rl0 and the PPPoe interface to wan. However, if the connection dropped, it would not reconnect until I rebooted the modem and dicked around with the config for half an hour, i don't think I ended up with anything different, it just managed to reconnect, for awhile.

The other problem was that I could not update a dynamic DNS site, my log indicated there was no IP assigned to the WAN interface. The IP seemed to be assigned to the PPPoe interface.

Eventually I tried to revert using my backed up slice, I'm on nanobsd, but that did not work and I had to rebuild from scratch.

Any feedback is appreciated, I have a second m1n1wall I can configure with pfsense 2.0 for testing.

clarknova · Oct 19, 2010, 6:13 AM

In 2.0 you want to go to Interfaces>Assign>PPPs. Create a pppoe interface using the physical interface (rl0 in your case). Next go to Interfaces: Interface Assignments and use the drop-down to assign PPPOE0(rl0) to the WAN. Save, Apply. You should be in business.

infinityloop · Nov 3, 2010, 12:32 PM

@clarknova:

In 2.0 you want to go to Interfaces>Assign>PPPs. Create a pppoe interface using the physical interface (rl0 in your case). Next go to Interfaces: Interface Assignments and use the drop-down to assign PPPOE0(rl0) to the WAN. Save, Apply. You should be in business.

Even though I did as you explained.
The dashboard shows me that the wan interface is "dissabled" - which it is not inside the interfaces section.
trying to press the connect button results in …. nothing.

Tested beta 4snapshot available yesterday.

chpalmer · Nov 3, 2010, 3:38 PM

I had to invoke the setup wizard to make it work finally here… Had the same problem getting it to work as you have...

infinityloop · Nov 4, 2010, 6:10 AM

@chpalmer:

I had to invoke the setup wizard to make it work finally here… Had the same problem getting it to work as you have...

Did not work here.

What I had to do to get the connection up was to select that new option for "empty servicename".
Without that option set, it would just not connect.

Then I tried to add the 2nd wan connection i have here. But there beta 4 fails miserably.
The only way to get both connections "up" was by rebooting the box.
Inside the "Status - interfaces" section, the disconnect button does not have any effect.
If one of the connections goes down -> reboot required.

I think I will wait for RC1 before trying again. back to 1.2.3 for now which just works. ;)