Upgrade to 22.05 has killed my pppoe WAN
-
That's probably quicker if you're able to do that.
Steve
-
@stephenw10
Clean install and restore seems to have got me back up and running. Changed the file system to ZFS.In order to restore + which I previously had should I just request another lab key? Or should I use the previous one if I can find it?
Thanks for all your help Steve; the moral of the story is to have a cheap router ready to rock so you can plug pfsense downstream of it and thus retain functionality. Zen's FritzBox has set me in good stead in this instance.
-
@stephenw10
Oddly I cannot paste in a key. It's on 2.6 CE, but the register page does not allow pasting - says it already knows the device. Can you advise please?
-
@orangehand
Sorry - ignore. I hadn't spotted it in the upgrade drop down! -
Like it says there, your device is already registered, you don't need to register again. the NDI doesn't change when you reinstall.
Steve
-
@stephenw10 So I am back at 22.01 where I was. I'd like to go up to 22.05. What chance do you think of the same chaos ensuing? Am understandably nervous!
-
Well I've updated countless things from 22.01 to 22.05 without issue. Including CE > Plus upgraded boxes. So I wouldn't expect any issues. You can never be 100% though since you hit something last time.
-
@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
