22.05.b.20220513.0600 pppoe Cannot attach to ng_ether message: Invalid argument.

netblues

pppoe fails to start after upgrading to 22.05 beta (from 22.01

This is running under redhat kvm, with vlans.
However vlans are handled at the kvm level, so pfsense just sees different interfaces.

May 15 19:50:46 	ppp 	27472 	[wan_link0] Link: reconnection attempt 1 in 2 seconds
May 15 19:50:46 	ppp 	27472 	[wan_link0] LCP: Down event
May 15 19:50:46 	ppp 	27472 	[wan_link0] Link: DOWN event
May 15 19:50:46 	ppp 	27472 	[wan_link0] PPPoE node for link is not initialized
May 15 19:50:46 	ppp 	27472 	[wan_link0] PPPoE: Error creating ng_pppoe node on vtnet0:
May 15 19:50:46 	ppp 	27472 	[vtnet0] Cannot attach to ng_ether message: Invalid argument.
May 15 19:50:46 	ppp 	27472 	[wan_link0] LCP: LayerStart
May 15 19:50:46 	ppp 	27472 	[wan_link0] LCP: state change Initial --> Starting
May 15 19:50:46 	ppp 	27472 	[wan_link0] LCP: Open event
May 15 19:50:46 	kernel 		ng0: changing name to 'pppoe0'
May 15 19:50:46 	ppp 	27472 	[wan_link0] Link: OPEN event
May 15 19:50:46 	ppp 	27472 	[wan] Bundle: Interface ng0 created
May 15 19:50:46 	ppp 	27472 	web: web is not running
May 15 19:50:46 	ppp 	27472 	process 27472 started, version 5.9
May 15 19:50:46 	ppp 	27472 	Multi-link PPP daemon for FreeBSD

stephenw10

Do you see it failing like that everytime it tries to start?

There have been some changes to netgraph but I have PPPoE clients running here without issue.

Steve

netblues

@stephenw10 Yes, same message appears constantly

I see a relevant bugfix
https://redmine.pfsense.org/issues/12688
Is there a patch?

stephenw10

Hmm, that is already in 22.05 so it can't be that identically.

netblues

@stephenw10 Indeed!
I tried deleting and re-applying interfaces, rebooting etc, just to make sure it isn't something transient.
Reverting to the 22.01 snapshot always works.
All interfaces are virtio type.
Only ppp has issues. Other (internal) traffic via other virtio interfaces works too.

luckman212

@netblues Might be a good idea to pass this info over to a new redmine.

kprovost

Can you confirm the package version of mpd5 that's installed?
("pkg info | grep mpd5" should do just fine.)

The error string '[vtnet0] Cannot attach to ng_ether message' was part of the patch we removed to fix #12688, so it's very surprising to see it here.

netblues

@kprovost So, yes the issue is that mpd isn't getting updated to 5.9_7

However I run the process again, and I did notice mpd 5.9_7 being downloaded during upgrade.
After rebooting in ended up with 5.9_6 and the same problem
The thing is without internet connectivity isn't easy to update mpd to 5.9_7
The is no squidgard or anything outside packages installed.

Any chance a package would be the curlpit?
This is repeatable.

stephenw10

If you have Squidguard it might be it's install/deinstall script getting wedged. That has happened in the past but I could not replicate this time round.
If that is the case you will see the pkg-static process still present in the output of ps -auxwwd.

Steve

netblues

@stephenw10 No squidguard ever installed though.
I have removed a few things like haproxy, freeradius and wireshark,
and will try updating again.

Strange as it is it always ends up with the wrong mpd.

netblues

After changing connectivity options to non pppoe, and upgrading mpd manually., after upgrade, ppp finaly worked as expected.

I have a snapshot and tried the upgrade a few times.
Always ends up to the same result.
So it can't be transient/connectivity/host availiability issue

Easily fixed if there is pf internet connectivity after the upgrade. If not. hell breaks loose.

Radiam

I have just upgraded to 22.05 from 22.01. Same issue MPD: mpd5-5.9_6 with no pppoe - the 'cannot attach to ng_ether message' error.

Not sure I have an easy option to connect this box to the internet outside of building another box with 22.01. Any advice on how to resolve (copy files manually to upgrade mpd etc.) much appreciated.

jimp

What do you have in /usr/local/etc/pkg/repos/? Do you have any third party repositories in there? If so, remove them, remove any packages you installed from them, and pkg clean -a; pkg update -f; pkg upgrade -fy to reinstall everything to ensure you have a proper set of packages and dependencies.

We saw something similar last week from someone who used a third party repository to upgrade ntop and that third party repo had outdated packages.

In general using third party repositories is a bad idea, this is one of many reasons why.

Radiam

Thanks for the post. I have checked the repos and no third party - it seems like something went wrong with the install like netblues above. I do have squidguard installed.

In the end, I basically did what was described above (with some detail in case it helps someone else):

Connected WAN to a wifi hotspot (which was a little more painful than I hoped). This was helpful: https://www.youtube.com/watch?v=qRyXAFD94lI
Used pkg upgrade -y mpd5 in Diagnostics/Command Prompt to force the upgrade of the package

Confirmed upgraded with pkg info | grep mpd5
Changed WAN back to PPPoE connection

Hopefully this is a limited issue. Was a bit painful but learnt some stuff along the way so not all bad.