PPPoE problems after upgrading from 2.4.2 to 2.4.4

cetteup

@netblues Rebooting does fix it, thanks. However, it doesn't seem ideal to have to reboot anytime you assign a (virtual) interface.

netblues

try disabling and re enabling, you will probably end up to the same issue. The thing is no one has a clue what is causing this.

cetteup

@netblues It actually looks like just ANY change to ANY interface will cause these pppoe-issues. I just changes my OPT1 static ip address and even that killed my pppoe until I rebooted.

stephenw10

Did you try running that command? I assume it did not log any errors there?

Try running ifconfig -av when it's working and when it's not. See if there's anything different there.

It's hard to believe it would change when altering another interface but you could also check the generated file at /var/etc/mpd_wan.conf. Does that change?

Steve

cetteup

@stephenw10 Thank you very much for your continued efforts. And just to be clear: My PPPoE connection works fine unless I change any setting of any interface - then I have to reboot.

clog [...] secret did not result in any output.

Here's what ifconfig -av returns when things are fine:

0_1539186760802_Screenshot from 2018-10-10 17-51-43.png

And when PPPoE is broken:

0_1539186777441_Screenshot from 2018-10-10 17-51-53.png

The conf file does not change.

[Sorry for posting screenshots, anti-filter would not let me post the output as text]

netblues

Please do something with akisment. It doesnt allow output posts.

Situation is exactly the same over here.

jimp

@netblues said in PPPoE problems after upgrading from 2.4.2 to 2.4.4:

Please do something with akisment. It doesnt allow output posts.

Situation is exactly the same over here.

Wrap the output in code tags
or
Attach long output as a text file, rather than dumping it all in the post

Both are good forum etiquette and will avoid issues with posts being flagged as spam.

netblues

Unfortunately its the tagged code text that is not allowed by akismet..
Heuristic analysis of what is spam and what is not fails miserably.
Will try attachements next time.

On topic, I have 3 instances, one is a physical box running on intel nuk hardware and two are virtual under centos kvm.
All three of them talk to the same bridge modem devices via vlan trunks.
The two virtual ones have been reverted to 2.4.3p1 and work fine.
The physical one (on 2.4.4, updated from 2.4.3p1) needs to reboot every time something changes on ppp
(provider allows three concurrent ppp calls)
The only purpose of the physical box is to test 2.4.4 issues. Unfortunately, since it only has one physical lan, can't test without vlans.
On the other hand, if everyone had issues with simple pppoe there would be lots of complain threads by now.
I suspect it has to do with permssions and/or file ownersip, which is corrected upon reboot. If it was a config issue, rebooting would never fix it.
Any pointers on what to look for?

Joxxxx

I'm estonished that there are not more posts about this pppoe problem on 2.4.4. Maybe there are not so many people using pppoe after all ?
Since upgrading from 2.4.3 to 2.4.4, my pppoe doesn't work anymore neither. I also get these weird errors like you stating "file not found" or "not allowed to allocate ip address". Reboot doesn't fix it though, sadly.

It's super annoying because I had to revert back to 2.3.3 and I cannot use any package anymore because I get the following error when trying to install one :

WARNING: Current pkg repository has a new PHP major
         version. pfSense should be upgraded before
         installing any new package.
Failed

Did someone found out why the new pppoe connection layer is failing for some and not for others ?

netblues

Are you using vlans for pppoe?

Joxxxx

@netblues No, it's not needed by the provider.

netblues

@joxxxx Im not talking about the provider, just as a means of adding more than one interface on a machine that just has one via a managed ethernet switch
It seems the problem exists when vlans is involved.
And rebooting or just hitting connect seems to fix things.
Perhaps you are facing a slight different problem?

Joxxxx

@netblues Oh ok, I thought you wanted to know if the connection itself had a special vlan (some providers ask for that).
No, I don't use any vlans. I have 2 wan : 1 pppoe ftth and 1 cable. Only the pppoe fails on 2.4.4.

It's maybe another problem, but I tried everything I could, nothing helped. It's really strange... The connection works flawlessly when directly wired to the pc, on vyOS, sophos, pf2.4.3 but not on pf2.4.4 or pf2.4.5. Something changed, but what ?

netblues

@joxxxx Have you tried recreating the ppp connection on pf 2.4.4 from scratch?

Joxxxx

@netblues yes, tried first by updating, then by installing a fresh 2.4.4 and importing the settings and then on a fresh 2.4.4 and manually creating the pppoe connection. Didn't work with the same errors all the time.

For info, I'm running it on esxi 6.5 with a quad gigabit eth card.

netblues

@joxxxx I suppose you have disabled all 3 hardware offload options on advanced/networking.
(meaningless for a virtual network interface, by design...)

And what are the exact errors?

Joxxxx

@netblues Actually, Hardware TCP Segmentation Offloading and Hardware Large Receive Offloading were disabled, but not Hardware Checksum Offloading.

The errors are :

[opt1] IFACE: Adding IPv4 address to pppoe0 failed(IGNORING for now. This should be only for PPPoE friendly!): File exists

[opt1] IFACE: Removing IPv4 address from pppoe0 failed(IGNORING for now. This should be only for PPPoE friendly!): Can't assign requested address

It then cycles infinitely, each time getting a new wan ip and throwing the same errors.

Thanks a lot for your help !

netblues

@joxxxx This is something else. Have you tried with hardware checksum offloading disabled?

Joxxxx

@netblues Not yet, I'll boot up the 2.4.4 vm and test it out. (On 2.3.3 hardware offloading doesn't change anything).

Joxxxx

Ok, just tried it and still the same, here some more logs (appart of the recurring file exists etc. from above) :

Nov 22 14:00:50 	ppp 		[opt1] IFACE: Up event
Nov 22 14:00:50 	ppp 		[opt1] IFACE: Rename interface ng0 to pppoe0
Nov 22 14:00:50 	ppp 		[opt1] IPCP: rec'd Configure Ack #3 (Ack-Sent)
Nov 22 14:00:50 	ppp 		[opt1] IPADDR 188.XX.XX.XX
Nov 22 14:00:50 	ppp 		[opt1] IPCP: state change Ack-Sent --> Opened
Nov 22 14:00:50 	ppp 		[opt1] IPCP: LayerUp
Nov 22 14:00:50 	ppp 		[opt1] 188.XX.XX.XX -> 10.0.0.1
Nov 22 14:00:50 	ppp 		[opt1] IFACE: Adding IPv4 address to pppoe0 failed(IGNORING for now. This should be only for PPPoE friendly!): File exists

Strange thing is that it talks about ipv6 although I disabled it everywhere I could. It seems like on 2.4.3 it doesn't do that.

Even updated to 2.4.5-dev to see, but still the same.