PPPoE with Vlan tag Internet does not work 2.4.1

bigbird007

Hi all

I thought i would share this here , I had upgraded to 2.4.1 from 2.4.0 however my internet would not work.
I also did a clean install of 2.4.1 and same thing.

My isp is Internode and its a cable modem.

The Config is your standard username and password and also I need to create a Vlan tag 2 and link it to the wan interface.

So it looks like it won't connect all with 2.4.1, Rolling back is fine and internet is working with the above settings.

Something maybe broke with Vlan on the wan side though i am not an expert.

Is anyone else with a isp that you requires a vlan tag on the wan side but is failing since 2.4.1?

Feel free to ask more questions

cheers guys

Grimson

https://forum.pfsense.org/index.php?topic=138804.msg758710#msg758710

bigbird007

Thanks Grimson I should of searched a bit harder

epek

Same problem here. But the solution above doesn't work for me. (No lagg in config.xml, adapting vtnet0 accordingly, leads to unassigned interfaces on reboot, when replacing all occurencies accordingly. Manually chaniging only the vlan und pppoe sections does not help either - interfaces assignment works again, but pppoe still does not.)

The PPPoE Client ceased working right after upgrading from 2.4.0 to 2.4.1.

Furthermore - with a backup default gateway, manually configured - package updates fail. e.g. a shell dependency of freeradius3:
https://pkg.pfsense.org/pfSense_v2_4_1_amd64-pfSense_v2_4_1/All/bash-4.4.12_2.txz

Despite name resolution is working here I see a „host not found“ message. I also tried to manually download that from a different client (with wget) and through an LTE connection. All the same pkg.pfsense.org does not exist.

For the PPPoE problem - reinstalled 2.4.1 from it's clean CE iso, restored the config - same error. I reconfigured the pppoe connections from the scratch - same error behaviour.

BTW, there is even more: MTU settings are missing on the "Advanced and MLPPP" tab. I used to have baby jumbo frames configured there.

For the logs: System logs/PPP show setting the MTU, a try to connect and no data. Just as when using the wrong vlan.

I reverted to a virtual disk of 2.3.x - worked all well. I guess 2.4.1 didn't receive sufficient testing. Blame on me.