strange behavior on pfsene PPOE

dominik.b

Hello everyone,

I have found quite a few posts about problems with PPOE connections at the moment.

I have a similar problem but can confirm that in my case it is really spooky.

BTW: I made a post on lawrencesystems.com Just in case someone finds the other post :-) But I think it's better to post it here.

#####################

Hi there,

I have a very strange behaviour on my Pfsense.

It looks a lot like the problem here:

PPOE Problem

BUT here is the funny part :-)

The whole setup worked with pf 2.2.xx or so. That was 4 years ago.

Now, when I try to do the same thing again, it does not work.

AND if I restore the old backup, it works ???

AND I took screenshots of every page in the setup and copied everything 1:1 to the new installation, but still no luck.

So in my case the Vigor160 is not the problem or at least there is a setting that is not available via the GUI?

At the moment I am deleting everything in the working backup until there is nothing but the bare installation and hopefully I will find a solution to this mysterious problem.

But if you have any idea where to look, I’d be very grateful.

Update1
It gets even better

When I delete all the unnecessary stuff and finally run the PPOE setup wizard again, it fails?!

So I made a backup before and after running the wizard and found that there is a difference in one line.

0
pppoe
pppoe0
re0
xxxx@xxxx.xx
--------ZH-----ub------=
yyyy

--------dH-----1b------=
on

Where “y” and “on” and the visible letters between the “-” are different.

Does this ring a bell or is it just a coincidence?

UPDATE2:
The old config backup is working fine, probably on older pfsense versions as well as on the latest version.

BUT if I start from 0 with a fresh installation of pfsense it´s not working.

I might have a clue here, because of 100 of reboots I always see the message:

Configuring WAN interface..[fib_algo] inet.0 (bsearch4#26) rebuild_fd_flm: switching algo to radix4_lockless

I did read that this function is not present anymore in pfsense, could that be the reason?

Regards, Dom

dominik.b

Ok Problem solved.

Issue can be closed