Upgrade to 22.05 has killed my pppoe WAN
-
@stephenw10
Same again. No WAN post upgrade to 22.05
This is a mess!
Any ideas? -
@orangehand
I’ve got a spare physical port. Might it be worth trying to move the wan interface to it? -
@orangehand
Just tried igb2. Simply changed WAN to it in interface assignments. Haven’t rebooted. No dice -
@orangehand
Rebooted. No change -
You see the same error? Same output from
pkg info -x pfSense?I note you have Squid running, I wonder if that is getting stuck reinstalling.
-
Shell Output - pkg info -x pfSense
pfSense-22.01
pfSense-Status_Monitoring-1.7.11_4
pfSense-base-22.05
pfSense-default-config-serial-22.05
pfSense-kernel-pfSense-22.05
pfSense-pkg-Status_Traffic_Totals-2.3.2_2
pfSense-pkg-acme-0.7.1_1
pfSense-pkg-bandwidthd-0.7.4_5
pfSense-pkg-iperf-3.0.2_5
pfSense-pkg-ntopng-0.8.13_10
pfSense-pkg-openvpn-client-export-1.6_4
pfSense-pkg-pfBlockerNG-devel-3.1.0_4
pfSense-pkg-squid-0.4.45_8
pfSense-pkg-squidGuard-1.16.18_20
pfSense-pkg-sudo-0.3_7
pfSense-pkg-suricata-6.0.4_1
pfSense-rc-22.05
pfSense-repo-22.05_2
pfSense-upgrade-1.0_26
php74-pfSense-module-0.76 -
@orangehand said in Upgrade to 22.05 has killed my pppoe WAN:
pfSense-22.01
Yeah, it still has the 22.01 meta package. If you run
pkg upgradeit should offer you the upgrades to the current versions of anything that didn't update correctly. -
@stephenw10 That worked, thanks. Manually change the WAN method to PPPoE or restore the last good backup?
-
I would manually change since restoring the backup will reinstall all the packages again and might hit whatever was stalling out last time. If that does happen you can usually find the stalled process and stop it allowing the install to continue.
Steve
-
@stephenw10 Part of my plan was to virtualise pfsense in Proxmox. I've just made a bare VM of 2.6 CE which again will only correctly bring up a WAN interface off my ISP router and thus using DHCP. I assumed I would be able to get PPPoE to work on this clean install but no. I've read other instances of 2.6 or 22.05 killing the WAN interface. Does this need to be logged as a bug now?
ppp log attached
-
@orangehand The connection is Zen fttp and I've double checked that the only data they need in the ppp process is username and password, both of which are triple checked to be correct. I'm just checking what they are seeing their end. Will update this if anything significant.
-
@orangehand
OK. Mysteriously all sorted. I've typed in the ppp creds so many times, but this time it worked. About to try the CE to + upgrade! -
Hmm, yeah, fingers crossed then. I have a number of PPPoE connections working fine here in 22.05. As far as I know it should work fine.
Steve
-
@stephenw10 Bazinga! Finally! Many thanks for your help Steve. It didn't return any packages, but I'd filled the previous box with so much dross that I'm happy to be starting again. If I've restored a backup of the system with those packages installed, if I install them manually, will they likely just pick up the settings? And if there are orphan settings which I will never use again and which have no parent pkg, how best to remove them?
Many thanks again!
(This is now virtualised under Proxmox.latest on one of the Chinese 4x2.5g boxes that STH have been featuring 2G/50G 2 cores. FAR quicker and more responsive than the APU24 that it was on as a bare metal install)
-
Sorry to revive a 10+ day thread.
Just upgraded from 2.6 > 22.01 = works fine
upgrade from 22.01 > 22.05 it broke my PPPoE. Bell Fibre in Canada. IDK if that brings any details to the table.I will attempt some of the things here with dpkg upgrade because it's a remote site, so fingers crossed for me.
I tried a few times to just re-enter the PPP details; deteling and remaking both the VLAN tag and PPP credentials and just straight NOTHING. PFSense just checked out for a vacation. -
@stephenw10 Given the most recent post here, is this looking like a bug now?
-
More information needed. @gothixkhan are you seeing the same errors in the logs after upgrading?
-
@stephenw10 I'm happy to report 2nd time around, it did not mess up PPPoE.
Is it possible really that it gets stuck on a pkg upgrade if PFSense is loaded with plugins?
my previous installation had pretty much all the plugins I needed for security and functionality.I just redid it on a brand spanking fresh install of pfsense and it worked like a charm. so maybe food for thought?
-
@gothixkhan said in Upgrade to 22.05 has killed my pppoe WAN:
Is it possible really that it gets stuck on a pkg upgrade if PFSense is loaded with plugins?
Yes, it is. And that is what we suspect is happening here though we've not been able to replicate it locally. Unfortunately most users reboot or reinstall before we can check what the pkg process is doing.
However this doesn't appear to be a PPPoE problem specifically. That's a symptom of an incomplete upgrade.Steve
-
Hi,
I wanted to upgrade my 2.6 CE to pfSense Plus 22.05 today (always need to watch out for an ability for a 30 min downtime) and ran into exactly the same issue. :(
The intermediate step to 22.01 worked fine, after update 22.01 --> 22.05 my WAN was dead. Seeing the same error message in the logs: "Cannot attach to ng_ether message: Invalid argument"
I had no way to get PPPoE up and working. Found this thread and saw that my mpd was 5.9_6 (it should be 5.9_7). As my server is in my basement with absolutely no cellular coverage I can't get some LTE hotspot connected - so finally I needed to revert to my pfSense 2.6 snapshot which I took before the update.
So, looking for a new slot where I can put my complete homlab down, can I download the mpd package somewhere manually and then update it "offline" if the same issue happens again? (Which is a good chance as I saw no errors during the upgrade process and package download)?
Any advise how to manually upgrade the mpd from 5.9_6 to 5.9_7 without any internet connection would be highly appreciated.
-
J jacotec referenced this topic on
